raze2012

We can’t fix what happened. The June fiasco brought attention to the Fediverse and it provided a boost. A boost the fediverse wasn’t fully equipped for, but a boost nonetheless.

The best thing to do is prepare for the next fiasco. And given “Reddit pays you for updoots” is still incoming, there will be a next fiasco. Make sure bugs are fixed, be able to point to some apps or alternative views that people made, and overall be a smoother transition than what was before.

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.

the conversation should never be about reddit losing, it’s about the users winning.

if only. Lotta people really thought they could make reddit worried and that if they rebelled enough they could fix reddit. If it wasn’t going to work after that 2-3 day blackout, it wasn’t going to work. The mod in that article said it best:

“More than a month has passed, and as things on the internet go, the passion for the protest has waned and people’s attention has shifted to other things,” an r/aww moderator wrote in a post about the rule change.

And yeah, attention span on the internet is low. If you can’t fix, it’s best to start rebuilding what you want elsewhere. The best time for a backup community was 5 years ago; the second best time is now, so we don’t have this problem of “where do we go from Reddit?” in another 5 years. If more people had the courage to leave, it may have ended in a better protest than these attempts to ruin the IPO or whatever.

Better to play the long game for now. This won’t be the last drama, and it’s simply better to make sure any jank is fixed for the next time people get frustrated and seek greener pastures. That slow burn is how we create a proper platform.

The idea here is that you have general categories and then you rely on tags to do more granular filtering. so you may be on the gaming group, but if you really hate retro gamess you would instead add games.retro (or something similar) to a filter list.

The idea of only a few groups and no custom group creation is intentional. There were other reddit alternatives that died out because everone was creating new groups willy nilly and it meant no one group could get enough traction. In contrast, Tildes only started with a dozen groups and you start out subscribed to everything.

1. it’s not a waitlist, simply invite only. If you can find someone who browses tildes they can give you an invite with no issue. But a semi-common way to “go around” that is messaging the admin, who ofc has infinite invitess, has a business address, and probably has dozens of requests coming in to read.

2. it’s quite the opposite here. The lack of free account creation is to purposefully limit growrth. Tildes doesn’t want to be a dumping ground for reddit refugees everytime a drama explodes.

I mean, they are still on Reddit 3 weeks after the fallout, and a week after they took away a feature people liked. And then when they official announce the cash karma it’ll just get worse.

Pretty clear that the people left are just gonna keep fucking around rather than move on from Reddit. The latter can at least start fostering communities ready for the next inevitable drama.