3 ms·

And they prefer using uncool tools intelligently to solve a complex problem; rather than using the next cool thing dumbly that creates more problems than it sol

by cplat 11y ago

And they prefer using uncool tools intelligently to solve a complex problem; rather than using the next cool thing dumbly that creates more problems than it solves.

simula67 11y ago
And sometimes they are unbelievably set in their ways, for example using procedural code ( STATIC ALL THE THINGS! ) in Object Oriented languages like Java.
- mooreds 11y ago
  And that's the rub. When you are hiring experienced devs, are you getting Mr I-use-staticz or are you getting Ms Let's-use-boring-tech-because-it-works?
majewsky 11y ago
Exactly. More than once I've written a small shell script to do things that other people do in multiple KLOC of Go or NodeJS.
- sqldba 11y ago
  When I quit my prior job, they started a multi-month project to replace all of my PowerShell with "proper" C#. Then they decided it was too hard, threw it all away, and just decommissioned parts of the application and run everything else manually. Working under brilliant minds like that you can see why I quit.
  - yardie 11y ago
    Sounds like a bunch of C# devs who didn't know Powershell and couldn't be arsed to learn it. Even though it has similar syntax. To some developers every problem requires the only hammer they have. Must have been really bad. Why not just hire you on as a consultant?
    - JBReefer 11y ago
      which is sad, because Powershell is great
  - voltagex_ 11y ago
    I'm not fantastic with Powershell but there's another potential reason: you're not allowed to run "random" exe files on $SERVER but (signed) Powershell scripts are fine. I'm not sure where the cutoff point is between this needs to be an app / this can stay as a script, but Powershell seems to lend itself to going either way. I can either incrementally replace C# functions with Powershell (while importing types and functions that I need) or incrementally replace Powershell with C# with the same method.
- akerro 11y ago
  http://aadrake.com/command-line-tools-can-be-235x-faster-than-your-hadoop-cluster.html http://aadrake.com/command-line-tools-can-be-235x-faster-tha...
voltagex_ 11y ago
Like make (or cmake if I'm feeling nice) instead of javascript-build-tool-du-jour.

by cplat 11y ago

And they prefer using uncool tools intelligently to solve a complex problem; rather than using the next cool thing dumbly that creates more problems than it solves.

simula67 11y ago

And sometimes they are unbelievably set in their ways, for example using procedural code ( STATIC ALL THE THINGS! ) in Object Oriented languages like Java.

mooreds 11y ago
And that's the rub. When you are hiring experienced devs, are you getting Mr I-use-staticz or are you getting Ms Let's-use-boring-tech-because-it-works?

majewsky 11y ago

Exactly. More than once I've written a small shell script to do things that other people do in multiple KLOC of Go or NodeJS.

sqldba 11y ago
When I quit my prior job, they started a multi-month project to replace all of my PowerShell with "proper" C#. Then they decided it was too hard, threw it all away, and just decommissioned parts of the application and run everything else manually. Working under brilliant minds like that you can see why I quit.
- yardie 11y ago
  Sounds like a bunch of C# devs who didn't know Powershell and couldn't be arsed to learn it. Even though it has similar syntax. To some developers every problem requires the only hammer they have. Must have been really bad. Why not just hire you on as a consultant?
  - JBReefer 11y ago
    which is sad, because Powershell is great
- voltagex_ 11y ago
  I'm not fantastic with Powershell but there's another potential reason: you're not allowed to run "random" exe files on $SERVER but (signed) Powershell scripts are fine. I'm not sure where the cutoff point is between this needs to be an app / this can stay as a script, but Powershell seems to lend itself to going either way. I can either incrementally replace C# functions with Powershell (while importing types and functions that I need) or incrementally replace Powershell with C# with the same method.
akerro 11y ago
http://aadrake.com/command-line-tools-can-be-235x-faster-than-your-hadoop-cluster.html http://aadrake.com/command-line-tools-can-be-235x-faster-tha...

voltagex_ 11y ago

Like make (or cmake if I'm feeling nice) instead of javascript-build-tool-du-jour.