Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

Now let that sink in:

  • A lot of their system still depend on very old code/hardware. And those are decades old.

  • Those who knew how to deal with it are retiring/gone.

Now many of the so called newly hired 'coders' have no idea what they are dealing with and likely still just mimic and reuse code with no real understanding.

Now let that sink in: * A lot of their system still depend on very old code/hardware. And those are decades old. * Those who knew how to deal with it are retiring/gone. Now many of the so called newly hired 'coders' have no idea what they are dealing with and likely still just mimic and reuse code with no real understanding.

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (30).
[–] • 5 pts

The layers of new functionality and other hang-on crap is coded by curryniggers. And it typically breaks if anything about the stuff it's built on is changed, and it's so convoluted that it can't be reused or fixed. In many cases, that's a major barrier to fixing the outdated underlying system, among other factors.

[–] • 2 pts

I work for a company that is often accused of hiring out to curry nuggets by those here, and can guarantee that’s not the case - at least for my teams (big company). In my experience with adding new capability to old existing government systems. They’re all old, and forced to continue because they don’t want to replace anything…but still want new stuff on top of it.

As everyone here can imagine, the government does a terrible job in managing their infrastructure, terrible job in planning, and terrible job in finance management.

[–] • 1 pt

I'm sure it's not the case for all of them, but I know first hand that it is the case some times.