Skip to main content

Motivated Developers Do Valuable Things (Mostly)

I have a provocative claim that people do what they want in a given software organization and then play the game of scrum or some similar established process. A more nuanced way of putting that is that we (developers) are incredibly easy to sidetrack from the commonly agreed "most important TODO items." Sure, we follow the abstract, larger vision of a given product, but the more granular the level, the more variance there is in people following the predetermined issue list.


When it is written or said out, all that does not seem that provocative. It is actually written in agile process documentation, but not in those words. Agile process talks about "requirement volatility" which can be seen as a similar thing I am talking about.

Given most employees do what they want, how do organizations keep on top of that?

Now, for what might seem like a continuation of stating the obvious: meetings and issue trackers are vital tools for monitoring team activities. Motivated individuals naturally tend to do impactful work from their perspective, but that may not hold collectively, thus highlighting the necessity for these tools.

The naivete I have grown out of is believing that meetings are unimportant. Meetings are not just a formality; they are, more often than imagined, more crucial than writing code. They are one of the most valuable activities a company engages in. Without meetings, the organization is likely solving such trivial issues that they cannot pay software engineering-grade salaries.

Indeed, the world is full of poorly organized meetings. It's a common theme across countless business self-help books, each proposing ways to inject discipline into them. This reminds me of the nature of coding: a portion of what we write is incredibly valuable, driving significant revenue. However, let's be honest, a good deal of it is less impactful, often addressing imaginary problems (my favorite blog post of the year thus far).

I still grind my teeth every time a meeting is called. I must emphasize that it stems mainly from my predisposition rather than the organizers' insensibility.

A piece of insight that struck me recently touches on meeting participation. If you're consistently passive in meetings, or never initiate discussions, you're likely missing out on a crucial aspect of your role. Your value in an organization is not just about the current feature you develop; it's also about your ability to contribute to broader discussions and decision-making processes. Do not expect a bump in salary if all you can show are green tiles in GitHub.

Turning to issue trackers, let's talk about Jira. I can't believe I am writing this, but Jira is actually... good.

Yes, really!

In my current project, we're using an alternative tool that, despite its sleek UI and speedy tab-focus-to-new-issue rate, needs certain features that seasoned developers like us have come to appreciate in Jira. While our processes could be optimized, switching tools or methods feels like a distraction from our primary goal: refining and prioritizing tasks.

Comments

Post a Comment

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...
Post a Comment
Read more

PydanticAI + evals + LiteLLM pipeline

I gave a tech talk at a Python meetup titled "Overengineering an LLM pipeline". It's based on my experiences of building production-grade stuff with LLMs I'm not sure how overengineered it actually turned out. Experimental would be a better term as it is using PydanticAI graphs library, which is in its very early stages as of writing this, although arguably already better than some of the pipeline libraries. Anyway, here is a link to it. It is a CLI poker app where you play one hand against an LLM. The LLM (theoretically) gets better with a self-correcting mechanism based on the evaluation score from another LLM. It uses the annotated past games as an additional context to potentially improve its decision-making. https://github.com/juho-y/archipylago-poker
Post a Comment
Read more

"You are a friendly breadwinner"

A recent blog post by Pete Koomen about how we still lack truly "AI-native" software got me thinking about the kinds of applications I’d like to see. As the blog post says, AI should handle the boring stuff and leave the interesting parts for me. I listed down a few tasks I've dealt with recently and wrote some system prompts for potential agentic AIs: Check that the GDPR subprocessor list is up to date. Also, ensure we have a signed data processing agreement in place with the necessary vendors. Write a summary of what you did and highlight any oddities or potentially outdated vendors. Review our product’s public-facing API. Ensure the domain objects are named consistently. Here's a link to our documentation describing the domain. Conduct a SOC 2 audit of our system and write a report with your findings. Send the report to Slack. Once you get approval, start implementing the necessary changes. These could include HR-related updates, changes to cloud infras...
Post a Comment
Read more