3

Does your company chicken out on doing multithreaded programming because it's 'too complicated and unpredictable' for their programmers? lol

Comments
  • 2
    Nah, it’s just that we mostly don’t care.
  • 3
    I used to work on a project that'd efficiently multithread up to 60+ cores.

    So, no.
  • 0
    Most frameworks can handle that for us, so no. But even at lower level I expect my colleagues to be able to write multithreaded code if we need to
  • 0
    @petergriffin Except when you have to deal with processing billions of items at record speeds because the client wants it..
  • 0
  • 0
    We do multithreading, but it’s only for the framework stuff. Most of us only develop ”inside” our own dsl, so it’s already taken care of.
  • 2
    It would be nice for my employer to multithread my paycheck and raises
  • 0
    If your company doesn't invest in good devs and tries to build an ontern workforce, then yeah, we do refrain from difficult programming 🙃
  • 1
    Nah, but it’s built into most of our tools.

    The database mess though?
    Yeah, they “determined it was not possible” and gave up. gg.
Add Comment