- 0 Posts
- 10 Comments
He certainly has the high ground
burnso@lemmy.worldto
Programming@programming.dev•We have used too many levels of abstractions and now the future looks bleak
292·2 years agoThen teach us. Advocate for us. Help us improve and understand.
A very large part of the problem is that the people who are knowledgeable are often the ones that bought into the whole lone wolf coder shtick.
Most junior people I work with are interested and want to learn, but between high demands, no time to do it and senior devs who focus only on their own problems - it’s very hard to know how to learn and improve.
We can and need to solve this but it requires that we work together and actually sit down to bridge the knowledge gap.
burnso@lemmy.worldto
[Outdated, please look at pinned post] Casual Conversation@lemmy.world•Where are all the Positive, Wholesome Communities gone, and where are all the hugs, where is my wholesome memes, to help me fight, the politics
0·3 years agoCan you give tips re: plantscaping and aquariums? They were some of my favorites on reddit but I’m not sure what they’re called over here.
Thanks for summing it up! I get the point of the article a bit more clearly now.
I wonder if “AI engineer” isn’t kind of superfluous in that case? It’s essentially just the new normal for software developers/engineers. Another API or tool to interact with to produce whatever product we’re building. Where does the specialist competencies come in, besides having a more intimate knowledge of the APIs and basic understand of how this tech works?
Interesting, but for some reason I found it very hard to read and get anything of substance out of the whole thing. Anyone care to help a dumb dumb out? Or is it just as fluffy as it seems?
Also, is the newsletter any good? Or is it mostly speculative non-fiction with words thrown around that don’t really amount to anything?
Don’t mistake my sarcasm for disinterest. I’m genuinely curious.
🥲 That was beautiful. I would pay Disney good money to see a limited biopic series following the B1 battle droid that said screw it, defected from the army, didn’t get into Jizz and started a fruitful career as a big band singer.
burnso@lemmy.worldto
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com•I'm using ChatGPT to create a short story about a lawyer who is trying to abolish copyright law.English
115·3 years agoAnd then everyone applauded him for his bravery?


Not sure, but probably. I only used yarn 1. Never got around to trying yarn 2+ as migrating our fairly large monorepo project at the time felt like a pretty large and complicated ordeal. By the time I switched jobs npm was already a whole lot better in the ways most important to me.
The little I’ve read about and used pnpm so far it seems a lot more plug n play than yarn while bringing big benefits. Even workspaces seems a lot simpler than it ever was with yarn (at least when I used it). Love the idea of non-flat node_modules and simplified lock files as well.
Time will tell if npm incorporates enough of pnpm’s features to make it obsolete eventually but for now I can understand why it seems so widely adopted.