4 ms·
Here's the big secret about the tech industry: arbitrary technology is exactly what you want for your project. It doesn't actually matter. Any inherent differ
by nostrademons 11y ago
Here's the big secret about the tech industry: arbitrary technology is exactly what you want for your project. It doesn't actually matter. Any inherent differences in productivity are dwarfed by the effects of being emotionally invested in your work and having lots of other people emotionally invested in the outcome. Besides, regardless of what you choose, if it becomes successful it will be rewritten multiple times by multiple groups of people, and the effect of having them emotionally invested in their work will far outstrip any inherent differences in technologies. So pick whatever you want, and then let your employees pick whatever they want subject to the constraint that groups who work on the same codebase better agree on the same technology.
- lordnacho 11y agoSomeone needs to tell this to recruiters. There's too many job adverts for jobs that any programmer could do in any language, but they WANT a Java/c#/etc guy.
- arethuza 11y agoI don't think it's recruiters - hiring managers want someone who can "hit the ground running" so look for an exact match between the technology involved in their current project and the experience of an applicant. The same managers then wonder why their teams are reluctant to work with technology that isn't "hot"....
- solipsism 11y agoCan't really blame them when it's part of our culture to start looking for a new job once we've been there a year, why would they want to invest significant amounts of resources into you? Then again, maybe you can blame them, as at least part of the reason for this part of our culture is that it's the best way to get high enough promotions to get up to our deserved salary (as defined subjectively by the engineer).
- cmrdporcupine 11y ago95% of jobs are for maintaining an existing code base. So they just want the person who will jump in and start working on it with minimal bullshit. Honestly, learning the syntax of a language takes under a week. Learning the culture and APIs can take years. I've been having to do Objective C for the last year and a half. I don't like it, but it's my lot. I understand the language, but I can't say I understand all the tools and APIs, still.
- hultner 11y agoI think people sometimes takes recruiters words too literally, wanting proficient in a language is a good way to scare of people afraid of leaving their box (I've met plenty of developers reluctant to try new languages and technologies). Talking from personal experience I've rarely ever been more than slightly familiar with the language /required/ for a job and I've always made this clear however I've also explained that this isn't really a problem and I've never been rejected from a position because I weren't familiar with their arbitrarily chosen technology stack. Quickly acquiring new knowledge needed for the job is the most defining quality for engineers/developers.
- lqdc13 11y agoNot sure about dwarfed. I'm at least 50x more productive at prototyping Python than in C. I don't understand what passion has to do with the language/library choice. Assuming there are some people who are primarily motivated by the language they use or syntax of that language, what about people who don't care about the language and are more interested in algorithms and data structures? What about people who are motivated by the final product? Also, lack of such studies leads to people not trying new "stacks" because they are afraid that it's a new unproven technology that probably won't work.
- debaserab2 11y agoI don't think you "don't care" about the language - you just want a language that gets out of your way and allows you to express your solutions easily. That IS a language preference.
- nickpsecurity 11y agoYet, the poster works with a high-level language that readily offers common constructs that are needed without memory management, etc details. Integration is also easier than with C. So, there's concrete evidence that prototyping in Python will be faster given equal effort due to (a) enabling advantages and (b) less work for common stuff. That's me sticking to utter basics ignoring things like REPL interactive development.
- nostrademons 11y agoYou're at least 50x more productive at prototyping Python than in C. I am too. I know some veteran C++ programmers who are far more productive at prototyping in C++ than in Python, though. And even for myself (who is a huge fan of dynamic programming languages), there are some tasks - eg. MapReduces - where I'll prototype in C++ rather than Python because the integration with the framework and faster performance outweighs any gain from language constructs.
- shitgoose 11y agoI totally agree with you that it doesn't matter what language you chose for the project. I would just replace references to "emotional this and that" with "understanding the business domain". If you know what you are doing, it absolutely doesn't matter how you do it, you will get it right anyways.
- mwcampbell 11y agoIs it truly inevitable that a successful product will be rewritten? That's so wasteful that it seems irresponsible to let personal preference or emotional investment influence foundational decisions that might later prove wrong, requiring a rewrite. We should do our best to make such decisions carefully, dispassionately, and scientifically.
- jacobr1 11y agoThe inevitability at this time seems to be that the desired function of large, successful systems will evolve over time. This is the root cause of larger system rewrites being so common and (at this time) largely inevitable. But that is also the appeal of strong subsystems that last and can evolve. Language runtimes, libraries, infrastructure components like databases. The can largely persist, but their suitability to various systems will shift as the system themselves change. One must consider that many approaches, even if better for the long-run would have near term costs in terms of additional effort, or training, operational support or even hardware needs. > That's so wasteful that it seems irresponsible to let personal preference or emotional investment influence foundational decisions that might later prove wrong, requiring a rewrite Not so, since it is likely the case that the requirements and system's function will change, the primary objective is the efficient production of first working version. Personal productivity, satisfaction and good team dynamics probably trump most technical consideration beyond broad strokes (writing for web in assembly is probably a bad idea, but django vs. rails vs. go microservies is probably moot). Furthermore, one must consider the corollary to the initial presumption: most new projects either aren't successful or aren't long lived. So while if you have strong evidence that a system will be successful and long lived further investment in technical deliberation in making the choice of platform, toolset and architecture would be warranted - it is much more likely no such evidence exists. And therefore the initial investment is the only one likely to be made, so longer term confederations matter not (again beyond some basics and near universal best practices).
- nostrademons 11y agoWhen a successful software system is rewritten in another language, that doesn't mean the original decision was "proven wrong". It means that conditions have changed. The original language was usually absolutely right for the conditions that existed when the original software was written, otherwise it wouldn't have become successful. Those conditions often include severe resource constraints; small teams; small numbers of un-demanding customers; and extreme uncertainty about exactly what the product will do. When the product becomes successful, the certainty about what it will do goes up, available resources go up, team sizes get bigger, and customers get more demanding. The world changes around you as well: new languages are invented, new frameworks come out, customers request different integrations. All of these impose different constraints on the software architecture. (Incidentally, I suspect that failure to recognize the time-dependence and context-dependence of decision making is behind most career missteps. That old grizzled programmer who insists on using COBOL and DB2 on record-oriented flat files? He's following best practices, he's just following best practices from the 1960s. Similarly, many workers who assumed companies would honor their pension agreements and no-layoff culture were in for a rude shock when executives made decisions based on what is necessary now and fucked over the people who worked hard for them then.)
- jimbokun 11y ago"Any inherent differences in productivity are dwarfed by the effects of being emotionally invested in your work and having lots of other people emotionally invested in the outcome." In my experience, technology choices can make a massive difference in my ability to stay emotionally invested. If I'm constantly spending mental energy on the idiosyncrasies, strange bugs, and repetitive code required by my technology stack, I have much less time and energy to devote to making changes the customers will actually notice.
- nostrademons 11y agoNo argument there. But you can measure that effect directly, without the need for any studies about how well other people do with a framework.