Author Topic: Software engineers: managing interference  (Read 1342 times)

Dex Sawash

  • Silver Member
  • ****
  • Upphängningspunkterna
Re: Software engineers: managing interference
« Reply #30 on: February 08, 2019, 12:16:42 PM »
What’s wrong with managers
dabbbling in the “codebase”?
The real problem is that
people seem to think the the internet is
a giant truck that you can just dump
massive quantities of information on,
but it isn’t, it’s a series of tubes that
can get jammed when people place
a massive load into them.
My own staff sent me an internet
last month but it didn’t arrive until tomorrow because it got tangled up in the tubes.

Want to hear Angrew do this Dylan cover

Z

  • The movie, not the TV series, or the book
Re: Software engineers: managing interference
« Reply #31 on: February 08, 2019, 01:12:56 PM »
The first couple of years! These days the respect for the job is so low that this would be a couple of months.
Tbf this is a double sided thing. Everywhere is used to people coming in and leaving the second they're trained up to go somewhere better, aren't they? Why wait a year for a decent pay increase when you can get one right now by switching jobs. Seems to be much easier from a political standpoint to keep hiring new people instead of making a genuine effort to retain the existing mid level people who understand the system.

Twed

  • Take a Key for Coming in!
Re: Software engineers: managing interference
« Reply #32 on: February 08, 2019, 06:12:52 PM »
I'm venting a lot here, probably portraying things as more negative than they are. I sat everybody down to have a conversation about software quality today. I don't think it was particularly understood, but it plants a stake in the ground I guess.

Re: Software engineers: managing interference
« Reply #33 on: February 08, 2019, 10:49:02 PM »
I'll come back to this, but it sounds like you need exactly the sort of person that's making my life difficult, but necessary at the moment. A non-hands-on technical shit buffer that can simultaneously placate management but enforce code-quality by sitting everyone down and agreeing a 'definition of done'. Make them be the cunt that proposes things like the 'three amigos' and 'example mapping' and let nature take its course. Demand someone like this and swallow your pride when they listen to them floating ideas you've been floating for ages.