Live data from Hacker News

Ask HN: What is the first thing you implement at a new company?

news.ycombinator.com

1–10 of 293 posts

Ask HN: What is the first thing you implement at a new company?

#1
For job-hoppers and contractors. If you arrive at a company, what is the first thing you push for?

For instance, I usually implement a good feature-branch flow with branch pipelines and a strict merge-to-develop etiquette with mandatory merge requests. It makes my work easier and once the team is used to it, they also really like it. No more messy development branches.

I also request a small office stool next to my desk to make code reviews, three amigos and pair programming easier. It is a small thing but I noticed that people are more eager to discuss things if they have a place to sit.

Re: Ask HN: What is the first thing you implement at a new company?

#6
For the first month or so I take a very humble listening position, even if I immediately see things I want to fix. More often then not, there is a background and a history to things that could lead to a) my “fix” being unnecessary and/or ill-informed and b) friction with the rest of the team because here comes a whippersnapper upending all our stuff.

Process and code fixes are _much_ easier once you have good rapport with the team.

Re: Ask HN: What is the first thing you implement at a new company?

#9
post #5

What's three amigos? Never heard that term in programming.

I had to google that as well. It seems to be an agile practice [0] that consist in gathering a developer, a product owner and a QA tester in order to produce acceptance tests using the format given/when/then.

[0] http://jonkruger.com/blog/2012/01/04/the-three-amigos/

Re: Ask HN: What is the first thing you implement at a new company?

#10
post #6

For the first month or so I take a very humble listening position, even if I immediately see things I want to fix. More often then not, there is a background and a history to things that could lead to a) my “fix” being unnecessary and/or ill-informed and b) friction with the rest of the team because here comes a whippersnapper upending all our stuff. Process and code fixes are _much_ easier once you have good rapport…

Yeah, I have to say I'm a bit surprised to see people so eager to change things that are working, so fast.
Post reply on HN