201–210 of 293 posts
First, is anything broken? Any RAID arrays that are degraded or failed (yes, I've come into shops where that was the case). That sort of thing.
Are systems secure? Are updates applied? What sort of network security is there? If there are known holes, has anyone compromised the system?
Monitoring, how do we know something is having problems before the phone starts ringing?
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.
Earlier quoted context omitted.
Young folks think, since they've only seen large projects done the Agile way, that its the only sensible way. Yet so much got done, for decades, without agile's help. Even at large companies, sometimes. Even on large projects. I imagine the vitriol above was a response to the dehumanizing effect that agile has on the individual contributor. They become, by design, a replaceable unit. "Hey get me a 6-pack of programme…
And, I get it. Different strokes for different folks. I've worked on more than just crud apps. And at this point, with the front-end/back-end false dichotomy, nobody works on simple crud apps anymore. Single page js frameworks have made interaction design so bloated, it's kind of a little bit awful. But the real loss of traction is in third-party services, authorization and inter-departmental warfare over favor and j…
I just try to be fair and balanced. But I feel with you.
Earlier quoted context omitted.
Make sure to get a MX Blue mechanical keyboard, so that everyone is aware of who's doing most of the keyboard mashing around the office.
Cherry switches? Millennial... You really need an old IBM, plus it doubles as a weapon if your dominance displays backfire.
Earlier quoted context omitted.
"Daily standups" are morale killers.
Daily standups for remote workers are godsend. You'd think you could rely on people to communicate over chat or email, but the standup actually gets everyone talking and discussing.
Earlier quoted context omitted.
As a person working in this scenario I find the biggest issue coming into work on an established code-base is the lack of documentation and a lack of interest from the company's own people to divulge any information about the code base. This unfortunately leads more often than not to the situation you describe, re-written code or projects perhaps unnecessarily separated.
Very true as well, and if that were plainly stated the problem could be addressed. The issue is that some of these people are smooth talkers able to convince managers that these big shifts are necessary right away...and inevitably end up abandoning big projects they push for. Others are able to poke around the codebase and ask questions till they can contribute in a meaningful way, but these are rare in my experience…
>> For the first month or so I take a very humble listening position .. and then - Everything in source control - CI - Static code analysis - Artifact repository - Automated deployments, incl database and configs - Branching strategy & pull requests - Standalone dev env per developer
What do you use for an artifact repository? I’m assuming you mean the cached artifacts of builds, but also vendor artifacts/cache like npm_modules or docker containers? This sort of vendor dependency management is a problem I haven’t found a great solution for yet. I’m actually thinking about creating a product that’s implemented as a proxy and supports multiple package managers, including docker, and caches all down…
Single Sign on. There is nothing worse than loads of different accounts that are all for the same person.
We use SSO now. It's nice.
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…
However, the point of the process is to enforce consistency. If you have no process, then everything is dependent on the whims of the programmer in charge of the project.
No code review? Then I have to trust your code is spotless.
You want to be left alone in a library until the project is done? Then I have to trust you understand the product owners requirements perfectly.
You want to be in charge of the project? Then I have to trust you can handle that.
If I just hired you, why should I trust you?
Based on your comment, I wouldn't trust you at all. You sound like the kind of person who only learns lessons the hard way.