I won't get into whether or not it's fair to call call "developers" "engineers", but I do make the distinction in the first paragraph that the article refers to software engineers. In addition, velocity, bug count, and lines of code are all software terms. I can't imagine anyone thinking this is referring to any other type of engineering.
In this case, other context clues tell us that the article means 'velocity as in software development'.
Agile, for example, is another general term that has a fairly specific meaning in this context.
If you overhear someone in a park say "Oh, you guys are agile? What's your average velocity?" would you assume they are talking about athletics or software development?
Author here. Your point is valid. I do try to make this clear in this portion:
> However, an over-engineer can sometimes perform like an under-engineer or an engineer. Underperformance and overperformance could be influenced by a number of factors including work environment, context, intellectual horsepower, and even personal life.
I personally continue to write under-engineered and over-engineered code because there are so many internal and external factors that go into solving a problem.
I encourage you to keep writing, but it seems you need more research into developer patterns if you want to contribute to an already highly discussed topic.
For instance, last month this article[1] gave some seriously good insights to developer checkin frequency based on hard data. It provides a lot more value than the anecdotal, muddy definitions of over/under/engineer.
That's a very interesting article. However, it does seem suffer from the same issues Joel outlined, namely, the measure of attributes of a commit can be gamed and worked towards to achieve a "prolific" or "senior" status.
What the article you linked does reinforce is the value of iterative development. As opposed to doing large infrequent commits, doing small bits of work more frequently causes a success higher or "impact".
I would say that the article provides a data driven approach to justifying the effectiveness of good iterative planning. However, it doesn't address whether the commits of the "senior" engineer or the "prolific" engineer are of high quality.
Pangea | Chicago, IL | Senior iOS, Senior Platform (.NET/C#) Engineer | Full Time, On Site | http://engineering.gopangea.com
Founded in 2012 and headquartered in Chicago, IL, Pangea started with the mission of making money transfer effortless. Since then, we’ve been striving to enhance the security and reduce the cost and pain points of international money transfer.
Our first solution allows users to complete a transfer in three easy steps and pay with any US debit card, with an innovative nationwide cash solution coming soon. Receivers in Mexico, Colombia, Guatemala, El Salvador and Dominican Republic can collect the transfers in cash or receive the money directly into a bank account. Through every partnership and product iteration, we’ll continue to help our users save more time and money.
Founded in 2012 and headquartered in Chicago, IL, Pangea started with the mission of making money transfer effortless. Since then, we’ve been striving to enhance reduce the cost and pain points of international money transfer.
Our first solution allows users to complete a transfer in three easy steps and pay with any US debit card, with an innovative nationwide cash solution coming soon. Receivers in Mexico, Colombia, Guatemala, El Salvador and Dominican Republic can collect the transfers in cash or receive the money directly into a bank account. Through every partnership and product iteration, we’ll continue to help our users save more time and money.
At first blush it might seem to have a high learning curve given the verbosity of the syntax to define a stack, but with the launch YAML support, the syntax has become more succinct. Once you use it, you'll wonder how you ever lived without it.
The product page doesn't do it justice, but in short, CloudFormation allows you to:
- Describe the AWS resources you need in a single file (YAML or JSON), this would be your "stack".
- View all the resources provisioned based on your code in a single UI grouped under the "stack" in the CloudFormation console.
- Manage changes to your resources as different versions of the code file, meaning if you update a resource's properties in code, it'll know and update the already provisioned resource.
- You can delete an entire "stack" and be certain that all associated resources are also destroyed.
- When I used it, the coverage of types of resources you can code for was wide and they're continuously adding more.
If you're trying to remain cloud-agnostic, then I suggest you also checkout HashiCorp's Terraform [https://www.terraform.io/]. Think of Terraform as a scripting language that compiles into AWS CloudFormation or any other cloud provider.
Thanks for the heads up on CloudFormation. I've just poked around and realise the our Elastic Beanstalk instances all create a stack in there automatically. Seems pretty useful, and I will investigate a little more to see if we can integrate other AWS assets like S3 buckets, RDS servers etc. into each stack for better management.
- [ByteSize](https://github.com/omar/bytesize) (.NET/C#) library which is a utility class that makes byte size representation in code easier by removing ambiguity of the value being represented. ByteSize is to bytes what System.TimeSpan is to time.
- [PS1 Gen](http://omar.io/ps1gen/) is a simple bash PS1 generator and reference so you can soup up your command line. I created this after trying to research how to create a cool PS1 string.
We're looking for a strong iOS engineering leader for a 70% individual contribution and 30% engineering management role. You'll be responsible for the iOS app that's used by nearly 40% of our customers. You'll also be managing one other talented iOS engineer who's been with the company for over 1.5 years. The opportunity for growth in this position is to lead the iOS and Android teams.
Founded in 2012 and headquartered in Chicago, IL, Pangea started with the mission of making money transfer effortless. Since then, we’ve been striving to enhance the security and reduce the cost and pain points of international money transfer.
Our first solution allows users to complete a transfer in three easy steps and pay with any US debit card, with an innovative nationwide cash solution coming soon. Receivers in Mexico, Colombia, Guatemala, El Salvador and Dominican Republic can collect the transfers in cash or receive the money directly into a bank account. Through every partnership and product iteration, we’ll continue to help our users save more time and money.
This is exciting news for all .NET folks. We're running our Platform in .NET on AWS, so we'll need to wait for AWS to support Windows Server 2016 before we can leverage Docker.
For Windows Server 2012, AWS supported it [1] a little under 2.5 months after release [2].
Founded in 2012 and headquartered in Chicago, IL, Pangea started with the mission of making money transfer effortless. Since then, we’ve been striving to enhance the security and reduce the cost and pain points of international money transfer.
Our first solution allows users to complete a transfer in three easy steps and pay with any US debit card, with an innovative nationwide cash solution coming soon. Receivers in Mexico, Colombia, Guatemala, El Salvador and Dominican Republic can collect the transfers in cash or receive the money directly into a bank account. Through every partnership and product iteration, we’ll continue to help our users save more time and money.
I won't get into whether or not it's fair to call call "developers" "engineers", but I do make the distinction in the first paragraph that the article refers to software engineers. In addition, velocity, bug count, and lines of code are all software terms. I can't imagine anyone thinking this is referring to any other type of engineering.