5 ms·

Man the slackware clock thing is so common. “Is that in confluence?” burns me up regularly. Things like how to delete a file in git. Or revert a file. As the nu

Man the slackware clock thing is so common. “Is that in confluence?” burns me up regularly. Things like how to delete a file in git. Or revert a file. As the number of tools required to build software continues to grow there are more and more opportunities for people to play dumb and act dopey.

renewiltord 4y ago
I don't see how that can work. If someone does that even once you're going to lose respect for them. Twice and you're going to fire them for just not being smart enough.
- mberning 4y ago
  In a sufficiently large organization with legal, hr, compliance, etc. it can be brutal to get someone fired for incompetence. Often they will start looking at the manager rather than the employee. Especially if you inherit a whole team of these folks and want to purge. Sadly it is often easier to just spoon feed these types of people than get them fired.
- dilyevsky 4y ago
  This was an extreme example, there are many more subtle variants of this usually complaining about devenv or some other tooling. Here’s one making front page recently: https://daniel.do/article/laying-myself-off-from-amazon/ https://daniel.do/article/laying-myself-off-from-amazon/ And hey sometimes they have a valid point but yeah usually they will feel out management about it and if it works you’re going to hear about it non-stop
srcreigh 4y ago
There’s a very fine line. What is the standard way to set up the editor? How do people connect to databases? How do people generally reproduce an issue? What’s the attitude towards prod DBs? In fact, what is the expectations around asking questions? Each of these questions has many different answers. Even a very experienced developer may never have seen other options and have intense expectations but not write them down because they’re “obvious”. I wouldn’t be surprised if some company had some standard way to do certain Git operations due to some possibly misguided internal tooling effort… etc If you really don’t want people to ask questions like that, you need to have company specific documentation which is required reading.
ilyt 4y ago
Unless you use MS products, then "it didn't worked yesterday!" is perfectly valid excuse... After trying for hours to make their autogenerated libray to work (I had to patch their own wrappers to return actual error code coz they fucked up error handling) I just gave up for a day and threw some excuse ... the code worked next day. By which I mean it displayed another nonsensical error but it was progress!
djmips 4y ago
Sometimes it must be a personality trait. I have one dev I know that is extremely productive when he is working within his cocoon. But the minute you ask him to use a new tool or deploy to a new system - he needs major hand holding even though he's senior. I don't really understand it, but it is what it is.

renewiltord 4y ago

I don't see how that can work. If someone does that even once you're going to lose respect for them. Twice and you're going to fire them for just not being smart enough.

mberning 4y ago
In a sufficiently large organization with legal, hr, compliance, etc. it can be brutal to get someone fired for incompetence. Often they will start looking at the manager rather than the employee. Especially if you inherit a whole team of these folks and want to purge. Sadly it is often easier to just spoon feed these types of people than get them fired.
dilyevsky 4y ago
This was an extreme example, there are many more subtle variants of this usually complaining about devenv or some other tooling. Here’s one making front page recently: https://daniel.do/article/laying-myself-off-from-amazon/ https://daniel.do/article/laying-myself-off-from-amazon/ And hey sometimes they have a valid point but yeah usually they will feel out management about it and if it works you’re going to hear about it non-stop

srcreigh 4y ago

There’s a very fine line. What is the standard way to set up the editor? How do people connect to databases? How do people generally reproduce an issue? What’s the attitude towards prod DBs? In fact, what is the expectations around asking questions? Each of these questions has many different answers. Even a very experienced developer may never have seen other options and have intense expectations but not write them down because they’re “obvious”. I wouldn’t be surprised if some company had some standard way to do certain Git operations due to some possibly misguided internal tooling effort… etc If you really don’t want people to ask questions like that, you need to have company specific documentation which is required reading.

ilyt 4y ago

Unless you use MS products, then "it didn't worked yesterday!" is perfectly valid excuse... After trying for hours to make their autogenerated libray to work (I had to patch their own wrappers to return actual error code coz they fucked up error handling) I just gave up for a day and threw some excuse ... the code worked next day. By which I mean it displayed another nonsensical error but it was progress!

djmips 4y ago

Sometimes it must be a personality trait. I have one dev I know that is extremely productive when he is working within his cocoon. But the minute you ask him to use a new tool or deploy to a new system - he needs major hand holding even though he's senior. I don't really understand it, but it is what it is.