4 ms·

> Software you run is software you have to maintain; until you can burn it in the fires of Mordor. If there's a public solution that is a good fit for your prob

> Software you run is software you have to maintain; until you can burn it in the fires of Mordor. If there's a public solution that is a good fit for your problem, and was built along the same lines you would build it, then that's great; but if it's a great fit for the problem and also pulls in 70 dependencies and updates three times a week, that's probably not worth the integration mess. I’ve gotten flak for rolling my own library. Basically, I was trying to get the base clock rate of a server for benchmarking purposes. Instead of using an external library, I simply wrote some inline assembly to read from the timestamp counter. I was told this will create a maintainence headache, but zero fucks given on my end. I got to write some inline assembly today. :)

taneq 8y ago
> I was told this will create a maintainence headache... People say things like this as if it's possible to ever get away with not maintaining software. Everything you do will create a headache, you only get to decide the exact location. (And I'm with you on reducing external dependencies where the cost to do so isn't prohibitive.)
maxxxxx 8y ago
"I was told this will create a maintenance headache" That's such a weird attitude I see often. If you had put your stuff on Github under a different name and then downloaded it everybody would have been fine with it.
- Spooky23 8y ago
  I used to work at a place long ago where the on site engineers would write the code, commit it to a “shared source” program at a vendor, and then license the code back at a cost from the vendor.
  - kungtotte 8y ago
    Let me guess, at some point a manager was upset that some internal code broke and instituted a "only shared libraries from this vendor"-policy that was set in stone?
- TeMPOraL 8y ago
  Sometimes I think it's just someone's laziness that somehow mutated into cultural norm. Or maybe CYA mentality, as when a dependency breaks, you can blame third parties and say that it was totally not expected to happen.
peterwwillis 8y ago
Later, when this causes a portability problem, it will be replaced. As long as you, your manager, and your teammates are fine with having to replace your work, go crazy. Write an HTTP server in Pascal. Create a linker in awk. YOLO.
- ak39 8y ago
  >HTTP server in Pascal Heyyyy, what's wrong with that? I am creating a dashboard analytics program which is a Windows service with a fully fledged web server built-in in Pascal currently!
voltagex_ 8y ago
That's cool for you but * How many people in your team/organisation can read and write assembly? * How difficult is it to hire someone with assembly knowledge where you are? (not having a go at your solution specifically - not enough project managers think about maintaining solutions after people have left)

taneq 8y ago

> I was told this will create a maintainence headache... People say things like this as if it's possible to ever get away with not maintaining software. Everything you do will create a headache, you only get to decide the exact location. (And I'm with you on reducing external dependencies where the cost to do so isn't prohibitive.)

maxxxxx 8y ago

"I was told this will create a maintenance headache" That's such a weird attitude I see often. If you had put your stuff on Github under a different name and then downloaded it everybody would have been fine with it.

Spooky23 8y ago
I used to work at a place long ago where the on site engineers would write the code, commit it to a “shared source” program at a vendor, and then license the code back at a cost from the vendor.
- kungtotte 8y ago
  Let me guess, at some point a manager was upset that some internal code broke and instituted a "only shared libraries from this vendor"-policy that was set in stone?
TeMPOraL 8y ago
Sometimes I think it's just someone's laziness that somehow mutated into cultural norm. Or maybe CYA mentality, as when a dependency breaks, you can blame third parties and say that it was totally not expected to happen.

peterwwillis 8y ago

Later, when this causes a portability problem, it will be replaced. As long as you, your manager, and your teammates are fine with having to replace your work, go crazy. Write an HTTP server in Pascal. Create a linker in awk. YOLO.

ak39 8y ago
>HTTP server in Pascal Heyyyy, what's wrong with that? I am creating a dashboard analytics program which is a Windows service with a fully fledged web server built-in in Pascal currently!

voltagex_ 8y ago

That's cool for you but * How many people in your team/organisation can read and write assembly? * How difficult is it to hire someone with assembly knowledge where you are? (not having a go at your solution specifically - not enough project managers think about maintaining solutions after people have left)