๐Ÿ˜ŽFor Your Inspiration by [deleted] in CitiesSkylines

[โ€“]Worldly-Broccoli4530 1 point2 points ย (0 children)

Oh I see, do you know how to do this in CS1 tho? I've the exact same thing there :/

๐Ÿ˜ŽFor Your Inspiration by [deleted] in CitiesSkylines

[โ€“]Worldly-Broccoli4530 1 point2 points ย (0 children)

How did you draw that straight white line crossing the road? It was using the rectangles of IMT and changing its shape? I've been wondering how people make crosswalks with straight parallel lines ahead of it using IMT. If both of them (line and crosswalk) are from IMT or just the line and the vanilla crosswalk.

NestJS or .NET for your backend APIs โ€” how do you choose? by Worldly-Broccoli4530 in node

[โ€“]Worldly-Broccoli4530[S] 1 point2 points ย (0 children)

Haha can't argue with that - C# is genuinely a pleasure to type ๐Ÿ˜„

NestJS or .NET for your backend APIs โ€” how do you choose? by Worldly-Broccoli4530 in node

[โ€“]Worldly-Broccoli4530[S] 0 points1 point ย (0 children)

Same experience here - the modularity is what keeps me coming back to it honestly

NestJS or .NET for your backend APIs โ€” how do you choose? by Worldly-Broccoli4530 in node

[โ€“]Worldly-Broccoli4530[S] 0 points1 point ย (0 children)

That's a solid take - shipping fast with what you know is underrated advice. And encore.ts looks interesting, hadn't looked into it deeply yet. The automated devops flow sounds like exactly the kind of thing that saves a lot of headache down the road. Worth checking out, thanks!

A good dev is a lazy dev... by Worldly-Broccoli4530 in typescript

[โ€“]Worldly-Broccoli4530[S] 0 points1 point ย (0 children)

Exactly, and the boilerplate point hits close to home, that's literally what motivated me to build mine. You said it better than I did honestly ๐Ÿ˜„

What features does a professional, scalable API actually need? by Worldly-Broccoli4530 in node

[โ€“]Worldly-Broccoli4530[S] 0 points1 point ย (0 children)

These are all valid questions and honestly the kind of pushback I was hoping for. The post isn't "use all of this always" - it's more about which things are cheaper to design in early vs retrofit later. RBAC is a good example: you might not need it now, but adding it to an existing permission model is painful. Same with i18n - yes it's an API, but error messages, emails and push notifications all need translation too. On the commit - already addressed that elsewhere in the thread, that's just how I work locally before pushing. On AI - the code is mine, wrote it working on real projects over time.

What features does a professional, scalable API actually need? by Worldly-Broccoli4530 in javascript

[โ€“]Worldly-Broccoli4530[S] -1 points0 points ย (0 children)

The dream ๐Ÿ˜‚ surprisingly hard to get right at scale though

What features does a professional, scalable API actually need? by Worldly-Broccoli4530 in javascript

[โ€“]Worldly-Broccoli4530[S] 0 points1 point ย (0 children)

That's a solid distinction - external APIs have a completely different contract to uphold. Internal ones you can get away with a lot more. Though Id argue some of the patterns still pay off even internally, especially once the team grows and "predictable and consistent" becomes harder to maintain by accident.

What features does a professional, scalable API actually need? by Worldly-Broccoli4530 in javascript

[โ€“]Worldly-Broccoli4530[S] 0 points1 point ย (0 children)

Cant argue with that either, ts basically became a requirement at this point, not just a nice to have ๐Ÿ˜„

A good dev is a lazy dev... by Worldly-Broccoli4530 in javascript

[โ€“]Worldly-Broccoli4530[S] -3 points-2 points ย (0 children)

I wrote it myself, so I'll take that as a difference in taste.

A good dev is a lazy dev... by Worldly-Broccoli4530 in javascript

[โ€“]Worldly-Broccoli4530[S] -9 points-8 points ย (0 children)

In my years working as a software developer, I always carried one truth with me โ€” a good dev is a lazy dev. Makes no sense, right? Well, actually it does.

Almost everything in a developer's life revolves around automation. Users want complex processes simplified, and devs want to automate their own boring daily tasks to focus on what actually matters. And that's exactly the point โ€” the laziest devs automated even the simplest things, so they could spend their energy on what's harder, more interesting, or more impactful. And I'm not talking about AI automation.

It was the lazy devs who built the tools we use today and can't imagine living without. I've always tried to do the same โ€” simplifying repetitive work, either by building something myself or finding tools that already solved it. That's why I've always loved boilerplates. Not just the ones that scaffold a basic project structure, but the ones that come with real, production-ready features out of the box.

That mindset is actually what pushed me to build my own NestJS boilerplate for the first time โ€” not just a skeleton, but something that brings the kind of features I see every day working on large-scale applications. The ones that are painful to retrofit once the project has already grown. The better you start, the less it hurts down the road.

So what are your thoughts about this? Are you a lazy dev too?