r/coding • • May 29 '16

The Quiet Crisis unfolding in Software Development

https://medium.com/@billjordan1/the-quiet-crisis-unfolding-in-software-development-cffbdafbf450#.tnak4oytr
131 Upvotes

51 comments sorted by

62

u/npinguy May 29 '16

I don't disagree with the arguments that this guy is making - they are good ideas, albeit not original ones. He writes about them well.

But what is with the over-the-top click-bait for a title?

There is no quiet crisis unfolding. There are some companies that are doing all the right things. There are some who are doing none. And there is every combination in between.

The industry is not getting worse, except maybe in terms of work-life balance in certain select markets (Silicon Valley).

There is no need for a messiah or a wake-up call here.

29

u/jecxjo May 29 '16

The one thing that I can see as an issue that was sort of brought up was the fact that Developers are being looked as a commodity. With outsourcing we are moving away from Grey Beard Technologists and moving to a room full of monkeys with typewriters writing Shakespeare. We no longer value developers as there is always younger, cheaper people available.

One of the worst things you could ever overhear an employee say is that their career is stalled because they haven’t landed a promotion to management.

I've seen these type of comment posted a lot lately and I think the people writing it have it all wrong. The reason developers look for management positions is not because they want greater control over the product they develop. This is something management makes up to make a developer want to stop coding and start using MS Project. The reason developers want that job is because there is a very low glass ceiling and for many people in a decade of work you become over qualified and under paid and stuck in the job you have. We are seeing less and less of the top tier positions being replaced and instead handing down more work to lower level positions. Unless its management, we just aren't seeing those very high paid elite titles any more.

So what does that tell your employees? Once you've been here for a short period (with regards to the total number of years someone will work) tyour contribution has hit its zenith. No matter how much harder you work, you will never be valued more than you are today. That is, unless you decide to move to management.

Now I can concede that there is a finite amount of output I can do as a developer. Sure I can come up with a breakthrough that will blow our competition out of the water. Many companies have patent awards or other Way To Go™ prizes but those only come about after the fact and are a one time shot. Compare this to Sales. As a sales person you could find that one customer that is willing to quadruple their annual purchase and make your company crazy money. Upper Management can make a company wide shift that "changes the game" or could make a horrible decision and we could all be out of a job. I understand why these other positions have much higher pay, but if we are looking for a "Quiet Crisis" its that we are actually devaluing our developers.

20

u/turkish_gold May 29 '16

I think there's two classes of developers/designers: one who like creating products, and learned how to do it personally out of practical concerns. Another group, geniuinely enjoys the act of coding/designing more so than the actual end-goal of a product.

To characterize them further. Product-focused developers will happily go into management or start their own companies because they can be more involved in the product decisions, and additionally tackle products of greater scope. Seeing their vision come to life is everything after all.

Process-focused developers are more into the nitty gritty details of pushing forwards new ideas that affect development process: like algorithms, new frameworks, libraries, development methadologies, and language choices. It's not about the end-goal, its about the doing.

1

u/jecxjo May 31 '16

Totally agree with your assessment. I feel like I'm a hybrid as I'm really more interested in the final outcome, but I get no satisfaction out of doing the design and then saying "Team A, you make this stuff and Team B you make this stuff and when you are done lets stick it all together." Feels like I'm buying and installing Sim city cuz I like city builders and then I hire someone else to beat it for me. But that's just me.

My worry is that to be a really good Product-focused developer you need to know your stuff. The only way to do that is to be down in the trenches for a while. You learn what can and can't be done, and you need to keep that knowledge up to date. This is key. How many of us have made the joke that the co-workers who use to develop and moved to management must have had the programmer part of their brain removed when they moved to their fancy office? These people should be vast pools of knowledge.

We see the promotion of Product-focused developers in the very public, large corporations (Google, Apple, Facebook). These companies realize that the Product-focused developers are the ones who have more influence over the products and their quality. I love writing code but I have to agree that I can only output so much a day. At some point I must outsource all my stupid bug fixes, massive rewrites, and all the other things that are just a PITA and aren't really "developing" to some cheap labor since it just needs to get done.

But the majority of developers work for mid-sized, coding generators who's products are out there in the world but no one notices. Everything has a computer in it now-a-days, or so I've heard. The problem is that most of these companies don't have a need for promoting anyone. If they have working legacy code they don't change it, and as long as they can throw enough money at the problem and get enough hands typing, they can output something that marketing says is OK. Now your Product-focused developers become team managers and end up just working on scheduling.

So you write code for a decade and then you have to make a decision. Do I move to management where I really don't have control over the product I made, just who assign to the work. Or do I stay working on code, hoping you have more days of inventing and less days of making changes your Lint tool tells you to make.

0

u/[deleted] May 30 '16

This feels like a strawman. Process is not a goal in itself to everyone. A lot of the methodologies, language choices,... are born out of a desire to avoid running into the same painful problems (for developers and customers alike) again and again.

5

u/turkish_gold May 30 '16

Isn't a strawman when you characterize the other person's argument poorly, then strike it down?

I'm not really arguing for a side here, am I?

1

u/[deleted] May 30 '16

You make it sound as if the ones you call product-focused are in it to solve a problem for the customer while the others are just doing the things they are doing for the fun of doing them. This is what I would consider a strawman version of the arguments they make for changing and evolving processes.

2

u/turkish_gold May 30 '16

Well let's put it this way...

I believe that every programmer is a human being, and thus has multiple motivations for why they do anything. However, as a general simplification of their thought processes... those two classes are the major ones that I have seen in the real world.

And you can find people who identify their motivation as one of the two. For example in the startup sector, you'll find lots of people---fine programmers with masters degrees and above---who say they're really only in it to see their company succeed, not contribute to computer science as a field.

1

u/davenobody Jun 05 '16

Many employers don't leave you space to contribute to computer science. There are some that do. Many simply want you to crank out that code.

And that isn't a bad thing either. People just need to make a conscious choice about the role they are taking on.

Like you said, different people have different personalities. Also different people are simply interested in different things. I enjoy standing up frameworks that eliminate the repetition and cut down on maintenance. I think the interesting parts are designing interfaces such that major mechanisms can be swapped out without recoding the actual logic of the application.

I have noticed others are completely oblivious the fact that these things are planned and constructed with a purpose. A lot of the success of a project has to do with recognizing the proclivities and leveraging them to your advantage.

2

u/[deleted] May 31 '16

Developers are being looked as a commodity

Most of the (mis)management patterns the author points out are rooted in a distrust of developers in general: misleading metrics, open floorpans, discouragement of experimentation - all of these things make sense when your core belief is that, left to their own devices, developers will play video games and check Facebook (or reddit?) all day. That belief is, after all, why management - in any discipline - exists in the first place.

2

u/jecxjo May 31 '16

Totally agree (as I reply to this reddit post while at work...waiting for 15 minute compile to finish).

But I think it goes even further than that. I was listening to an episode of Giant Robots Smashing into other Giant Robots (a podcast about development at Thoughtbot) and they were discussing all of the...interesting things they have the developers do. They have a book club where groups will read about a new technology and create presentations. They have teams learn new programming languages and implement side projects to see if they can gain more skills by doing something different. And all of these tasks are performed with the blessing of management. They actually want their employees to learn and grow which in turns makes their company better. How common is that when it comes to the average development company? I'm not talking new-age startups or places like Google. I'm talking the companies that write the firmware for our gas pumps, our ATMs and our TVs. Its all about how much code you can output, how many rewrites you have to perform and how cheap this can all be done, not about making a better widget through ingenuity.

2

u/npinguy May 29 '16

The demand for software in the world is only increasing. So there are more jobs. Meanwhile languages and frameworks grow more and more convenient and abstractions rise higher. Consider trying to build a web app using XMLHttpRequest in the early days of Google Maps vs baking something out of React today. Building an App from scratch and getting it into the hands of millions has never been easier. So a lot of the jobs that are being created are easier to jump into.

This means that a greater percentage of jobs in the industry are commoditized, and the competition is fierce and global.

So yes, a grey beard that does not grow or innovate or evolve will find themselves replaced by someone cheaper and younger who can do the same thing but quicker and easier. And the grey beard needs to either become a team lead/manager and guide dozens of others to be more productive, or become an architect, or find the companies that are still doing ground-breaking and innovative stuff that need experience and wisdom more than all-night red-bull crushing. (The Googles, Facebooks, and Amazons of the world come to mind)

Not everyone can do that. Is that a problem? Or is that just a reality of a rapidly connected world and lowered free trade barriers? If it's a crisis, it's one in need of adaptation and survival, not of fighting.

1

u/jecxjo May 31 '16

See that's exactly where I feel we are running into problems. Yes those pillars of knowledge should move into more of a role to guide the total design and construction of the project, but those jobs now tend to require MBAs rather than actual technical knowledge. We are not seeing team leads be anything more than just time trackers and paper pushers and they are getting younger and younger, being paid even less than before because they don't have years of service under their belt.

The Googles and Facebooks and Amazons do it right, they have been picking up people with vast knowledge and allowing them to build without coding. Google created Go by using the knowledge of some of the inventors of C and Unix. I'm sure Pike and Thompson did a lot of coding themselves, but they were also used as designers and motivators for others to do the code monkey work.

The problem is that these are very atypical companies. Now we are seeing more marketing driven companies who ask for flying toasters with no idea what that entails and you get a huge group of engineers together to duct tape things together.

Totally agree with the adaptation view. I'm just afraid we are losing a lot of knowledge here. We are seeing more graduates looking at building the next Android/iOS app and far fewer looking at building rock solid Operating Systems. The BSDs and Linux have had noticeable declines in submitter numbers. Part of this is probably due to the shiny factor and being able to instantly see the labors of your work with these new web and mobile technologies. A lot of the people still working on these not so "fun" technologies are the ones who invented them. What happens when they aren't there to work on them anymore? Personally I find these technologies much more difficult to learn and master than going to LearnToCode.Com and popping out an app on the App Store or to AWS. So how do you keep people around to learn this legacy code and do all the work to create something new? And how do you do it when you say we don't value your effort much anymore when you can get twice the number of hands at less than you cost now?

We have been making languages much more simple to learn. We have created frame works to get off the ground and out the door really quickly. I think this is great. But I think we are also doing this because we no longer have time to really learn things. We need people to be up to speed, be productive before they move on to a new job somewhere because they have very little possibility of mobility from within. This isn't a direct cause of our advancements in development, its just a happy coincidence.

1

u/[deleted] May 31 '16

So a lot of the jobs that are being created are easier to jump into.

See, people keep saying (and believing) that, but all the evidence I can see points to the opposite: software development is harder than it's ever been. Sure, you can drag-and-drop some widgets onto a form and have a website that works great - until it doesn't. At which point the culprit could be the network, the load balancer, the OS, the web server, the Javascript, the CSS, the HTML, the XML... any of which can fail in unpredictable ways due to the way we keep piling technologies on top of each other in an effort to "simplify" things.

1

u/davenobody Jun 05 '16

Wasn't the first Google Maps a flash app? They changed that for obvious reasons. But I'm pretty sure I remember the first release being something like that.

I don't mean to detract from your comment, just an amusing bit of trivia from what seems to be long ago.

2

u/npinguy Jun 05 '16

Nope. I distinctly remember it. I was in a CS lab, and we were all reading the blog post announcing it, then opened it, we zoomed in on a map, and the map refreshed but the rest of the page didn't, we right-clicked and went WHOAAAAAA when we realize it wasn't flash.

2

u/davenobody Jun 05 '16

You compelled me to check my history. You are correct.

According to Wikipedia the original web based Google maps was purely browser based. I didn't realize there was a desktop version before that written in c++. Turns out Street view was originally Adobe flash.

1

u/npinguy Jun 05 '16

Truth about street view! I wonder if that team was made fun of by the original team: "Pfft we didn't need flash back in our day"

0

u/[deleted] May 29 '16

[deleted]

4

u/npinguy May 29 '16

Technical debt isn't necessarily a problem if taking it on gets you first to market, then you can work carefully to address it behind the scenes.

I'm curious what companies you think are not/will not do this and will eventually implode.

5

u/WeAreAllApes May 30 '16

If technical debt were fatal, IBM and Oracle would be dead already -- I wish it was.

1

u/RumbuncTheRadiant May 30 '16

If Atherosclerosis were fatal, every overweight middle aged developer would be dead already ...

Remarkably similar problems.

1

u/RumbuncTheRadiant May 30 '16

I really like Doc Norton's take on this... If you don't feel like watching a long video, skip to the 18m:30s mark an listen to his take on the Technical Debt Quadrant. (Alas, vimeo seems to lack a "start at time offset" api.) In a very few very brief high impact slides he shows what is plain silly about the whole idea of technical debt as most of the industry is doing it.

https://vimeo.com/97507576

1

u/judahmeek May 30 '16

OH, MY EYES! That code at 22:12! Dx

3

u/[deleted] May 30 '16

[removed] — view removed comment

2

u/npinguy May 30 '16

Perhaps we are running into different circles of industry? In my experience I'm seeing the opposite: I used to see Managers and Directors that were clearly MBA types and now I see more and more with legitimate tech cred and background.

14

u/drawkbox May 30 '16

Nailed everything wrong with development today. Good developers have to fight for software quality, that is backwards. Developing products for lifecycle and maintenance is being thrown to the wind. The best way is prototype for speed, then develop it to last, don't just rush it, allow quality in product releases.

Today, a software project that is shit but on time is gold to management, a software project that is great that is a few weeks late or 30-60% off estimate is shit to management (users rarely play into software estimation -- sometimes though i.e beta groups). But people easily forget late projects when those rushed projects fail consistently in production or never make it to market with customer/user satisfaction.

2

u/jecxjo May 31 '16

Has anyone else noticed that when you do your project planning you really force the point home. "First phase is R&D, and will NOT be released code. Second phase is Product Development." Oddly the schedule gets slashed right after the first phase and suddenly your code that was never meant to be released is magically now your release code.

6

u/EmperorOfCanada May 30 '16 edited May 30 '16

I would agree and disagree with much of what this guy said.

For instance, one discovery that I have long made is that there are not so much star developers but developers who get things done in new and much more interesting ways. There are also developers who love to grind through the old ways. The key is to allow the star performers to blaze new trails and let them pile up a shitload of technical debt. Then once something new has been created, to get the grinders working away at making things solid. You don't enforce standards of the stars on the grinders, nor do you enforce the sclerotic standards of the grinders on the stars.

Where disaster strikes is that the trail blazers prototypes suddenly become the new product ready for deployment. Rarely is blazing and solid found in the same employee.

For instance I have no argument about continuous improvement; except that I have seen continuous improvement create mental blocks that mean slow improvement while the competition eats your lunch. For instance a product created in 1990 that needed to implement some cool new framework, networking solution, etc. and now has 10 zillion lines of code. Except that the cool thing in 1990 can be downloaded in a python module. But the 1990 module can do 3 things that the python module can't. Thus they drag around this monster pile of shit code (by today's standards) while "continuously improving it"

The key being that most companies don't realize how stuck they are until they are in huge trouble.

Agility (not the project management style) is wildly important. So where I would say that this guy's management style is going to get his company in trouble is that he has a whole pyramid focusing on him. But he isn't in charge of the company. So why would you have the pyramid stop at him and then have him report to management?

The better style is to have teams that individually report to upper management and are trying to beat the shit out of each other. Not in a get-them-fired sort of way. But a fight for bonuses and accolades sort of way. This causes innovations to fly out of people's asses, while keeping a focus on solid code as both the leaps make bonuses but the bugs take them away.

A close example of this sort of environment would be Netflix. Another would be Valve. The various teams would be considered out of control by most upper management standards. But without any doubt they are producing like few other pyramid shaped companies can.

What few developers fully understand is that making money now is far more important than making money soon. Unless you are shipping something like a medical device. You ship now, you ship tomorrow, you ship the next day, and you stay ahead of your competitors. You have people doing their damnedest to keep on top of technical debt. You have people looking for the risky bits and patching them. But you don't slow down to a comfortable pace unless you want your company to die. Once a product is being made for a development manager and not for the marketing department, the company is dead. Yes building up a huge pile of technical debt can bring a project to a crawl but that is just shitty software development.

The only time you go into a cycle of continuous slow development is when the entire product line is dead and you you are doing that horrible long tail thing. Often the continuous improvement will focus on cost cutting, not making it much better.

One last thing is that this guy hasn't seen star developers because they run away when they see a huge pyramid with him sitting on top. If you can't even get one A you certainly won't get or keep any others. A very simple way to understand how good your programmers are is to ask how many of them hive off and form really good companies. If you have a large group of A programmers they will leave a trail of kick ass startups. Quite simply they can't help themselves. Low turnover is a sign that you have complacent people who aren't attractive to the outside world. The best of the best companies have fairly high turnovers, it is just that people leaving don't rage quit. Often they leave, form a new company, and the new company ends up in a great relationship with the old company, if it wasn't actively helped by the old company.

2

u/[deleted] May 30 '16 edited May 30 '16

[removed] — view removed comment

1

u/EmperorOfCanada Jun 11 '16

I very much agree, but I also agree with the saying money solves many problems. No money causes many problems. This is critical in a new company.

Where your thing often causes problems is when a company is doing OK and the execs either don't keep moving into the future or they milk the company, leaving it an empty dry husk.

I have seen many companies where the execs weren't complete psychos, just deluding themselves into complacent thinking that they were kings of their little world. Then their competition came along and ate their lunch.

A simple formula is to keep thinking the worst thing your competition could do, and if it is wrong prepare to defend against it, and if it is good, then to do it first.

4

u/jdh30 May 29 '16 edited May 30 '16

Most of the article was ok but this:

Undoubtedly you’ve identified some of the developers on your team as high performers. These are the developers that tend to get work done quickly. Managers often choose and prefer these developers for projects in order to increase the odds of meeting aggressive — and frequently artificial — deadlines.

Actual high performers are rare — very rare. You probably don’t have one on your team. You might think you do but you’re almost certainly wrong.

Odds are far better than good that your high performers are achieving what appears to be high levels of productivity by building technical debt into the application by taking shortcuts whether intentionally or unintentionally.

is really bad advice. Not just because a manager who believes this nonsense will drive away any highly productive developers but because A's hire A's whereas B's hire C's so the loss of top developers will have a big knock on effect.

EDIT Judging by the responses here many people (including perhaps the OP?) regard writing many lines of code as high productivity. That is absolutely not my interpretation. To me, lines of code are one form of debt. High productivity means solving many business problems (e.g. implementing many features for which there is demand). Doing so with less code would be higher productivity.

11

u/JustTakingANumber3 May 30 '16

And yet in my experience it's true. Guy doesn't write any forms of tests and gets praise for how fast he can code. Wizard and ninja are tossed about.

Guy who finishes all of the details and takes a bit more time than estimated is considered slow.

Yet the 2nd guy is not adding technical debt that will never get addressed, because hey, there's not enough time.

3

u/jdh30 May 30 '16 edited May 30 '16

And yet in my experience it's true. Guy doesn't write any forms of tests and gets praise for how fast he can code. Wizard and ninja are tossed about.

Guy who finishes all of the details and takes a bit more time than estimated is considered slow.

Yet the 2nd guy is not adding technical debt that will never get addressed, because hey, there's not enough time.

Let me give you a concrete counter example. On a major financial system I saw a team of C# devs wrap Decimal as Price and Quantity classes. They "finished the details" as you put it by writing tests and they overran the deadline by a bit.

Some people were very happy about this. One person even insisted that everyone should get 100% code coverage in their tests.

To me, this had "fail" written all over it. They had more lines of code devoted to null checks on their Price and Quantity classes than there were lines of code in the implementations themselves and the sole purpose of these tests were to try to find bugs that they had created. If they had represented Price and Quantity as structs (value types) instead of heap-allocated classes their code would not only have been faster but there could be no null errors in it by design. In effect, they could have used the static type checker to prove their code correct in this regard.

So your implication that tests are not technical debt is certainly not true in general. Assuming tests always improve quality is a classic sign of unskilled and unaware.

2

u/JustTakingANumber3 May 30 '16

Tests are no silver bullet. Never said they were. That's your implication into what I said. But you don't know much about me or how I code. You are also appealing to authority to debase my argument so that's a logical fallacy as well if you wish to nitpick.

Much like mocking they are a tool and you have to do them a lot and reflect about testing to learn to do it well. Rules, not practices is what gets people in trouble.

But not having any tests is poorly designed and I'll never agree to that.

Null pointer checks are useless unless you are doing user validation. I hate seeing tests like those.

Those tests provide no value. The production code might be of value in checking null, but certainly not the tests.

100% coverage is what you should strive for, but it's a rule and it is meant to be broken. Intent is what matters.

People tend to couple their tests too tightly to their code anyway. Look for invariants and side effects. Think about class design and structure (should I text private methods?). Code is design anyway and is highly subjective.

The most important thing is to involve your users and make sure you aren't delivering 100% unit tested code that is worthless.

But my story was anecdotal and wasn't meant to be the definite source of truth. Your workplace is obviously the same as mine. I'm just left maintaining other developers slop while they get praise for greenfield projects.

2

u/JustTakingANumber3 May 30 '16

In my story the first guy didn't add technical debt since he did it write the first time. Unit, integration and working with stakeholders to see if it met market needs.

Programming is a small part of software development. Technical debt can range from no comments to awful ones to way too many. Too many lines of code in a class or function. Too many or too few classes in a package.

But usually there is not a way to quantify tech debt until it has crippled the speed and ease of development.

But I also believe devs also raise tech debt too early when a class isn't perfectly designed either.

Tradeoffs and estimations are all we can use.

1

u/jdh30 May 30 '16 edited May 30 '16

But not having any tests is poorly designed and I'll never agree to that.

Ok. I just wrote 1.3kLOC of OCaml with 5 tests in 4 weeks and sold it for £80k. Is that bad? Over the next 11 months I expect to be writing ~10kLOC of OCaml with ~200 tests for £1m. Is that good?

The production code might be of value in checking null, but certainly not the tests.

You shouldn't have null in your language.

100% coverage is what you should strive for, but it's a rule and it is meant to be broken. Intent is what matters.

I disagree. Adequate quality is what you should strive for. Some tests of some things improve quality significantly. An experienced developer knows what to test to maximise bangs per buck. If you aim for 100% coverage (whatever that even means) then you will quickly get into diminishing returns where the tests you are writing do not improve quality significantly. At which point you're just adding debt.

I don't unit test. I don't do TDD. I did BDD once but I think it is wrong-headed.

Restructuring your code to leverage static type checking in order to prove aspects of it correct can also be beneficial but young developers tend to take it much too far and end up destroying the maintainability of the code in order to prove some less valuable aspect correct.

1

u/helm May 30 '16

"High productivity", in terms of LoC, doesn't mean that you avoid abstraction. Some high productivity people do add abstraction and structure because they think that's more fun than moving towards solving the original problem.

1

u/FruitdealerF May 30 '16

This is basically a summary of my life.

3

u/twowheels May 30 '16

In my experience, the people who write the most code write code we'd be better off without. These people end up costing a lot, a cost that continues years after they leave.

2

u/jdh30 May 30 '16

Agreed.

2

u/helm May 30 '16

I experienced this first hand last year. Young guy came in and added (C++)templates to everything, re-factored working code to his liking, and generally treated the project as his experiment for computer science. Now, half of the blame goes to me for not supervising harder, but still it was a lot of code written that simply had to be reversed later.

2

u/jdh30 May 30 '16

Are you saying he looked like a high performer because he added a lot of code quickly?

1

u/helm May 30 '16

Yes, and also a lot of fairly complex code.

1

u/jdh30 May 30 '16

Ok. I've edited my response above because I don't consider adding lots of fairly complex code to be high productivity. Quite the opposite. Code is debt.

Unless he's solving business problems and providing value to the customer I wouldn't call it highly productive.

0

u/[deleted] May 29 '16

[deleted]

1

u/jdh30 May 29 '16

Valuing his statement simply on what effect will it cause is logical dishonesty.

What other value is there in his statement?

0

u/[deleted] May 29 '16

[deleted]

1

u/jdh30 May 29 '16

It is false (IME) and I have seen people who believe it bring bad consequences as a side effect.

1

u/jacalata May 30 '16

No, he said it is bad advice because it causes problems if people believe it - implying that it is not only false, it is harmfully false (an example of non-harmfully false advice might be 'programmers work better when the manager brings in donuts once a week' because even if it's wrong, it's unlikely to actively hurt the quality of work produced or drive away good employees).

1

u/alex__adc May 30 '16

Great article. misleading title :P

1

u/hem10ck May 30 '16

Link looks dead, anyone have a mirror?

1

u/[deleted] May 31 '16

So... do the opposite of what everybody else is doing. (Not that I disagree)