ipsc shooter, shitposter

  • 0 Posts
  • 176 Comments
Joined 1 year ago
cake
Cake day: January 19th, 2025

help-circle
















  • Companies already were shifting work to India. The offshore/onshore cycle has been going on since like the late 90s. The decently skilled ones would get an H1B and get relocated to the United States as a reward/incentive for good work, but in my experience there were plenty of American citizens that could do the same work that they did. Companies preferred H1B’s because they were cheaper and because the company controlled their immigration status so they had huge power over the workers. But honestly in my field the work quality was subpar.

    This is just companies crying that they can’t have indentured servants anymore in the US and they have to deal with offshoring again.


  • The tradeoff always was to use higher level languages to increase development velocity, and then pay for it with larger and faster machines. Moore’s law made it where the software engineer’s time and labor was the expensive thing.

    Moore’s law has been dying for a decade, if not more, and as a result of this I am definitely seeing people focus more on languages that are closer to hardware. My concern is that management will, like always, not accept the tradeoffs that performance oriented languages sometimes require and will still expect incredible levels of productivity from developers. Especially with all of nonsense around using LLMs to “increase code writing speed”

    I still use Python very heavily, but have been investigating Zig on the side (Rust didn’t really scratch my itch) and I love the speed and performance, but you are absolutely taking a tradeoff when it comes to productivity. Things take longer to develop but once you finish developing it the performance is incredible.

    I just don’t think the industry is prepared to take the productivity hit, and they’re fooling themselves, thinking there isn’t a tradeoff.