Always the same bs ... It is like some people simply do not know what prioritizing means...

"I want all of it, now!" is like a statement from a stubborn 5 year old.

@rEaL-jAsE

I don't think that's a good idea. Of, course if you get the architecture perfect on the first try, that's great.

But in the majority of cases you learn more about the problem you are trying to solve while solving it. Instead of wasting time on desperately trying to find a perfect solution before even beginning the implementation, you should come up with a good solution that works for now and refactor in stages. Much more efficient and less frustrating.

Completely normal and a good sign of progress!

The more advanced you are as a developer the more you are noticing bad code quality as you are writing the logic.

I personally like the dev-cycle of making it work first, then pretty and then performant. Of course you should not build a huge pile of crap before doing any refactoring, but give yourself room to experiment even though the very first approach might not be perfect. While implementing your solution you will think of a better solution far more often than when just trying to find a perfect solution at the first try.

been there

@Anakata Sry, to hear that. You should probably get a second sim-card (in case you want to afford it) - one work and one private number.

It's crazy, how many burning ships keep on floating around happily ^^

Well this is devrant. So please keep your positivity to yourself ;)

You are not alone, having these dreams, my friend!

That mythical man month ^^

@error503

Seems like you have never really programmed before ;)

@sariel

I thought about rethink as well, but decided to use supabase - mostly because of the simplicity of the setup. Really happy so far, but not much experience with it yet.

Every framework produces an undebuggable pile of trash if the developers are not skilled at using it.

For me, using TS or any kind of typed-preprocessor is a must have.

The Lead developers have to set up the application structure and not rely on every developer to make their own design decisions. This is true for every single application to be built.

Regarding material design: I do like depth in web pages and when it is used selectively it can look amazing. Actually some of the most well designed websites - personal preference - use depth layers.

Have a look at stripe's site!

However I agree with you that pure Material design can lead to bad results - not bad but really outdated. The whole thing paper on a paper on a paper is just too much.

I'd rather have flat components (flat within) and only use depth to separated cards/buttons/etc. from the background.

Why do you have to use electron? Can't you just build a web app? Plenty of great stable stuff there!

Learn both types of languages! My recommendations are:

Haskell (functional) and C (low level).

I like both languages a lot and have learnt so much with these even though I am not using them on a day to day basis.

@cervantes01 Trust me, try it for a small project!

Designing websites is so much faster with tailwind!

At some point one has to adapt either a design component system (Material, Ant Design, ...) or a design utility library (bootstrap, tailwind).

Writing custom CSS gets so messy in production. Not while you are building it, but at the point when you have to change something after a few months of not working on the project.

Reading this, gives me the impression that you have never really used either CSS or TailwindCSS.

Yes, the HTML looks messier with Tailwind!

However - in my opinion - this solution is still way better than the traditional way of writing CSS classes.

Their documentation is actually really good if you know CSS - just search for the property and the customization is right below the examples for all variations of this property. But if you don't even know much about regular CSS then I can see why you are confused.

Keep studying before ranting about topics that are too "high level" for you.