4 ms·
Hah. The author is missing the point of their own example: > Investigating, you find out that there’s no compelling business reason for the component to be wri
by TeMPOraL 5y ago
Hah. The author is missing the point of their own example:
> Investigating, you find out that there’s no compelling business reason for the component to be written in Rust. Not much of a technical reason either. It’s just that the developer involved really wanted to learn the Rust language and related ecosystem of tooling, and they figured this work project was the best place to do that learning.
> Magpie Driven Development is when you have developers who want to use something new for no better reason than it’s shiny and fun.
That developer didn't use Rust because "it's shiny and fun". They did it to learn. Couple possible reasons:
1/ Mental hygiene. They're bored out of their mind with their current tech stack, and picked something different to prevent burnout.
2/ Principal-agent problem. They wanted to learn the new language, perhaps to use it for a side project, and opted to do some of the learning on company time.
3/ Professional development. They want to "sharpen their saw" and/or keep up to date with industry trends, and opted to do it on company time.
4/ CV padding. They consider changing the job, and are trying to gain some marketable experience.
5/ In-house improvements. There's a need for a change of tech stack in the company, of which the author of this article isn't aware. The developer did a project in new technology as a part of moving in this direction.
We can debate professionalism and ethics of any of those reasons as applied to a specific case. But I don't think classifying such situations as developers chasing shiny things is productive or insightful.
- deleted 5y ago[deleted]
- bobthepanda 5y ago> In-house improvements. There's a need for a change of tech stack in the company, of which the author of this article isn't aware. The developer did a project in new technology as a part of moving in this direction. Certainly something that would probably get messaged at all levels of the company, not something you surprise drop on the rest of your coworkers and pull them kicking and screaming towards.
- marcosdumay 5y agoYou mean, it's something for management to decide, and the technical staff has no role on learning the costs and benefits of each option? If a developer could create it alone, without anybody noticing, the company can replace it again if they learn it's not a good technology.
- bobthepanda 5y agoit sounds like the developer is in a team of developers. If someone else on the team wants to shake up literally everything with no consultation with the rest of the team on whether or not it's a good idea, now everyone else is getting dragged along for the ride without much consent, because now it has to be maintained and kept up to date. And it may not even be a good idea; individual developers are not infallible.
- marcosdumay 5y ago> literally everything A service, isolated from the rest of the code, fully written in a week by a programmer without experience on the language. If that shakes literally everything, your place has a problem. And it's the kind of problem a single developer or small skunkworks team can help you move out of, if they are given some freedom to experiment with architecture and settle on some good guidelines.
- bobthepanda 5y agosomeone learning a language on their off time does not mean that everyone else has the off time to do a language. presumably the one engineer won't be the only person touching it, and they'll have vacations and days off where someone else will need to assist, and they'll probably leave the company at some point (especially if it's in service of CV polishing). now everyone has to learn the special new language if the new service is supposed to be a productionized thing. the least you could do is ask the rest of your team first. what's so contentious about working with your coworkers?
- 5y ago