News for hackers. Stuff that matters.
Re:Maximizing Developer Effectiveness by lxe on Saturday January 16, 2021 @02:53AM (#25800830)
Here I am, a productive developer eager to deliver maximum value to my customers and apply my innovation to company goals.

Open up JIRA and pick up a unit of work to produce today -- gotta stay faithful to those story points!

Somehow, a magic team of spherical devops in a vacuum created an environment where things are just green, predictable, and are never broken.

Another theoretical team of angels from a parallel universe has materialized into this one, updated all the docs, and beamed back into their universe of productivity and effectiveness.

Unit of work defined, I then proceed to produce it for a few hours completely uninterrupted, since if another human being were to make contact, I'd simply explode and format my hard drive, losing all my productivity.

It's break time -- I ingest 2 story points of coffee and join a game of table tennis. The ball bounces back and forth without ever touching the ground. My movements are productive, and value-adding, just like my partner's.

Back to producing units of work, only half a story point left (sike! no such thing as half a story point, and no such thing as "left", as it's a measure of effort, not time. Almost got you there!).

Git push! Automatic CI gains consciousness and validates that my work unit has no chance of causing a user to break our software. It gives me a thumbs up and discards its human shell to fade back into the ones and zeros. A QA engineer cries out in the distance.

A metric of my productivity is logged to the OKR database.

Nothing breaks, and nothing unexpected happens, as the universe is completely predictable.

Re:Maximizing Developer Effectiveness by cjfd on Saturday January 16, 2021 @04:18AM (#25801134)
It is true that the effective developer environment sounds a bit too good to be true. Also, there seems to be a contradiction in it. We get an answer from the other team very quickly but on the other hand there are no interruptions. It seems a bit hard for both of these things to be true at the same time. On the other hand one does have to notice that one can either be moving towards the effective developer environment or towards the ineffective one. It is a very important question in which of these two directions the actions of the team are headed. E.g., if the nightly build fails is somebody doing something about it or not?
Re:Maximizing Developer Effectiveness by ownagefool on Saturday January 16, 2021 @05:59AM (#25801492)
The article specifically suggests there's a dedicated support developer, which means you're sacrficing one member of your squad (per week) for the productivity of the rest of them. We can debate whether the idea is good or bad, but it's not pretending that its magic.

On the wider article, I think the litrature is a poor subsitutde for reality. And honestly I question whether a lot of these agile consultancies actually have the required experience to teach us how to be highly effective as opposed to what we can learn directly from orginsations that are highly effective, but I do believe they have enough experience to tell us that effective development teams invest in development tooling, dev focused user experience, and a dev focused culture.

Who and how you'll build this is left as an excercise for the reader, which is unfortunte because we now have a legion of consultants who've never produced a line of code making a career telling us "culture is hard" and then forcing us into scaled agile frameworks and tooling that are contradictory to the ethos.

Doesn't mean the underlying point is bad though. Engineering teams need some time to work on developer experience instead of just being feature factories; bigger org can hire teams dedicated to helping with this. This is a good thing, but many orgs fail at understanding and allowing the investment.

Re:Maximizing Developer Effectiveness by brobdingnagians on Saturday January 16, 2021 @08:05AM (#25801950)
I'm torn about this article, I love the part about feedback loops and optimizing the parts of your day where you are in a tight loop for a long time; but for most of the article it seems he is _almost_ saying something profound, but there is too much clutter and buzzwords around it. I know these abstract consultancies have a use, but they seem to target what managers and executives _want_ to hear instead of the truth.

e.g.: "The promises that were made to executive leadership about the latest technology are not coming to fruition quickly enough."

It feels like he then proceeds to talk about how management can get the developers "organized" to make sure they get the job done. Having a developer doing support for the day kinda sorta seems like a nice idea until you realize that "Isn't that what the manager is supposed to do? Understand his team and get what they need/negotiate with other teams so that they can just get their work done?" It's kinda like he's telling managers how to outsource their work to someone else. Pass the buck and live in a fairyland.

I know people who idolize Thought Works, Martin Fowler, Uncle Bob, and others in the "consulting set"-- but it seems like they fill a particular niche, and it isn't the phenomenal tech experts, it is more of the "how management views tech from an academic level and how we can get these interchangeable programmer cogs to get our project done w/ the least amount of effort". They rarely give hard advice, it is more of soft exposure to "new tech" and "here's something that works for some people, you might be that person". "We'd love to sell you on new tech that will be a silver bullet for all your problems"

In any case, I learned some interesting stuff from the article, and I do think it is a valuable read.

Re:Maximizing Developer Effectiveness by ownagefool on Saturday January 16, 2021 @10:20AM (#25802720)
Indeed.

The lack of hard advice is great for them because they're essentially never wrong but you'll also never fix the problem with the advice alone. Keeps the gravy train going; if they solved our problems with hard facts in blogs, we wouldn't need them.

That said, the advice itself is still pretty good if you have the chops to follow through, but I honestly don't think you can build the chops by hiring in the consultancy to tell you. In fact, it's actually a bad sign that you leadership both need obvious advice, and think they can enact change by hiring the consultancy.

The reality is, you'd probably have better results changing the leadership.

Re:Maximizing Developer Effectiveness by qwantim1 on Saturday January 16, 2021 @11:37AM (#25803319)
Asking for advice from a contractor is not bad.

Asking for leadership from a contractor is bad:

1. They don’t understand what you need or how to get it to you, but they sound like they do, and they look professional.

2. There are no great contracting options for something you can’t do yourself and that there aren’t requirements for.

Fixed contacts may start off looking good but they swap resources out and you end up incomplete or halfassed, overtime and maybe over-budget.

A renewable contract may blow really pretty smoke too and look like a high speed train, but that’s not what was needed, they never finish, or when it’s forced to completion, it’s incomplete or halfassed, overtime and over-budget.

If you don’t take care of your health on your own, you can’t expect a doctor to do that for you. Similarly, don’t expect a contractor to solve all of your team’s development problems, though some can give good advice or assistance.

Steps towards making yourself healthy may include exercise, eating better, adequate sleep, regular checkups, etc., while steps towards fixing your development team’s problems may include raising those to your leadership, own problems, foster trust, facilitate, and change your job if problems are not resolved.

Re:Maximizing Developer Effectiveness by ownagefool on Saturday January 16, 2021 @12:43PM (#25803800)
Maybe.

Funnily enough I was a contractor providing leadership and helping orgs for the last 5 years. I did my best to varying degrees of success because the leadership themselves would either let you run with it or not. My 1 man band is very different from thoughtworks though.

Now I am leadership and it's way easier to just make decisions.

Re:Maximizing Developer Effectiveness by qwantim1 on Saturday January 16, 2021 @02:36PM (#25804778)
Sure, there’re exceptions.

But if you don’t understand the requirements, choose to pay someone to figure it out, and they finger-paint your business, you may have been better off without it.

Nothing sells better than crap. By that I mean literally nothing, like you could sell emptiness more feasibly.

Re:Maximizing Developer Effectiveness by ownagefool on Saturday January 16, 2021 @03:52PM (#25805399)
Yeah, reasonble points.
Re:Maximizing Developer Effectiveness by stepbeek on Saturday January 16, 2021 @11:10AM (#25803120)
To be fair, they’re selling to those executives. It’s unlikely that devs on the ground have the authority to sign off a large consultancy bill.
Re:Maximizing Developer Effectiveness by piva00 on Saturday January 16, 2021 @08:11AM (#25801985)
In my current team (and my previous one from another company) we have what we call "goalie" duties. Each week one engineer from the team is responsible for answering inquiries, not necessarily they have to know the answer but they are the ones to be interrupted and handle accordingly.

It works pretty well, our devs are capable of assessing urgency to either bring it up on Slack, wait for the next stand-up or call to arms if it's something critical.

It improves rapport with stakeholders and other teams; it improves morale, it's predictable who will be interrupted during the week, alleviating that from the rest of the engineers. And as a side-effect it helps to force knowledge sharing over time.

Re:Maximizing Developer Effectiveness by jy2947 on Saturday January 16, 2021 @11:48AM (#25803393)
Isn't the typical responsibility of the manager or the team lead?

Inquire often is followed with more requests, if each developer serves as the weekly-speaker-of-the-team, will the external partner eventually figure out "John will do anything for us and Steve is mean"?

Re:Maximizing Developer Effectiveness by gregd on Saturday January 16, 2021 @10:32AM (#25802814)
This is actually a great idea and something I'm likely to bring back to my own teams!
Re:Maximizing Developer Effectiveness by ivandenysov on Saturday January 16, 2021 @06:27AM (#25801591)
In my current company we have a daily devops and dev duty. With current dev team size each gets around 3 duties per year.

Dev duty takes care of rollouts, crises, rollbacks, keeping an eye on performance and error monitoring. It's a great approach that works for us and allows every developer to get familiar with rollout process eventually, but I don't know if there are downsides for smaller teams or for projects that are split into several independent services instead of one monolith.

Re:Maximizing Developer Effectiveness by thargor on Saturday January 16, 2021 @09:06AM (#25802206)
How large is your team? 3 duties per year sounds incredibly low.
Re:Maximizing Developer Effectiveness by Ma8ee on Saturday January 16, 2021 @05:13AM (#25801331)
And how do you resolve this contradiction? Teach your employees that if you don’t want to be interrupted you better write good documentation. And have one dedicated team member each day responsible for supporting other teams. I think both of those are mentioned in the article, but it was a little a while since I read it.
Re:Maximizing Developer Effectiveness by leghifla on Saturday January 16, 2021 @05:27AM (#25801374)
"Teach your employees that if you don’t want to be interrupted you better write good documentation."

And reward them for doing it.

If your company do "360 degree" evaluations where your peers praise you for your quick answers to their questions, you are effectively incentivised to NOT document and instead be interrupted...

Re:Maximizing Developer Effectiveness by pferde on Saturday January 16, 2021 @10:51AM (#25802970)
One does not preclude the other. Your quick answers can come in form of sending them links to the relevant parts of the documentation you wrote earlier.

And if their question is not something that can be answered that way, you can improve your documentation so that next time the question is asked, you do not have that problem.

Re:Maximizing Developer Effectiveness by brokenkebab on Saturday January 16, 2021 @07:12AM (#25801755)
It's not something to be taught. For majority of devs an average working day is too short to do everything they theoretically should. So they make choices based on feedback/motivation which rarely favors writing good docs over writing more code. On top of that many good devs are simply unable to write comprehensible documentation because its very different kind of skills, or just because English is not their native.
Re:Maximizing Developer Effectiveness by cjfd on Saturday January 16, 2021 @05:53AM (#25801476)
I would be inclined to say that interruptions to help your colleagues should be accepted. Writing good documentation is actually hard and if you not willing to invest the time to do it well and to make sure the documentation can be found when needed you had better not write documentation at all.
Re:Maximizing Developer Effectiveness by postit on Saturday January 16, 2021 @03:20AM (#25800913)
Thanks.

This summarizes and completes perfectly the ThoughWorker bingo. They are always dreaming about the ultimate factory line for knowledge workers, but they don’t get much done other than blog posts.

Re:Maximizing Developer Effectiveness by Allenaz on Saturday January 16, 2021 @04:54AM (#25801254)
Last year I got to work on a codebase done from scratch by ThoughtWorks India, it was a convoluted piece of shit anywhere you looked... and, again, it was from scratch, they made a 1 year-old codebase feel like a giant ball of legacy spaghetti.
Re:Maximizing Developer Effectiveness by onethought on Saturday January 16, 2021 @03:33AM (#25800969)
Even by the HNs/SV measure of success they just got 700 million in funding and a 4.6 billion valuation... Just from writing blog posts apparently.
Re:Maximizing Developer Effectiveness by joana035 on Saturday January 16, 2021 @05:50AM (#25801458)
Well, sell each consultant hour ~100 and pay ~30. After the initial project implementation swap the whole team to India, move the existing people to another projects. Keep everyone in a cult like mindset, profit.
Re:Maximizing Developer Effectiveness by onethought on Saturday January 16, 2021 @08:06AM (#25801958)
Do you work somewhere that pays you exactly the same as the value you generate?

Are you saying ThoughtWorks bait and switch their customers? Do you mean without their knowledge? Or are they convincing them to accept dev teams from India?

Re:Maximizing Developer Effectiveness by kiplingsif on Sunday January 17, 2021 @03:45AM (#25809215)
Anecdotal but that's exactly what ThoughtWorks did for a company I work for, and then we entered protracted legal battles around Intellectual Property for the work/crap they had produced.
Re:Maximizing Developer Effectiveness by vasco on Saturday January 16, 2021 @04:04AM (#25801087)
I don't know about what they actually do because I've never interacted with the company other than reading what they publish. I have to tell you that if you apply the things they share, where previously you had a home-grown "process" or lack thereof, your engineering organization will produce better results and your engineers will be happier. I can't vouch for every single thing they ever wrote, but I think this style of rebuttal must be coming from someone who's had to work in disfunctional places with overbearing product management.
Re:Maximizing Developer Effectiveness by daniel-grigg on Saturday January 16, 2021 @05:36AM (#25801412)
The pendulum can swing too far both ways. Having worked for a startup that consisted of probably half ex-thought workers I can attest that yes some of the development processes and infrastructure we created were commendable. Some others were just absolutely frustrating. However I feel the only metric that’s really worth mentioning is that after a couple of years, there was practically no product to show of, not a single paying customer and the company slowly burned through its entire runway and faded to (more) obscurity. Yes I’m convinced that the ideological stances such staff took were directly correlated with the business failure. I think the only positive result was focusing on building an ivory tower meant everyone’s CV looked more impressive.
Re:Maximizing Developer Effectiveness by djrobstep on Saturday January 16, 2021 @04:16AM (#25801128)
I think you overestimate the sophistication of the average Dev shop. There are many orgs where "having a basic CI process" would represent a massive leap forward in developer productivity and happiness.
Re:Maximizing Developer Effectiveness by FlyingSnake on Saturday January 16, 2021 @04:16AM (#25801130)
This reminds me of this wonderful piece of art from Krazam; The Hustle.

[1]: https://m.youtube.com/watch?v=_o7qjN3KF8U

Re:Maximizing Developer Effectiveness by BossingAround on Saturday January 16, 2021 @06:01AM (#25801502)
His microservice video [1] is also pretty awesome!

[1] https://www.youtube.com/watch?v=y8OnoxKotPQ

Re:Maximizing Developer Effectiveness by balfirevic on Saturday January 16, 2021 @09:15AM (#25802257)
My favorite, Resolving Conflicts: https://www.youtube.com/watch?v=FDoH15ylAeo
Re:Maximizing Developer Effectiveness by lxe on Saturday January 16, 2021 @04:24AM (#25801151)
Why haven't I seen this before?

Why am I on Hacker News at 1 in the morning on a Friday (Saturday?)

Re:Maximizing Developer Effectiveness by posedge on Saturday January 16, 2021 @08:56AM (#25802182)
Probably better than being on Hacker News at 1 in the morning on a Tuesday.
Re:Maximizing Developer Effectiveness by sbdmmg on Saturday January 16, 2021 @04:58AM (#25801266)
Your reply is fun to read and I really enjoyed it. Of course the descriptions of the "typical day" in the original blog post is idealized. I suppose this idealization is there to make the contrast between the highly-effective day and the low-effective day. That is just the blog post.

Leaving aside this funny idealization and its comic interpretation of the blog post, in real life there are good habits and bad habits that can make a team work more efficiently and less efficiently. I have had first-hand experience with developers from ThoughtWorks, the consulting company behind that blog, and I can tell that they are indeed trying to apply those principles and strategies in their projects.

The fact that they are a consulting company gives them an advantage when trying to apply these principles. They only need to worry about the "small picture" of the project they're consulting on. They don't have to deal with all the "big picture" issues that might affect the employees working within the company they're consulting for (e.g. company politics, technical legacies, etc.) So IMHO perhaps some of these techniques and strategies to become a more effective development team are less applicable if you're working in $BIG_CO rather than in $CONSULTING_CO.

Re:Maximizing Developer Effectiveness by ericbarrett on Saturday January 16, 2021 @04:41AM (#25801210)
I belly-laughed for a good while after reading this, thank you!

I have had jobs ranging from entry-level phone tech support to Silicon Valley FAANG (E5 equivalent) to "the ops guy" at a New York startup. Like many here, I've been doing "DevOps" since before the term existed. Every job will have both kinds of day as described in the article. The only thing that matters is the ratio of good to bad, and how much you enjoy your work, your boss, and your coworkers.

Re:Maximizing Developer Effectiveness by jgwil2 on Saturday January 16, 2021 @08:43AM (#25802107)
"Psych" not "sike" please people! It's short for "psych out."
Re:Maximizing Developer Effectiveness by atomicnumber3 on Saturday January 16, 2021 @08:46AM (#25802128)
Huh, I always figured "sike!" was the slang version. I have to say, I feel like "sike" says something that "psych!" doesn't.
Re:Maximizing Developer Effectiveness by lxe on Saturday January 16, 2021 @01:04PM (#25803957)
Yeah that was intentional. It’s weird to write “psych!”
Re:Maximizing Developer Effectiveness by jgwil2 on Saturday January 16, 2021 @01:16PM (#25804082)
There was literally a TV show called "Psych" that was a play on the phrase. It is quite normal to write the word correctly. I think it would be very weird if the show had been called "Sike."
Re:Maximizing Developer Effectiveness by dxdm on Sunday January 17, 2021 @02:28AM (#25808937)
I think the way it's used these days, it deserves it's own spelling.
Re:Maximizing Developer Effectiveness by 14u2c on Saturday January 16, 2021 @03:32AM (#25800965)
Absolutely. Here's the thing though, in this hellscape you might as well take advantage, and if these units of work can be generated like so, then its quite easy to become a "top performer" by adjusting your commit habits.
Re:Maximizing Developer Effectiveness by gabereiser on Saturday January 16, 2021 @04:03AM (#25801084)
You could always be the one to squash merge said unit of work and put your name as the committer. You automatically become a 10x dev. /s
Re:Maximizing Developer Effectiveness by lxe on Saturday January 16, 2021 @03:33AM (#25800970)
I keep my github squares a deep shade of green.
Re:Maximizing Developer Effectiveness by elliottkember on Saturday January 16, 2021 @02:57AM (#25800840)
Thank you for reminding me to read more fiction.
Re:Maximizing Developer Effectiveness by maxwelljoslyn on Saturday January 16, 2021 @03:28AM (#25800953)
> It gives me a thumbs up and discards its human shell to fade back into the ones and zeros.

Me saying goodbye to the bus driver before walking into the office.

Thanks for writing, 'lxe.

Re:Maximizing Developer Effectiveness by ggambetta on Saturday January 16, 2021 @07:22AM (#25801795)
Excellent post, thank you! I loved "spherical devops in a vacuum" :)
Re:Maximizing Developer Effectiveness by 2StepsOutOfLine on Saturday January 16, 2021 @03:55PM (#25805421)
This comment felt like the beginning script for this video: https://youtu.be/_o7qjN3KF8U
Re:Maximizing Developer Effectiveness by simonebrunozzi on Saturday January 16, 2021 @03:53PM (#25805407)
Upvoted, of course, and also wanted to say that you made me smile, almost laugh. That's how good your writing and wit is.
Re:Maximizing Developer Effectiveness by js8 on Saturday January 16, 2021 @07:57AM (#25801916)
I think there is this duality in SW development that some people tend to believe in, that there are two types of work, one highly creative, like product or architecture design, and then the mundane one, like coding and testing. (I actually realized this reading a recent HN post: https://news.ycombinator.com/item?id=25775872)

I don't subscribe to this, I think the work is ultimately very similar in creativity (just different skill set), both on high and low level. If something seems mundane, it is either a sign that there is lots of hidden entropy that you failed to capture (and thus risk that the high level understanding is wildly incorrect), or it means that we are doing things conceptually wrong (with more effort than required), but we don't know how (and so there is potential for innovation).

And from that duality is derived the idea, that if only we can perfectly specify the mundane work (for instance through "acceptance criteria"), it's just a matter of getting enough bodies to do it according to some grander plan. From this misconception derives the history of software development methodologies.

So originally, people thought, this duality is the same as in building a house, you have an architect, he does the design, and workers (coders) will build it. So the waterfall was born, where the emphasis was on the plan, and it was also the weak point, because in the real world of SW development, it turns out, the actual implementation influences the plan (so the architect cannot just throw it over the wall, as they say).

Then, from the disappointments, Agile movement was born, pretty much out of the idea that all development work is creative, and it cannot be easily formulated/predicted, so we basically need to iterate quickly and hope for the best. Just treat everything like research.

But, as it happens, people promptly misunderstood this (where are my metrics now??). Instead of understanding that the belief in the duality itself is the problem (a kind of wicked problem, really, because it can manifests in many ways), they looked at superficial recommendations of "Agile practices" - Scrum rituals, "embracing change" and foregoing proper planning, etc. (For me, good summary of this discussion is http://steve-yegge.blogspot.com/2006/09/good-agile-bad-agile... and https://simpixelated.com/two-year-work-retrospective)

One can draw an analogy to this duality in other industries, it's a problem older than software. It seems that with technological and process automation, other industries are actually becoming more like SW development (aka "software eats the world"). So elsewhere, this belief in duality gave rise to Taylorism (https://en.wikipedia.org/wiki/Scientific_management), and the rejection of the duality gave rise to Demming's philosophy (https://en.wikipedia.org/wiki/W._Edwards_Deming) and the related management methods (which were, again, misunderstood, I am sure). There the fundamental notion coming from the duality is that it's the management (or anybody else not doing the actual production job), not the workers themselves, to decide how to effectively organize it.

And still, to this day, some people intuitively cling to this duality, and try to apply Taylorism instead of something like Kaizen or Kanban to SW development (and certainly not only that). So you have JIRA tickets and people beancounting story points..

Re:Maximizing Developer Effectiveness by analog31 on Saturday January 16, 2021 @12:44PM (#25803809)
I think that complex organizations tend to develop caste systems. The caste hierarchy could be arbitrary, or based on imaginary metrics such as being "closer to revenue." It could have some basis in fact, for instance doctor hours are more valuable than nurse hours, which are more valuable than patient hours.

The upper castes have to be responsible for the work environment, otherwise it degenerates: The best people in the lower castes switch jobs to join a higher caste or a company with a better caste system. Or they unionize, either formally (like nurses) or informally by forming silos. Thus the castes become self fulfilling.

As an aside, one thing that HN has taught me, reinforced by this thread, is that I would not have survived in a high throughput coding environment, and am glad I didn't steer my career in that direction, though I love programming. I don't have the self discipline, and I'd have burned out quickly.

Re:Maximizing Developer Effectiveness by gadrev on Saturday January 16, 2021 @01:25PM (#25804148)
I can only applaud this.
Re:Maximizing Developer Effectiveness by Geminidog on Saturday January 16, 2021 @08:02AM (#25801933)
Martin fowler is the one true God of this universe.