3 ms·

I'd be curious as to where the magical 16ms figure comes from. Yeah, a single monitor refresh. But is that really needed for most UIs? these imbecile develop

I'd be curious as to where the magical 16ms figure comes from. Yeah, a single monitor refresh. But is that really needed for most UIs? these imbecile developers ... under-experienced software "engineers." Yes, I know we've all been conditioned by the relentless pecking order of this industry to direct our ire downwards and sideways, rather than where it belongs. But in my experience, at least 80 percent of the time the developers (whatever their caliber) are perfectly aware of when stuff is inadequate, and how to do stuff better. Ultimately it's managers and executives who make the call on what to create, and when to release.

hinkley 4y ago
I spent a lot of time in my career directing it upward, but it's not wrong to blame your peers either. Boundary setting is a two way street. There's a certain ratio of 'no' in your responses and if you don't hit it then you don't have a healthy relationship. And as the member of a group dynamic, you're letting down your peers. But the real shocker was when I caught developers agreeing with me in philosophical discussions and then sitting around doing nothing when slack occurred in the schedule. It didn't occur to me that developers would agree with engineering philosophy only to appear high minded, and then defect when the cameras weren't rolling. Boy was that a hard (and angry) week.
- lisasays 4y ago
  Oh sure - there are definitely morale and trust issues. Even (and sometimes especially) among otherwise smart and capable people. Vastly more common (and destructive) than simple incompetence, I have sadly come to find.
  - hinkley 4y ago
    "Groomed for failure" is one of the oldest engineering terms I stole from someone else. There's a definite "drive it like you stole it" mentality among managers about how to get work out of devs. I've never had much luck with Burnout and Replace. Building momentum by getting better at writing code (not better at taking shortcuts) has a lot going for it but seems hippy dippy to some people. I was just thinking this morning that Ted Lasso may make it easier for some of us to try again to reintroduce some of these concepts.

hinkley 4y ago

I spent a lot of time in my career directing it upward, but it's not wrong to blame your peers either. Boundary setting is a two way street. There's a certain ratio of 'no' in your responses and if you don't hit it then you don't have a healthy relationship. And as the member of a group dynamic, you're letting down your peers. But the real shocker was when I caught developers agreeing with me in philosophical discussions and then sitting around doing nothing when slack occurred in the schedule. It didn't occur to me that developers would agree with engineering philosophy only to appear high minded, and then defect when the cameras weren't rolling. Boy was that a hard (and angry) week.

lisasays 4y ago
Oh sure - there are definitely morale and trust issues. Even (and sometimes especially) among otherwise smart and capable people. Vastly more common (and destructive) than simple incompetence, I have sadly come to find.
- hinkley 4y ago
  "Groomed for failure" is one of the oldest engineering terms I stole from someone else. There's a definite "drive it like you stole it" mentality among managers about how to get work out of devs. I've never had much luck with Burnout and Replace. Building momentum by getting better at writing code (not better at taking shortcuts) has a lot going for it but seems hippy dippy to some people. I was just thinking this morning that Ted Lasso may make it easier for some of us to try again to reintroduce some of these concepts.