The article addresses both of these pretty clearly. Semantic versioning gets borked with reverts and the automatic changelog is targeting the wrong audience
I think you're missing the part where interacting with strangers is also working the general socialization muscle. If you find yourself being more social in general, and give yourself the time to recharge, then you'll be better equipped to engage with those closest to you. You may even get lucky and add someone else to that circle
That's exactly the sorts of issues I was having. That and it somehow kept losing my encryption information so I'd lose access to all of my messages or something similarly ridiculous
Very cool article. To really drill it home, I would have loved to see how the query plan changes. It _looks_ like it should Just Work(tm) but my brain refuses to believe that it's able to use those new indexes so flawlessly
I've tried off and on to actually use Matrix. I was a bit of a loud supporter in the early days. Unfortunately, it looks like it still hasn't grown past the fundamental issues I was having then. It might be time to try something else
This is exactly the kind of negativity that only appears on the internet and that this study sort of shined a light on. Would you really tell this person to their face that their art sucks just because it isn't good for you?
Part of the goals of making it so tiny, as far as I understand it, is that a normal person could reasonably implement the entire thing from server to client. Going full HTTPS and HTML is a bit of a lift for a single person in a short period of time
I actually kind of like the subset of Jira that I use. Put tickets in a project, create related tickets when I'm breaking down larger projects, expose the project as a Kanban board so we can see at a glance if the right things are being worked on.
That's it. I've essentially built this for myself a few times over so I doubt this is what people are actually paying for so I must be missing all of the features that people hate
I would say an actively harmful TypeScript. Just a couple of days ago, I had bug in production because apparently the union of two types is not the intersection but the sum. It exploded because one type had a method that the other didn't. That's an absolutely horrible footgun
I'm actually in this exact position right now. The vast majority of the time I write in TS but I have a need to process a whole lot of data so I went for Rust instead. Java is too much of a headache for me, personally
I frequently hear about this abuse of estimates and even ran in to it myself when I was a more junior engineer. In my opinion, part of maturing as an engineer is learning to call your shots and properly communicate when you aren't sure how accurate you are. It's one thing to say "I promise this will be done tomorrow". It's another thing to say "we're not positive but within the month seems likely"
> To authenticate is to prove who you are. To authorize is to grant access.
We should be screaming this type of thing from the rooftops. I struggled so much with the difference until someone said something to this effect. AuthN = who you are, AuthZ = what can you do. People seem to get confused because certain classes of individuals have certain rights and think it's the "who" that's important and not the role
I wouldn't call out the depression bit as a Gen Z exclusive. Millennials basically invented modern, every day, gallows humor. Arguably, they're also the ones to normalize going to therapy. Not to say that things aren't bad, just saying that part didn't start with Gen Z.