News for hackers. Stuff that matters.
Re:Programmers Should Plan for Lower Pay? by fragmede on Sunday December 29, 2019 @04:48PM (#21908760)
In fact, that's already been solved for the most boring of digital plumbing. The data is JSON (which requires UTF-8), and the port number either 80 or 443 - the library automatically handles that depending on if the URL starts with http or https. `requests.get(URL).json()` will grab that data for you (Python). That only covers a very specific but very prevalent use case, just like TCP/IP covers the most prevalent use case for networking.

What are you doing where that can't covered by that use case? Actually, I can think of tons. What are you doing that can't be covered by that use case, but is still boring?

Re:Programmers Should Plan for Lower Pay? by jniedrauer on Sunday December 29, 2019 @08:53PM (#21910109)
Something I find myself doing repeatedly is implementing arcane protocols that were created long before JSON. Bit-packed mainframe protocols. After the second or third time of working with another binary format, there's no new knowledge to gain, and it's not interesting work. But it requires meticulous attention to detail and can't be automated. Most industries don't require you to solve this specific problem but it's all variations of this. Shuffle data from one format to another format. Even if it's JSON, you're still moving it from one business domain to another, or one tech stack to another. Backend to frontend. Etc.
Re:Programmers Should Plan for Lower Pay? by perl4ever on Sunday December 29, 2019 @08:49PM (#21910093)
I think you are coming from a common perspective for people on HN and elsewhere in IT, where you can just install anything and provision any equipment to install it on and direct others to do the same.

A lot of people aren't in a position to do this. I think actual plumbers also have to deal with similar constraints.

It's nice to not be constrained, but it's also more impressive to do a good job under severe constraints, IMO.