Fair check! I use it to polish my phrasing (especially trying to keep up with this thread volume), but the 'scars' and the management experience behind the comment are 100% human. Point taken though—I'll try to keep it rawer
I don't like doing the leetcode grind, but all of the alternatives are strictly worse.
* Take home projects filter out people with busy lives. Wastes 100 people's time to hire 1 person. Can't be sure they didn't cheat. No incentives to stop company from giving you a 10 hour assignment and then not looking at it. The candidate with the most time to waste wins.
* Relying on academic credentials unfairly favors people from privileged backgrounds and doesn't necessarily correlate with skill as an engineer.
* Skipping the tech interview and just talking about the candidate's experience is prone to favoring bullshitters, plus you'll miss smart people who haven't had their lucky break yet.
* Asking "practical" questions tends to eliminate people without familiarity with your problem domain or tech stack.
* We all know how asking riddles and brainteasers worked out.
With leetcode, the curriculum is known up front and I have some assurance that the company has at least has some skin in the game when they schedule an engineer to evaluate me. It also tests your general knowledge and in some part intelligence as opposed to testing that you have some very narrow experience that happens to overlap with the job description.
I've spent a heck of a lot more time grinding leetcode than I have working on take-home projects. I always enjoyed doing take-home's because I could really spend time on it and make it something worth showing off - if anything it always felt like the perfect low-stress way to show what you can do. It's amazing how many candidates don't take the time to make it look good (or even meet the objectives in many cases).
Haven't done one since pre-LLM era though and that path seems like it might be completely infeasible for employers now.
That said, the most productive interviews I've been a part of as both employee and employer have always been with the technical people that you'll actually work with and conversational in nature. You can learn a lot about what someone knows by listening to their experiences and opinions (but this depends greatly on the quality of the interviewer)
The author is writing like Java was outlawed or something. There are tons of shitty enterprise Java jobs out there for those who want them. Personally, I worked one of those jobs a decade ago, and the article's description of the "golden age" didn't bring back good memories.
It's easy enough to avoid the NPM circus as well. Just don't put JavaScript on your resume and don't get anywhere near frontend development.
> The outgoing Element mobile app (‘classic Element’) will remain available in the app stores until at least the end of 2025, to ensure a smooth transition
I can't find any other communication from Element Creations other than that.
The renaming to Element Classic doesn't bode well considering that Element X still doesn't support a vast number of home servers and a number of Synapse authn/authz features.
If they remove it from the app store, my advice for my users is going to be to switch to fluffychat, and I'll eventually migrate away from Synapse to some flavor of Conduit.
Gotta be honest, I don't like people trying to go about their day being disrupted for the sake of a silly video. Even if I thought the jokes were funny, that would have ruined it for me. And they left in the part where they were asked to leave! They're proud of it!
When I originally played it back in the day, there was one scene, combined with some "gameplay decisions" which had me completely lose it.
On the mission where you have to assasinate Lebedev in the airport, when you finally get to him on the airplane you start a conversation, but are interrupted midway by your fellow agent Anna something, who proceeds to kill Lebedev. Well since this wasn't my first playthrough, I knew where the whole thing was headed so I decided to plant some LAMS on the approach to see what would happen.
And what did happen was one of the funniest scenes in a video game. You hear Anna's footsteps, the camera angle change from the dialogue-style camera to a zoom out, and JC turns to the hallway she is coming from. LAMs go off, Anna lets out a scream, JC turns right back to Lebedev and just continues chatting as if it was some type of minor disturbance
Does this depend on sliding sync and their standalone authz server like Element X does?
I'd love to use Element X, but Element abandoned the form of SSO my community depends on, and I don't really have an appetite to spend 12 hours of my free time standing up sliding sync, a separate auth server, migrating my users to the separate auth server, spending hours explaining to everyone that their credentials live in some other place now, and then migrating my custom server admin software to use OpenID connect. Oh well.
What about Matrix Authentication Service? That's still a separate piece of software that requires PostgreSQL (as opposed to SQLite like my Synapse instance uses) and has no clear migration path for those of us using our own SSO solution (SAML, CAS, maybe your own OIDC provider like Keycloak...), right?
I don't want to run Dex and complicate the stack further, either.
I think 12 hours to migrate is probably optimistic even with built-in sliding sync, actually...
I've lucked out and haven't had any issues like that on my tiny home server.
I wish it were easier to be a Synapse admin! It seems like all server updates are focused on scaling matrix.org and the little guys that provide network diversity are not really being considered a priority.
We're actively trying to fix that - we're finally launching an official Web admin interface as FOSS (AGPL) for Synapse in the next day or two (it was meant to ship today in fact, but got blocked on a debate on how to distribute the containers).
Meanwhile you can see me trying to improve diskspace for Synapse by ~100x here:https://www.youtube.com/watch?v=D5zAgVYBuGk&t=1851s - admittedly motivated by matrix.org, but it would improve disk storage immeasurably for everyone.
Then, https://element.io/server-suite/community is built to be a really simple FOSS distro (albeit for k8s) which provides Matrix Auth Service, Synapse, Element Web, Element Call and (in a few days) Element Admin all in one package for self-hosters.
We have very much not forgotten the self-hosters - not least because Element tries to make money by selling the enterprise distro for enterprisey self-hosters at https://element.io/server-suite/pro. The rule of thumb is that stuff which privileges the end-user goes FOSS, and the stuff which privileges the enterprise over the end-user goes Pro{prietary,fessional}.
> I wish it were easier to be a Synapse admin! It seems like all server updates are focused on scaling matrix.org and the little guys that provide network diversity are not really being considered a priority.
Matrix is a product of venture capital and the growth at all cost culture, the absurd price to play (reqs to federate with the canonical matrix.org server) made it clear from the get go. If you have your users managed externally, you could probably have a shot at setting-up an XMPP server alongside Synapse, for a tenth of the hassle and resources consumption, and see for yourself if that's an acceptable plan B.
reply