FWIW, at UCLA, computer engineering was a different degree than just computer science, and had more rigorous courses including electrical engineering and ethics courses. Many people dropped out and switched to the CS degree instead.

deleted by creator

tl;dw: the video makes bunch of theories, then says none of them make sense. We still don’t know.

If people are not happy, that’s the most important thing. I’d fix that first and foremost.

• It doesn’t sound abnormal
• You’re not crazy, there is always room to improve dev experience
• Probably they worked at a big company with tooling for this kind of thing. Startups can’t afford the same design patterns as big companies.
• YMMV, but this architectural pattern doesn’t seem very Go-friendly or startup-friendly. I’d just use one type with optional fields, instead of writing fully different types for each of DB, BE, and FE.
• Frameworks are like safety rails around design patterns. If you’re not an expert, they can help you build a passable system design. But in the long term it’s better to learn design fundamentals and use frameworks only as needed.

Depending on your experience level, reading through refactoring.guru may help your situation. Lmk if so, and what you end up doing.

Uhhh where is this person getting those stats? Turnover at Google is nowhere near that high.

Source: I used to work there

To be clear, I don’t think this post is the problem. The article, while I disagree, is fine. It’s OK to talk about the issues with Brave.

What is not OK is replying “stfu chromium shill” every time someone brings up a reason that maybe Brave isn’t all that bad, and then harassing them if they reply back. Obv you’re not doing that, so this comment isn’t directed at you.

1. Reading “Clean Code”
2. Doing a coderetreat
3. Volunteering to be a code reviewer for my product area.

Edit: Shortened, excuse my braindump

Kotlin! I love that dataclasses and extension methods are a first class citizen.

People said the same thing about gay marriage. There’s a difference between having a conversation about choices, and harassing anyone who disagrees with you.

My browser choice doesn’t affect you, so kindly stfu and mind your own business.

Unpopular opinion, I like Brave and I’m tired of everyone hating on it and its users. Please stop, it makes Brave users feel very unwelcome on this platform, and our browser choice doesn’t affect you at all.

If you don’t like it, don’t use it.

Friendly reminder that Brave browser blocks all YouTube ads and blocks their annoying popups too. It works on mobile too.

Corporations aren’t people and don’t behave like people. Giving credit to corporations doesn’t work in the long term, because people who work for them are constantly changing. The ones who did a good job may leave or get replaced, and the ones who take over may not care about maintaining their legacy.

Not because I think it’s the best of all time, but because I’m grateful it made my work easier: Kotlin.

I used to write tons of boilerplate in Java for my job, and now I don’t.

Wow, such vitriol in some of these comments. Y’all are kind of proving his point…

The paradox of software: Technology empowers people, but power corrupts.

It wasn’t removed because of the pronouns though. It was removed because the mod description violated their community policies.

There are plenty of mods just like it that the site keeps up. Dozens of mods even remove black characters from games, which is way worse. The difference is, those mods don’t write long rants about how much they hate minorities and liberals in their descriptions.

Good point. That used to be the case, but I think that’s been a solved problem for a while. IIRC, most places cache functions for up to a day, so any site with reasonable traffic won’t have to wait for boot.

Regarding scaling, one cool thing about serverless libraries is that some are open source and provide instructions on how to self-host.

FWIW, serverless doesn’t mean “no backend”. Serverless apps can still have backend code using edge functions. Serverless just means “much less backend”.

Most backend code I’ve seen is boilerplate, or reimplementing functionality that already exists in the DB, and serverless libraries just remove the need to write that boilerplate at all.

Is that a hot take, though? Pretty much every major tech company and major university agrees.

Compared to C or C++ it is miles ahead, but higher-level programming languages can be more intuitive. Kotlin IMO is much more intuitive than Rust.

While Rust code may look as simple as other high level languages, it takes much more effort to get there. It can feel like the type system is fighting against you, rather than being there to guide you toward a correct answer. Thanks to Rust’s macros, IDE support for Rust is also not as good, which contributes to that feeling.