schmonie

joined 1 year ago
[–] schmonie@lemmy.sdf.org 8 points 1 year ago

Also really enjoy the lack of unfunny memes and shitposts here. If you browse by all instances, it feels like it's really hard to find real content behind all the shitposts.

[–] schmonie@lemmy.sdf.org 1 points 1 year ago (1 children)

The bottom of that Wikipedia page has a reference to something else that sounded interesting called “/dev/mordor” in some Plan 9 OS fork called 9front. Sent me down a really interesting rabbit hole http://9front.org/

[–] schmonie@lemmy.sdf.org 3 points 1 year ago (2 children)

Reddit isn't totally free of this problem (feature) either--You can have multiple subreddits dedicated to the same topic.

IMO while the federated communities might feel fragmented if you are used to reddit, it's the main benefit of using Lemmy and something that should be embraced. Concentrating content into only a few instances defeats the point of federation.

Take the current issue as an example: A gigantic community defederated from another gigantic community leading to a comparatively large wall between the content of those communities. Had they been smaller, the impact of this issue would therefore also be smaller. This affects other communities which get content from beehaw as well, since there's now less interaction between a large portion of the fediverse user base.

It's only natural that large communities will bubble to the top however, and there probably isn't a good answer to how to 'balance out' those communities, or if that's even beneficial at all.

[–] schmonie@lemmy.sdf.org 1 points 1 year ago

Recently in my career I’ve been leading more and larger projects, and a lot of the skills I think more junior devs prioritize, I’ve found myself without. As you move into L4+ roles, I find the more important skills will come from team management, how to decompose problems, and delegate those components correctly given the talents of your other engineers. Critical thinking is important at every step of your career, but probably too broad to say it’s the most important. I feel the very senior engineers at my company are solving broad, architectural and operational issues rather than the individualized or hyper specific issues of the more junior devs. That’s not to say one set of problems is easier or harder than the other, but the senior devs need more “political” or managerial skills, for lack of a better term.