Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, toxicity and dog-whistling are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !uspolitics@lemmy.world
7) No Hit-and-Run questions.
Please don't delete your post for no apparent reason. If you plan on deleting a question later, say so in the post, or if you feel that you have a good reason to remove it, message a mod beforehand. It's not fair to the ones who took their time to answer, and it's not in the spirit of the community.
8) No Bots.
Posts or comments from bots, LLM's, AIs, Neural Networks, Transformers, or Marvin the Paranoid Android are not welcome in AskLemmy. Real humans only please.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Using AI doesn't mean you shouldn't learn how the systems you are working on or building work, or what tech stack choices are good for what purposes, or what's happening under the hood in the systems you're working on. In fact, learning these things is critical for being able to drive and review work to correct outcomes and efficient operation.
Whilst it might be useful to be aware of certain design patterns, coding concepts, and other low level details of how languages work it's unlikely you'll be applying these concepts yourself - but you must still be able to recognise and understand them. They don't go away in an AI world.
Understanding how things work and when to apply what methods and technologies is still as critical as ever, and is the difference between an engineer using AI on the job, vs an executive vibe coding some shit that doesn't operate scalably, or work on other computers, or can even be hosted safely.
If you can't explain what's happening inside the computer when you run any random line of code, start there. You should know when you're going to disk, or memory, or network, what the costs are, what happens when async code awaits, when you spawn threads, spawn processes, put sync code in async code, put async code in sync code, what the TCP stack is doing when you send data, what the UDP stack does differently when you send data, why you don't put slow operations in the main thread, what healthy caching looks like, what happens when unexpected things go wrong and how to handle those situations, etc