raze2012

in rough order of important:

• experience
• personal projects or project you contribute to (e.g. a decent sized code base in Github). if you’re early on, this can be school projects.
• ability to answer programming concepts in an interview settings
• school/grade prestige.

I have no idea what I would say in an interview.

if you have no previous job, then yea. It’s rough. The first job is always rough, and even in software that’s no exception. You will want to talk about decisions and features you worked on in personal projects for that stuff. And of course, really nail down your fundamentals; they really drill you with those interview questions as a junior.

If you have a job, then talk about that. Maybe there’s some NDA, but you can talk about some problem in general terms and what you needed to do to solve it. You’re not expected to do anything crazy as a junior, so your answer relies more on you knowing how to work in a team than novel architectual decisions.

Personal example: my first job was at a small game studio and my non-BS answer would be that I simply did bug fixes for a game. Nothing fancy, probably something an intern can do.

But interview spin: doing those bug fixes

• helped me learn about Unity’s UI system, I can talk about specific details if the interviewer cares (and don’t feel too bad if they don’t. Even a super experienced engineer won’t be able to talk about every sub-topic of an industry)
• I talk about where I encountered decisions and when I talked to my lead about what to do. e.g. One bug ended up coming from code that another studio owned. While it was a one line fix, I reported it to a lead who would then create an issue to pass on to that studio. Frustrating, but it shows you understand the business politics of the job, something school can’t teach.
• I never did it at that first job, but there were moments where deadlines get moved forward, and you think of a compromise for a feature due to the lack of time . That shows your ability to identify the Minimum Viable Product and to understand the problem, both the bad and good ways to solve something (sadly. in games you may have to hack solutions quite often)

Best of luck

We’re talking here about engineering role after all.

where? seemed like general advice.

Even then, thee aren’t mutually exclusive. your competence will affect how people see you on a personal level, at least at work. And your competence affects your ability to be given problems to own. You’re not gonna give the nice but still inexperienced employee to own an important problem domain. they might be able to work under the owner and gain experience, though.

Documentation and presentation are highly undervalued, and your ability to understand and spread that knowledge can overcome that lack of experience to actually handle the task yourself.

but the millions of small niches are lacking still

Even Reddit didn’t fully solve that problem. When you go outside of the general topics it an be surprising how slow activity can be. That’s simply the nature of the niche.

There’s no real way to solve that without simply being that change yourself. Because those niches tend to have the 2-3 same users posting half or more of the discussions or links.

Well that’s the sad reality. I don’t think most people want to move. They are hoping reddit fixes itself or at least compromises on their plans. I was in that same boat myself during the first blackout way back in 2015.

Ofc, I saw over 8 years how they proceeded to do almost none of their promises, implement actual user centric features when the loudest subs literally broke reddit, and threw in a bunch of stuff no one asked for: crappy video player, hiding QoL behind a paywall, polls that barely work on old reddit, adding NFTs over a year after the internet went to war with the concept?

Yeah, I’m a very patient man, but around 2019 I realized not much was going to change. And the coup dtat is that the communities themsselves have gotten more and more polarized over time. I remember a time where I could at least lightly touch into some political issues as long as I stick to smaller subs. During my last days (around the time blocks updated to be much worse) I was being blocked for correcting grammatical errors. Not minor stuff, stuff that would fundamentally change the meaning of their sentence.

So yea, I’ve given up. But it took me years after my “breaking point” and I’m sure for others they will be in the same boat

some of those mods are likely thinking that moving would destroy the community they worked so hard to manage

they aren’t wrong. It will massively deflate their community. That’s an ineivtability of how lurkers on the internet work. They aren’t there for community, they are there for easy passive browsing.

What can we do to help them transition?

“we” as in the common person? It won’t be a fast track. There will need to be a steady supply of content for a certain topic, and a stream of discussion. Unfortunately the best way to help as a single person is to basically become that sweaty forever online person. The first step to the Network Effect is to generate enough content to engage with.

If “we” have developers or artists that can be one bigger step to help out. contribute to making apps and extensions to either bridge the gap or overcome current shortcomings of these federated instances. Even amongst techy communities there is a lot of confusion to how instances work. So some app to make it dead simple to browse and comment (while later allowing options for power users) is key. Sync committing to working with Lemmy/KBin is definietly a bit help.

Most of the rest is up to the instance admins. SEO, improving features, getting good moderatiors, etc. None of that is in out control, we can only give feedback