5 ms·
Not sure what the articles point is? That you shouldn't write an application if you can use an off the shelf tool? Who does that? I'm paid to write code becaus
by alkonaut 10y ago
Not sure what the articles point is? That you shouldn't write an application if you can use an off the shelf tool? Who does that?
I'm paid to write code because someone wanted an application. I don't think I could tell the customers who buy our application that they should learn some bash or excel and solve their business problems?
I assume under some rare circumstances a developer isn't faced with writing an app (site, CAD program, OS, ...) but instead to solve some business problem internal to a business - then you have the option of not writing code.
- Swizec 10y ago> solve their business problems Your job is to solve business problems. You happen to use code as the tool to do so because it lends itself to building better, more reliable, more scalable solutions. Nobody pays for a lump of code, they pay for a tool that solves a problem they have.
- Beltiras 10y agoIncidentally this very often comes about by writing code. Or installing new systems. There's a strange broken circularity to that blogpost.
- blub 10y agoDepends really. A surprisingly large number of organisations don't seem to be equipped to handle business input from the development staff or any kind of "productivity multiplier" contributions. E.g: making the team more efficient, reducing signup friction, fixing UX annoyances, inventing a new feature or product, improving security practices, reducing defect rates by introducing CI/static analysis/whatever. In this case the job of the developer will be to write code and it doesn't make sense to pay high salaries because the ROI is not there. This leads to the situation where very good developers aren't paid good salaries because in such a company they are literally not worth the money.
- alkonaut 10y agoThe customer pays my employer for a solution and my employer pays me to create it but I get your point. I just didn't agree with the argument of the article in general - most of devs can't use a piece of shell script to solve a problem they would otherwise code. Simply because we work within the boundaries of a single product such as a large desktop application. I don't solve my employers business problems, I solve the customers business problems an the only way to do it is to code it in the application.
- douche 10y ago> Nobody pays for a lump of code, they pay for a tool that solves a problem they have. A more cynical situation, which I have seen all too often, is that they pay for the line items on the RFP. Whether or not those features will ever be used or are in any way beneficial.
- TeMPOraL 10y agoExcept there are two common problems here: - NIH. If you think it's programmers who primarily suffer from NIH syndrome, check again. Just how many times you end up writing something that's already done because your bosses insist they must have an in-house solution? - Nonsolving a nonproblem. A lot of code we write is meant to solve a problem that doesn't really exist, is created by stupid decisions higher up the chain, or sometimes just shouldn't be solved in the first place (e.g. tools facilitating an unethical business model). So yeah, I'm often paid to write code - because the decision that code must be written is made by people above me.
- OpenDrapery 10y agoSometimes, as a developer, I ask higher level questions about the business. Who is the customer? What problems do they have that we are trying to solve? How does this business make money? How are the executives measured? These are questions that are relevant if you want me to add value in a non code monkey way. But, sometimes, when I ask these questions, I get looks that say "You're paid to write code, so stop asking non code questions." Or maybe I'm just projecting.
- leepowers 10y ago> Nobody pays for a lump of code, they pay for a tool that solves a problem they have. Of course they're paying for code. They're paying for code that does something useful, and which may or may not produce value for their business. You can't separate the two.
- cookiecaper 10y agoI think his point is that engineers tend to favor complicated solutions, and that they shouldn't do that. Every line of code you write or modify is potential technical debt that you'll have to own. The author appears to indicate that this is bad, and also appears to recommend making wider use of pre-existing solutions to prevent it. That's fine as far as it goes, but it's a simplification. The piece does feel incomplete in that it doesn't discuss the incentives behind the decision to "write code" or not. The simple fact that we always seem to come back to is that once you learn the basics, good engineering just comes down to good judgment, which is only gained through years of dedicated trial and error. Is it better to write some glue code to bounce data between 8 different extant programs and make final transformations or to write your own program that handles the process soup-to-nuts? The answer is now and will always be "it depends" (and quite frequently, it involves elements of both). We need to make sure that the social incentive structures align with the engineering goals (i.e., don't tell someone that if they make something stable and low-maintenance, they'll unemploy themselves) and then we can trust people to do good, iterative work.
- OpenDrapery 10y agoEvery line of code you write or modify is potential technical debt that someone will have to own. With the turnover rate in this industry, I'm not sure anyone plans to be around when the monstrosity that they wrote starts to become a maintenance nightmare.
- deleted 10y ago[deleted]
- trprog 10y ago>That you shouldn't write an application if you can use an off the shelf tool? Who does that? Lots of people? Everyone who ever bought, downloaded or otherwise acquired any software not written by themselves?
- alkonaut 10y agoYes, sorry if I was unclear: that was my point. When I as a developer is paid to do something, usually someone (my manager, the customer etc) has already decided that whatever problem there is can't be solved without making a program specifically for it.