Live data from Hacker News

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

news.ycombinator.com

261–270 of 293 posts

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

#262

I once joined a company and found out on day 1 that they had: 1. No source control system 2. No bug/issue tracker (or formal software QA) 3. No build automation 4. No dedicated build system 5. No pre-launch checklists Basically, the latest release was whatever happened to be on one of the engineer's hard drives whenever someone frantically ran in and said "we needed to release!" You can imagine how fun it was to repr…

[deleted]

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

#263

Basically, when I ask for a role, whereby I expect to be placed in charge of the project, I expect exactly that. Not some fluffy title, with a cushy salary. I expect to be able to destroy the scrum process, hang the scrum master. Toss agile in the garbage. Ask the product owner what they actually want. Do that, in about a month. Finish the project 6 months ahead of schedule single-handedly, because web apps are fucki…

Could you please post civil and informative comments instead?

https://news.ycombinator.com/newsguidelines.html

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

#264
Proper (as in working and recoverable..tested to be recoverable under the worst case I could think off) backups.

I wish I was kidding but the last 'complete' back up they had was from mid-2014 (and the system was still in initial development from 2013 late 2016), I started June 2017.

Outsourced development company (and bad developers and..well stuff I'd never seen before, RAID on the server but only 1 disk in use, 64bit Xeon's running 32bit Debian...and on and on it went - A backup server that had nothing on it..I mean literally nothing, the entire system runs as root (because the way to solve your inability to understanding the linux permission model is just to run everything as root apparently).

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

#265
post #250
post #237

Earlier quoted context omitted.

Guys, should we tell him?

Oh, no What am I missing?

It won't get better, he's more senior, he'll probably get promoted before you guys (and he has a head start) so he'll be your bosses boss and mandate all this stuff.

You'll leave because surely everywhere can't be this dysfunctional only to find that everywhere is then you'll reach a grudging acceptance (people will call you cynical) and you will live for your hobbies.

40 years from now a vein blows out and you shuffle of the mortal coil.

Alternatively it'll get better, he'll realise that his ideas while well intentioned are upsetting the team and he'll tone it down a bit.

Flip a coin. (I wish I was joking about the binary options but well...it'll be one of those two).

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

#267

Earlier quoted context omitted.

Not parent, but generally to be able to do remote work. Production goes down and you're not at the office (1h travel)? Now even a 1min fix will cause 1h + 1min of downtime.

So is your cloud in the office then?

The cloud can also be on a VPN.

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

#268
post #219

Earlier quoted context omitted.

Sounds like a nasty place to be in if the first time you do is politically based.

I realise the way I put it may sound ominous, but it's for the good of everyone involved really. Most organisations are shockingly ineffective. Micromanagement and lack of long term planning is abundant. I get hired because I'm good at writing software. This is not wrong, but I can add much more value if I deliver what is needed rather than what is asked. My goal is simply to be able to do that.

Could you share a longer description of how do you do it?

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

#269
post #233
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…

We've got a new member on our team (from a different team within the company) who within his first week is already trying to shake things up with "fixes" Its driving me a little crazy. He is more senior than us, but doesn't have any of the context of why we do things the way we do He'll explain things to us we already know, and propose solutions to us we tried months ago that didn't/don't work After getting a little…

Hmm, well tell us the ideas and we'll tell you if he's right or not.

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

#270
post #87

Well, first I gotta rebuild the release process on top of nixpkgs, then, after rewriting the core product in rustlang, I can focus on replacing all the developers' macbooks with linux machines.

I already want to hire you!

hello mate,you can always reach anytime for any Hacking Job,I am Gary Philip,a Cerified Ethical Hacker.just send me an email :-garyphilip24@gmail.com I am up for you 24Hrs/7 days a week.
Post reply on HN