If they really believe they can measure programming ability by the number of times their workers are clicking things, I'd give a wide berth to their software products.
If they really believe they can measure programming ability by the number of times their workers are clicking things, I'd give a wide berth to their software products.
The “cloud wage” story could be very compelling in such situations, but it will likely lead to a lot of issues with the more complex systems. Someone has to be the true “architect” and own the successful evolution of the software/business.
Back in 2014, this article struck me as very insightful on the subject: https://www.japantimes.co.jp/news/2014/04/07/business/gods-e...
If you only have automation or low-end jobs, you are going to lose the ability to make transformative/revolutionary moves. You will still have the ability to refine existing processes, but there are definitely diminishing returns to consider.
The other item that’s also glossed over is sheer productivity - when dealing with more complex issues, experienced developers are a lot more productive, so your $15/hr can easily turn into 10-20x more hours with the wrong experience choice, in the end costing you more.
Hate to use a cliche, but “the right tool for the right job” applies to software too.
When you are the "consulting company", you don't care. You just get to bill more hours.
If you are the client company, you don't care, either. Anyone with half a brain cell in this day and age knows that outsourcing software development is wholesale idiocy. So, if you're doing that, you are either 1) idiots or 2) outsourcing for political reasons or 3) both.
Your options to compete with them are very limited.
Is the answer to every question, "Who is actually doing something creative and innovative?" always, "Me, and everyone else is not?"
Is it bad for software engineering that its reality is starting to resemble subway sandwich artists, and its fiction inside people's heads resembles being a Michelin star chef?
Right now though, it's more like a popular restaurant chef. Moving to the McDonald's model eventually.
I write software now. I helped open that kitchen. The first couple months is engineering, how to get organized to plate 90 quenelles in 4 or 5 minutes under a heat lamp. Writing software is just like engineering that kitchen everyday all day, month after month. It's not about creativity or innovation with food. It's about creativity and innovation with solving engineering problems.
Can you see yourself doing this? We need more diversity at the senior leadership level, please consider it if you haven't!
Also if you don't mind me asking, can you share what made you leave your former profession, was it the stress/physical exhaustion? It seems like grueling work to say the least.
Thanks for sharing your background and perspective on HN!
Two or three times, sure, but ten? Any more info on this? Are Michelin cooks superhuman or Subway people so terrible?
The biggest disadvantage to those outsourced developers might be that they didn't have the chance to learn English as well as the first-world devs, and thus might have issues with communication, which is a huge part of software engineering for sure. But in terms of abilities to learn, they are not worse than anybody.
previously worked on-site at a web hosting company which had similar sorts of spy systems in place - these weren't really checked or used as a primary measure, but more that spot checks were done to see if people were 'generally busy', and also when actual productivity (support request qty/quality) was down or discipline problems occurred the systems would be used to inspect/audit other performance.
programming is for sure less 'mechanical' than routine system support support requests, but I can see the same sorts of measurement as useful in a remote work / no trust environment.
Majority of freelance marketplaces use the same creepy tracking software for gigs paid by the hour.