11 ms·
Magpie Driven Development (MDD)
- Netcob 5y agoCommunication issues aside, good luck finding developers who aquired all the necessary skills to work in software development without this mindset. Of course it would be great for a company to be able to hire people who only learn new things on weekends and then 100% commit to and derive all their motivation from delivering the product, but I think that's quite rare...
- vaughandroid 5y agoI'm not a fan of this post as it seems to be pointing the blame at the wrong thing: the problem isn't the shiny new thing, it's the environment that allowed the situation to develop: people working in isolation, key decisions being made by individuals in private, lack of oversight. There are plenty of arguments in favour of allowing teams to use shiny new tech. Done responsibly, it can help with engagement, job satisfaction, retention, and recruitment.
- borracciaBlu 5y agoI've been witness of developers not working in isolation, with clear specs and requirements, who knew what was the expectation and still use the tech they preferred. I would say they were unprofessional and selfish. Not great as cultural fit neither. Discipline should came first. Imagine you go to a restaurant and order a pizza and instead you receive sushi just because the chef wanted to learn a new cooking style..
- Cthulhu_ 5y agoBut, as a company you should also focus on your own bottom line - working, stable, predictable, reliable software, a codebase you can still hire people for ten years down the line. Java and C# are safe bets. It probably won't get you the hip polyglot hype developer type, but I'm not convinced there's any company that thrives on those. Maybe for the POC or MVP, but long term you need a reliable tech stack. I mean take Google; their backbone is/was C++ and they're moving towards Go, which is even more boring than C++ is.
- mamcx 5y agoConsider it lucky Magpie is using Rust. Imagine if instead rewrite it in JS with they new shinny frameworks...
- dhruvmittal 5y agoI think a slight improvement over this model is to have a forward-looking CTO/Lead Developer/etc. who incorporates new technologies into the overall plan with sane fail states. This allows the overall technology stack to remain fresh, the developers to stay motivated and current, manages the overall amount of legacy code, while also managing incurred risk effectively. It can also lead to company investment in those new technologies, i.e. training time/budget or conference tickets (depending on what's relevant). Tl;dr: put your magpies on the top!
- nodejs_rulez_1 5y agoAnother one of those articles... Please tell us how you incentivise your staff to deprioritise their skill growth in favour of your business? I hope to hear things other than "salary, benefits and bonus" but they have to be monetary.
- handrous 5y agoCapitalists and the c-suite: Nepotism and self-dealing all day every day, constantly directing entire acquisitions to bail out a buddy's or a kid's failing business, or making companies they have control of rent buildings they personally own or whatever Software developers: Act in their own self interest in a minor way that's not perfectly in line with he company's interests Business bloggers: Hey now, cut it out developers! What a bunch of low-attention-span babies you are.
- rocqua 5y agoWhy do they have to be monetary but not based on salary or bonuses?
- nodejs_rulez_1 5y agoBecause you want people to care about business same way as the owners do, yet when the firing starts they will simply be let go. Another option is to openly state during hiring that new technologies and approaches are not welcome.
- UncleEntity 5y agoBecause the business pays them to do a specific job which doesn’t include them training for their next job? Is it really that common that people expect their current employer to subsidize their “skill growth” when they know they are just going to hop to another company in the near term? Not judging —- just asking as an outsider looking in. —edit— Huh, just downvotes so I assume it is expected to be able to train yourself on company time…
- TeMPOraL 5y ago
- nivertech 5y agoMDD - Migpie Driven Development HDD - Hype-Driven Development BWDD - BuzzWords-Driven Development HNDD - Hacker News-Driven Development RDD - Resume-Driven Development CVDD - CV-Driven Development
- EdwardDiego 5y agoWhen I was teaching myself to code, I frantically chased every language that was getting hype on proggit, back when it was worth reading. Ruby! No, wait, Haskell! No, wait, Erlang! I thought I'd never catch up to the industry. While I learned a bit from Haskell and Erlang, I eventually realised that no-one hypes the 'boring' languages that people are using to get shit done every day.
- jamesfinlayson 5y agoIt's kind of amazing that you can mostly get by with the same 10 languages that were popular 10 years ago.
- Cthulhu_ 5y agoI've been going through some developer profiles yesterday (we're looking for a full-stack developer, Go + TS + React), and the amount of people that just blurted out every language and technology they've ever worked on was... a lot. People need to focus their CVs a lot more. Write the one or two languages you have the most experience in / with, and the one you really want to work with at the top - you don't need to mention you know (x)html(5), css, sass, less and scss - if you mention you have experience as a web developer I will assume you know these things and can learn the rest easily enough. And stop mentioning things you sniffed at in school or on your friday afternoon, if you haven't built products in it, it's not really important.
- osigurdson 5y agoEDD - Epoch Driven Development To use precisely the tools and technologies that the project started with until the end of time.
- 5y ago
- can16358p 5y agoNot to advocate any of it, but if trying out that new shiny language creates real motivation for the developer (and of course, suitable from a business/maintainabity etc perspective too), let them. Of course you should have communicated more with the developer though to see what they've been working on.
- nottorp 5y agoCan't blame someone who tries something else instead of .net. Going back to my current legacy .net project that i hate. Except there's no way I can stealth port it to rust or anything else so i'll just try to get the changes over with.
- DeathArrow 5y agoLegacy .NET is crap. New .NET is pretty nice on the other hand.
- nottorp 5y agoI believe mine was started in VB pre .net :)
- jaywalk 5y agoOh. Oh no. I hope you've at least had exposure to recent, proper .NET code. Don't judge the platform based on that project.
- whizzter 5y agoWhile old VB was fun for whacking together things it's not really stuff one would want to maintain in the long haul. Right now I'm sometimes spending time maintaining something for a DCOM based semi-monstrosity and that does suck even if I've managed to clean out some old warts, luckily I'm also doing some more modern .NET stuff and that isn't too bad at all actually.
- darkmatterrat 5y agoHowever the people building stuff in new .NET are the same people building stuff in old .NET for the most part and you get all the same wonkyness just in .NET core.
- fmajid 5y agoI stopped reading when the author wrote with a straight face that .NET would help with their migration to Linux. That said, new technology proof of concepts should always be done on non-critical systems first, and certainly not sprung as surprises.
- konschubert 5y agoIf your senior dev manages builds a whole service in another language and you learn about it after they're about done, I think there are bigger problems than just the choice of the language.
- GVRV 5y agoYeah, this was surprising to me too. Maybe I've just never worked in organisations big enough where you can sneak off to rewrite services using a surprise programming language without any discussion about it.
- Cthulhu_ 5y agoI'd be inclined to fire them for not doing what they're being paid for. I mean don't get me wrong, every company should have allotted time for experimentation, but not to this degree. And it should not be adopted either, that would be sunk cost fallacy. If they wants to do Rust so badly, that's fine but they're now a trainer and need to teach the language to everyone involved and share responsibility of the new codebase. And if the other developers don't want to, then the developer needs to find a new job real fast.
- clncy 5y agoI also like the term Resume Driven Development (RDD) to describe this. Choose whichever technologies improve the developers resume the most.
- loulouxiv 5y agoThe technology most suited to improve one's resume will be the one most in demand on the job market, and therefore also the most difficult skill to hire for...
- tlackemann 5y ago"Let's use GraphQL"
- can16358p 5y agoLiterally happened to me. Our backend guys decided to switch to GraphQL from perfectly functioning REST. Result: release postponed by 4 months and 30% of the client side had to be rewritten. The whole client logic relies on Redux state as the single source of truth and I always fetch objects fully anyway, so it even makes less sense to switch. But again, backend guys being backend.
- jarcane 5y agoI've begun to recognize "unnecessary GraphQL" as a code smell, and one usually indicative of wider architectural problems in a project. I have yet to be wrong in immediately steeling myself for the worst the second I see the word.
- corpdronejuly 5y agoWhat would you consider to be "necessary GraphQL"
- jarcane 5y agoAre you Facebook?
- jamesfinlayson 5y agoPretty much this - I can see why Facebook use it but I wouldn't have gained much from GraphQL in any of my jobs.
- dgb23 5y agoNothing. But the utility it provides is a unification layer for heterogeneous data sources to enable ad-hoc queries on the consumer side.
- xyzal 5y agoI am guilty. Also, I very much enjoy it.
- oqbrya 5y agoThere is nothing wrong with learning new technologies and trying new stuff. If your organization prohibits this I don't think it is a good place to work. What you call "MDD" sound to me more like a planning or communication issue between the project manager and the developer.
- littlecranky67 5y agoLearning is one thing, putting a production service into place in a language no one else is familar with and without permission, is not okay.
- TeMPOraL 5y agoHah. 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.
- deepsun 5y agoI'm a Magpie. And I've left two other teams where it was hard to persuade managers to learn shiny new stuff on the job. Couple of points OP missed: 1. To prove that the new Rust service working fine, Magpie will stay extremely motivated, put 2x hours into it. You have to literally tear them off a keyboard. Now you got a devoted Owner, who is willing to take more responsibility of a project, isn't that wonderful? 2. Every rewrite serves as a good security review. Old unnecessary permissions will get abandoned, and only required accesses will be migrated. If Magpie is experienced and responsible, they will make it more secure than it was. 3. Every time I've seen a project rewritten (regardless of technologies) -- it became better. But only big companies can afford it. Magpie did it for you for free. 4. Motivation (aka pay less). If you see your team is bored, and updating their resume -- allow them to rewrite something on a tech stack they choose (and you can postpone promos till next year).
- deleted 5y ago[deleted]
- InsomniacL 5y ago1. 2x hours booked against a project with a cost code. 2. There is no security review if only one person knows that language. As well as that one person being new to that language. 3. mostly agree but as you state, not relevant to new technology decided upon by someone on a whim. 4. Do you really believe creating sections of the tech stack that only a single person is able to maintain will result in you not having to pay these staff as much? Those staff who you now have a critical dependency on and they know it?
- inetknght 5y agoTo your point #4: Do you really think that developers shouldn't be paid what they're worth? Or that developers should hold down their worth so that you can pay them that much less?
- Cthulhu_ 5y agoBut migrating to a more niche technology where the existing one was fine is artificial inflation.
- bovermyer 5y agoI see several comments here defending new-shiny syndrome in the context of improving the developer. From a business standpoint, that doesn't make a ton of sense. Development is meant to complete the business's objective of solving a problem for humans. It's not meant to make the developers enjoy their work more (though that's a nice bonus when it happens). Chasing the new shiny puts the team in a perpetual state of re-learning how to do a known process. Maintaining and extending existing code in a known way is more predictable and more cost-effective.
- handrous 5y agoYet, if the developers who successfully mislead their employers into misguided tech choices have notably better careers, on average, it's exactly what we should do. And we shouldn't feel a bit bad about it unless we're in one of those rare roles where lives are on the line. > Development is meant to complete the business's objective of solving a problem for humans. Sure, but every layer of management is making decisions constantly, including about what to direct development to do, that are in their own personal interest rather than the business' interest. If they can do that, the peons can (and should) too.
- bovermyer 5y agoThis strikes me as very cynical. In my own life experience, the majority of my employers have genuinely wanted to work together to improve things for a large group of people. I have never worked for an employer where it was obvious that everyone was only out for themselves.
- deleted 5y ago[deleted]
- inetknght 5y ago> I have never worked for an employer where it was obvious that everyone was only out for themselves. I guess you mustn't have worked for very many employers. Or at least not in the USA. The sentiment is endemic where I am in Houston, TX and previously in CA
- what_is_orcas 5y agoI've sort of been dealing with this at my day job, except it doesn't come from other developers, it comes from management. Every few years, a new Head of Engineering comes in and says something like "let's use $TECHNOLOGY for this project" with the expectation that it will make the company more effective, I think. It's been GraphQL, microservices, clouds ("can we do this with Lambdas on AWS?" when we don't have any other significant infrastructure on AWS), and a bunch of other things. On one hand, it's good for me to dabble in a lot of this stuff (learning the basics of GraphQL on company time helps my resume, after all), but I end up pushing back most of the time ("I don't think this is a great use-case for GraphQL. From what I understand, $X and $Y would be reasons to use it, but for this project, REST makes more sense because of $Z"). Meanwhile I'm just trying to get my work done and not make it a hassle. If we had a good reason to use GraphQL (or any of the other things management suggests), I'd be into it, but I don't want to be wrestling with fitting square pegs into round holes for no benefit.
- mywittyname 5y agoThis manager might be optimizing for the environment they work in. If the expectations are the Head of Engineering introduces Cool New Technology to the company, then that's what they will push to do. If you report directly to them, it might be worth a conversation to frame your team's work in a way that sells it as Cool New Technology that is being built.
- what_is_orcas 5y agoOh certainly. I have a pretty good relationship with that manager, actually, and that's more or less the framework we use to sort of compromise. He gets his buzzwords and I get to get my work done. I enjoy learning new things, don't get me wrong, but sometimes a CRUD app is just a CRUD app and trying to shoehorn other stuff into it makes it more of a pain in the long run. I guess I just wanted to illustrate that this isn't only an IC issue; management can engage in MDD too.
- Cthulhu_ 5y agoOne thing to consider is that $TECHNOLOGY may not be picked or presented for its technical or performance benefits, but purely for hiring. And marketing, because hiring nowadays is 90% marketing, and in that most of it is down to "you'll get to use this cool technology". A LOT of job adverts in the past years that I looked at had "blockchain" and "IoT" sprinkled in, not because they did anything with it, but because a lot of developers wanted to do something with those. Because "Java, Postgres, React" don't excite anyone anymore.
- llimos 5y agoGuilty of this. And I encourage my team to do it too. You need to align incentives. The doing it in secret part is a far bigger problem.
- mkl95 5y agoMagpie Driven Development is imho a symptom of Dead-end Driven Development (DDD). Dead-end Driven Development happens when the majority of a developer's time is spent working with technologies that hurt their career. The way you end up like this is often because the projects you were initially hired for have reached a maintenance state. Instead of rewarding developers who have successfully completed the tasks they were initially hired for by assigning them tasks that benefit both their career and the company's goals, developers who meet management's expectations are often assigned to legacy projects that are riddled with obscure bugs, strange architecture, and bad choices. The end goal of these tasks is often to upgrade a system that uses ancient technologies in order to ease some customer's mind. In this situation burnout eventually creeps in and the engineer faces two choices: either they start doing something that puts their career back in the right track (MDD) despite the consequences, or they find another job that improves their situation. In the previous economy I would expect most people to pick option 1. In the current economy I'd expect an overwhelming majority to pick option 2.
- Cthulhu_ 5y agoWhile I hear what you're saying, if everyone was like that, who would be left to maintain existing systems? In my limited experience, it takes up to 3 years to go from the start of a project to it being in a maintenance state. A lot of developers (consultants, self-employed, etc) have jumped ship before that, often around the two year mark. So there's two - three years of work, it's 90% done, it's nearly ready to go into production... then what? Who does the actual work? Who does the maintenance? I think anyone that picks a technology stack and architecture should stay long enough at a company working on it until they fully understand the consequences of their decisions. Too many people jump from one hype technology to the next, one greenfield start of a project to the other, but never have to deal with their own code and decisions ten years down the line. And you KNOW a lot of software has a lifetime of at least a decade, sometimes / often more. There's critical systems that are still running with the decisions of a previous generation of developers, people who are now being asked to come back from retirement to maintain their old systems. You can't call yourself a senior (or serious) developer if you've never had to deal with the consequences of your own actions.
- grayclhn 5y agotbh, the only problem I have with the approach in the article is that they’re not being strategic about it. I’ve informally had a, “one cool idea per project,” rule in the past. So if the project itself is cool, stay conservative with implementation choices, etc. But if the project is routine, you get to experiment a little.
- politician 5y agoIt takes a certain culture and way of working for staff to be able to safely experiment with new technologies or new product ideas. I prefer to build teams where learning and experimentation are aligned with business objectives. However, this approach doesn't work for everyone or for every business. There are many successful risk-averse businesses staffed by folks working ticket queues. In the end, it's about the culture. An autodidact will struggle in a ticket mill. A ticket puncher will struggle in a skunkworks.
- spc476 5y agoIn my case, it wasn't MDD. I was tasked by my manager to take a look into this whole SIP thing. So I started reading up on it and writing code in Lua (using LPEG) as an exploratory project [1]. Unbeknownst to me, my prototype was put into production by said manager. Sigh. I'm still the only person who really knows Lua at the company. [1] I used Lua to write the testing programs for the product.
- AussieWog93 5y agoI really like the metaphor of a Magpie, especially since they start swooping once people get to close to their babies!
- ChrisMarshallNY 5y agoI’ve been writing shipping software for my entire adult life. In my experience, shipping requires compromise. For example, I have found it to be a very bad idea to schedule a ship project, based on shiny. It’s always a good idea to step back from the precipice, a bit. The last two years at my last job, we were assigned to work with a startup, staffed by awesomely brilliant folks, to develop a particular kind of software, in one of the new, customized, LLVM-spawned, languages. I won’t get specific. It did not end well. The devil is in the details. It was a great R&D project, but a lousy ship project. The app I’m currently developing is being written in Swift (shiny), but using UIKit (b o r i n g), and traditional MVC (b o r i n g), instead of SwiftUI (shiny), and MVVM (shiny). SwiftUI was a thing, when I started the project, but it was still pretty raw, and I had barely started to work with it. The servers are written (for the most part), in PHP. They work great. If anyone has any doubts about the viability of PHP as a server, they should check out the “fishtank graph.” That was the graph that was released, recently, that showed PHP is several orders of magnitude more prevalent in Web server code, than any other language. I call it the “fishtank” graph, because PHP is this line along the top, and every other language is represented by lines that look like gravel, on the bottom of the tank. I may have been able to do this enormous app in SwiftUI, but there was no guarantee. There was no doubt, whatsoever, that it could be done in UIKit. If I write in UIKit, I write MVC. UIKit was designed for MVC. I’ve found that it’s always a good idea to use a tool the way it designed to be used. SwiftUI is good for PoP, KVO, etc., and different event-handling models. It’s coming along great. The quality is amazing, as is the UX, and the performance. I plan to ease into SwiftUI, by writing SwiftUI versions of my various UIKit widgets. That will be a much better way to learn up on it.
- alexjplant 5y ago> MVVM (shiny) Microsoft tried to make this a thing 15-ish years ago with WPF/Silverlight ... is it experiencing a renaissance? Unfortunately I don't recall too much about its merits (or possible lack thereof) since the last time I read about it I wasn't sufficiently experienced with software architecture to understand what it brought to the table.
- ChrisMarshallNY 5y ago