Live data from Hacker News

Choose boring employees

sicpers.info

21–30 of 44 posts

Re: Choose boring employees

#21
post #9

This article is three lines long. What's next for the front page? Tweets?

Why not? I've seen a number of tweets make it to the HN front page.

Also, when many come here for the comments, or use an article about topic X purely as an excuse to discuss that topic in general (or see what their peers think), does the length of the source article matter much?

Re: Choose boring employees

#22

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…

> 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.

Re: Choose boring employees

#23

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…

I 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 wil…

I 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.

Re: Choose boring employees

#25

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…

I 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 les…

The 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) 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.

Re: Choose boring employees

#27
Unpopular opinion, but I actually think this is very good advice in certain situations. If your startup is using a technology tangentially related to your core product it can totally make sense to use "boring" tech.

The simplest version would be something along the lines of - building a hardware startup? It probably doesn't make sense to build your company's ecomm site on top of React/Redux/etc. Rails works. Shopify works. They are boring options but they get the job done and get out of the way. Same company needs a blog? Don't roll your own, just find someone to manage a wordpress installation and be done with it.

Now that might very not be the case if your hardware has a substantial online component of course, but if your core product value is tied up in selling a hard good that doesn't need an app or a management interface of any kind then it doesn't really make sense to spend extra resources on a really cool website.

Re: Choose boring employees

#28
post #21
post #9

This article is three lines long. What's next for the front page? Tweets?

Why not? I've seen a number of tweets make it to the HN front page. Also, when many come here for the comments, or use an article about topic X purely as an excuse to discuss that topic in general (or see what their peers think), does the length of the source article matter much?

> when many come here for the comments, [..] does the length of the source article matter much?

Fair point, I guess it doesn't.

Re: Choose boring employees

#29

Earlier quoted context omitted.

I 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 wil…

I 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…

[deleted]

Re: Choose boring employees

#30

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…

I 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 wil…

If react/njs is a mistake for web side projects, what would be a good alternative?
Post reply on HN