I haven’t played anything regularly in a few years. My board game group is finishing up an Imperial Assault campaign and there’s been talk of maybe doing RPGs next (though lord knows I have no shortage of board games that I have bought but not yet played). Would love to run Blades in the Dark, Mothership or maybe something OSR. I think all those could be good fits for our group.
Not quite the right kind of RPGs for this community but exciting nonetheless!
Looks good! Don’t forget to paint the base! A solid color like black is fine. It’s such a shame when it goes unpainted.
Then 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.
Fantastic lighting work!
Can 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.
In theory, sure. But because of how small and chronological lemmy is you often end up with the same post several times in a row when it’s crossposted. Which can be frustrating. Not really your fault, but an annoyance nonetheless.
I read it. Congratulations! 🥳
I wonder of this will also apply to npm then. I have a package that uses private packages which requires a personal access token to be present in env. Would make for nicer DX in our case.
I actually love it. It looks like something the character in question would have painted themselves.
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.
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.