• 0 Posts
  • 378 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle
  • I’ve been a pro software engineer for 30 years.

    Colleges are doing a horrible job at relevant skill sets for sure. But also, much of the time what I’m seeking is passion for the field. In today’s world, kids with passion learn everything themselves in their teens and go directly to the workforce because they’d learn nothing at college. College became a place to go if you can’t figure it out yourself, which also means you lack the passion, hence you’re really not a great hire for a small company.

    I currently never hire college grads anymore unless they’re older.

    Things are different at enterprises. They need so many people that the passion requirement is dropped and you end up with tech leads who are passionate leading armies of worker bees who need constant oversight. This also works but has its own inefficiencies far outside the scope of this comment lol.

    That’s how I see the state of the industry. People need to follow passion, not money. Unfortunately the incentives are misaligned by society in general. Not sure how to fix the value problem. For instance, teachers and childcare should be far more expensive and as such pay more. It’s a super heavy regulated sector tho, which is part of the problem.

    But I digress. College for a general software engineering job is a complete waste.



  • I find Grok great for research, ChatGPT great for fun and image gen, clause great for coding, gemini (google) good for quick tech dev/admin ops related searches.

    That’s how I’d best describe what I use each for.

    Do you find grok to be shit at everything? I find it does best/fastest when intermediate searching the web is required, it does that and sources it well. Asking something crazy like “what’s the best product for killing some yellow weed in New Mexico” will typically result in nice tables comparing products with links and details like that.












  • A RESTful service is (usually as of today) a JSON API. They aren’t mutually exclusive things.

    There’s no black and white definition there.

    However, when someone is creating a RESTful service, they’re stating that they’ll be paying mind to HTTP Verbs and status codes as a fundamental part of their design.

    In the original image posted, that dev clearly wasn’t paying mind to the HTTP layer and as such a commenter called it just a “JSON API”, which is the catchall, ugly, Wild West, typical way of doing things.

    Once again tho, it’s not black and white. Others can and will disagree and want to be pedantic. I’ve been a professional dev for 35 years, devs love to argue abt this shit.