3 ms·
Tech choices matter. The industry evolves and all of this experimentation in languages, frameworks, tooling, and libraries has led to real productivity gains.
by chrisco255 9y ago
Tech choices matter. The industry evolves and all of this experimentation in languages, frameworks, tooling, and libraries has led to real productivity gains.
10X developers may be rare...but I don't think it's so rare to see 10X productivity gains when it comes to tech stacks.
For example, a company who runs their own servers manually can see dramatic improvements in productivity and agility if they move to a newer tech stack and run on AWS or Heroku or some PaaS as an alternative.
Using JQuery may be the tried, true, and mature front end stack, but I've been able to rewrite front-end code in a different framework with less than 1/5th of the code to maintain.
To summarize, I think you should hire energized, motivated, continually educated employees that stay at the top of their game...not boring ones.
- kafkaesq 9y agoI think you should hire energized, motivated, continually educated employees that stay at the top of their game...not boring ones. I think the point of the article, which was rather subtle actually, is that "top of their game" is best defined in more general terms than simply "skilled in the top random webby crap from from the last 18 months". I've been able to rewrite front-end code in a different framework with less than 1/5th of the code to maintain. And about 10,000x as many dependencies, not to mention (if not exactly a shit-ton) a considerable degree of implied bulk in the form of new abstractions ("transpiling") and random contextual crap (packaging, etc) to maintain as well. And the implied path-dependence (for the sake of temporary benefit that comes from adding X, Y and Z to the project... it's going to be that much harder to refactor and shift to something else). All for the sake of a simple autocomplete form, and maybe a popup or two. Which is exactly what's so cool about "boring" developers -- they see not just the positive tradeoffs in using the shiny stuff ("1/5 as much code") but the negative tradeoffs ("So you mean that hot new AngularJS thing everyone was yelping about 3 years ago... suddenly isn't looking so hot anymore? How come?") as well.
- chrisco255 9y agoThe app I'm mentioning was pre-Webpack days, like 4-5 years ago. Just using KnockoutJS...which has no dependencies. It made me realize that tools can dramatically impact my output as a developer. Dependencies can sometimes be a pain in the ass to manage...but they are a huge net positive for productivity. When the choice is between downloading a battle-tested autocomplete package written and maintained by someone like PayPal (https://github.com/paypal/downshift https://github.com/paypal/downshift) and rolling your own thing...it's a no brainer. You use the battle tested lib unless you have a very good reason to roll your own thing. Some tools fade, some tools stand the test of time. AngularJS has been deprecated even by its own creators (who built a shiny new framework with the same name)...so that's a bad example.
- kafkaesq 9y agoRight -- moral of the story being, one needs to evaluate any given framework import choice on its intrinsic attributes, pro and con. Not simply on how new and shiny it is. And potential collaborators and colleagues, likewise. Just give me people who are solid in the better practices of whatever language they use (even if it's Java or vanilla C) -- and reasonably aware of the current landscape (even if they chose not to, or heaven forbid, the quotidian needs of the real, money-earning products they work on don't exactly make it feasible to adopt the latest and greatest tools or platforms) -- over the type of folks who instinctively cargo-cult nearly everything that's been trending in the last 18-24 months -- any day, please. AngularJS has been deprecated even by its own creators... so that's a bad example. But don't you remember -- AngularJS was (if you took certain people at their word) the absolute shit some 4-5 years ago (that's slang usage of "the shit", as in "something really, really good you just have to get into, man"). Whereas now it's... well somehow no one wants boast about using Angular anymore, do they? That's why it's such a good example of what I'm talking about.
- chrisco255 9y agoFrom that perspective, I see your point. I think Angular had an optimal sweet spot for the scope of applications it was good at building. Once you went past that point, it became unwieldy. I don't think you should chase something that's merely 12-24 months old if you're working on production code for a big product. But to some folks, using Golang or Node.js is considered "hipster" even though those technologies have been out now for many years and have proven themselves at scale at large companies. I wouldn't have suggested using Node in 2010, but in 2017, it's a mature choice. And letting your team use something like Go or Node over Java isn't going to kill you and you may very well see productivity gains and recruiting gains.
- rjzzleep 9y agoI built an private side project app that was in use at of the major brokers. I built it in react redux, because I thought it would raise "my" value. I've had to rebuild that shit more times than I care to admit. Imho for a small dev shop picking react is a stupid choice. For a small dev shop picking node in the backend is IMHO also a stupid choice. I could go on with the list, but I'm going to stop knowing that I will already have upset enough people. We've basically recreated the PHP problem. For whomever doesn't remember, before the first decent php frameworks like codeigniter(let's not talk about stuff like laravel) pretty much everyone built their own framework. After a couple of years when zend started to get traction they would integrate components from there. The main issue wasn't all the security issues or the usual PHP complaints you hear. The main was the same you have in the javascript community: > No two projects are the same If you have time and money to waste for people to constantly update your tooling fine. But I don't. Hell just keeping up to date with airbnbs linting style guide was a major PITA. EDIT: no I don't think the constant rewrites of redux and react router components, async connect, history etc. can be blamed on someone not having "enough experience in react". there's even a plugin to do regression tests on dependency updates. paying 100k for glorified javascript plumber jobs is unacceptable to me.
- joshwcomeau 9y agoI think a key thing you're missing is that you're new to React/Redux. Of course you won't be as productive with something you're just starting to learn (rebuilding something multiple times is natural when you're still figuring it out, but that goes away). That's not to say that everyone running Angular or Backbone or whatever should ditch their current stack and rebuild in React. But, a new dev shop would be wise to pick React, because most people who become experienced with it are very productive.
- deleted 9y ago[deleted]
- pdimitar 9y agoFlawed feedback. I trained myself in Elixir for a few weekends and once things started to click in my head (I was always an OOP / imperative programming guy so learning functional programming took me some trying) then I was able to do a mini-project that had real value... in 2 working days. I didn't have to deal with dependencies for more than 10 seconds (not an exaggeration), I didn't have to transpile, I didn't have to include shims / polyfills, I didn't have to explicitly include 2-3 CLI "task runners", etc. weird crap from the JS ecosystem that everybody in there thinks is normal for some reason. You can't just expect people to worship your tech stack and blame them for "not being experienced enough". Hell, if you put enough labor, you can get solid experience on a custom-tailored banking system written in COBOL, or custom-programmed FPGA CPU units. You can become an expert manual tailor, too. But that's not the point. IMO the point is -- are you able to immerse yourself in the tech stack you're proclaiming and be useful in business terms no more than 1-2 weeks later? If no, then your stack isn't worth investing into, especially after your stack is known to change trends as if it's some kind of a glamour fashion empire.
- angersock 9y ago> For example, a company who runs their own servers manually can see dramatic improvements in productivity and agility if they move to a newer tech stack and run on AWS or Heroku or some PaaS as an alternative. They can also see development and shipping of new features crash to a standstill if the move fails or, more commonly and even worse, they end up having to maintain and integrate 2 systems. Tech stacks make a huge difference at the start, but once you're in maintenance mode documentation and tribal knowledge are way better uses of time than playing with new shiny.
- rainsford 9y agoTech choices do matter, but I think the point of the post is that some developers chase tech choices for the wrong reasons. I don't think of a boring developer as someone who wouldn't look at transitioning from locally hosted servers to AWS. I think of them as the kind of developers who would have considered the move in terms of a cost/benefit analysis rather than doing it just because the cloud was the new hotness. The non-boring developers the post is talking about are the ones who would have immediately moved to AWS when it came out, just because it was new, and then kept moving to whatever the latest PaaS flavor of the month was every few months just because it was newer. I think those non-boring developers have good intentions, and certainly think of it in terms of staying on top of the industry, but I'm not sure they weigh all the factors in their choices. In particular, I think they tend to overestimate the benefit of switching technology while underestimating the cost to switch and the unknowns that come with a new technology. More than once I have heard a developer argue for doing a fair amount of work to switch to a new technology to gain what is in the end a relatively minor improvement. In my experience, it's certainly possible that a new tech stack could dramatically increase productivity, but even more often it seems like the result in the long run is a heavy lift to embrace the new technology, followed by the discovery of unknown issues, followed by being underwhelmed by the improvement in the end product. I think it's worthwhile exploring new technologies as they come out, but on a strictly evaluation basis and with the understanding that switching to them should be a the result of a measured analysis rather than doing so just because they are new and exciting.
- flukus 9y ago> 10X developers may be rare...but I don't think it's so rare to see 10X productivity gains when it comes to tech stacks. When did this happen? I'm certainly not 10 times more productive than I was 10 years ago. In terms of productivity I think the web is still catching up with what was state of the art productivity for desktop applications 10 years ago, and that was when I was writing in "low level" languages.
- pdimitar 9y agoSwitching from Ruby on Rails to Phoenix (Elixir) definitely made me at least 3 times more productive -- obviously not 10. The ideal tech stack to me is one that is very efficient in terms of machine speed, memory usage and I/O utilization but it sacrifices some of its raw efficiency for human readability, ease of upgrade, less dependency problems, uniform tooling, debug-ability, strong community... etc. etc. problems we the programmers face daily. To me, that is Elixir the language (and its web & API framework Phoenix, and its DB layer Ecto). For various outlier scenarios, to me that's also Golang and a lot of its non-web OSS libs and tools as well. Ruby is a joy to code in (most of the times) but when your $50 VPS can't handle even 50 reqs/sec then you can see how that joy turns into bitterness when the boss comes telling you "WTF?".