Please Start Overengineering
HTML-код
- Опубликовано: 4 май 2024
- Being low-risk is old-school. Using all the technology to build a single line is the way to go.
Previous video: • Please Stop Overengine...
Channels
Second Channel: / @ernestmarcinkoo
Vods Channel: / @ernestvods
Socials
➡️ Live: / ernestmarcinko
➡️ Web: ernestmarcinko.com
➡️ Twitter: / ernest_marcinko
➡️ Instagram: / ernestmarcinko
➡️ GitHub: github.com/ernestmarcinko/
➡️ Discord: / discord
➡️ Reddit: / ernestmarcinko
Music
➡️ share.epidemicsound.com/82sebp
#programming #coding #nextjs 
Развлечения
"You probably need less CSS to style than the classes"
Man chose violence xD
I think what you are trying to say is that you're concerned for newer devs thinking they have to use every new tech they can think of (I certainly did that when I first started coding), and not seeing the impact of the maintenance of the packages and knowledge requirements other devs need to start making changes in the codebase.
I agree with that.
What I disagree on is with the Tailwind take, you not liking it for "cluttering" your HTML isn't a good reason.
Tailwind is mostly CSS properties shortened to classes and with a JIT.
• If you know your CSS, the mental overhead you need to cross to write styles with Tailwind is way smaller than using fancy patterns like BEM, which is almost necessary if you want to write maintainable styles without Tailwind IMO.
• The amount of CSS you would have to write would end up being bigger than writing tailwind, it would just be hidden from you in another file
• The utility classes makes it way more maintainable, you don't have to think of stupid names to give for classes, and it's faster to write.
• Being able to style the element in the same file you have your HTML makes it faster to write.
• It overrides most of the bullshit default style rules.
• Every style impacts its component only, no crazy selector priority fighting nor having to mess with a class that could impact more than 1 component.
• Not relevant for this portfolio, but the JIT makes the outputted CSS smaller than 90% of developers would write.
• I much rather prefer to look at 3 lines of tailwind classes than having to jump around a CSS file (often times thousands of lines long, probably not the case in this project tho) for the classes which are being applied.
Maybe I'm missing something, but that's my take.
I do agree with your takes, but Tailwind is a very very light abstraction on top of CSS - I wouldn't call it over-engineering in my opinion
The way I see it, this approach will limit your potential. When you decide on the tool regardless of the problem, you're no longer a probelm solver. You limit yourself to certain number of jobs you can do especially when it comes with higher complexity than what is necessary, you make it easier for yourself to run into problems also making your software unreliable. Even if it's for a cv it should tell you something about the dev as an engineer/problem solver.
why does a static CV website need a whole apollo server and GQL? the more you look at the deps the more it makes me cringe
Because reasons
"BeCause PeoPle MaY wAnT to SeArch It"
@@13odman 😂
They're too forward-minded, they know they're going to learn new skills so he prepped a whole sql database to hold them.
They also know that in the real world skills come in many ways, shapes and forms, so they need to be prepared for an eventual change in schema, and instead of using a rest api they chose a graphql api to facilitate the addition of new fields, in a way that keeps the previous versions of the CV working properly in case a recruiter forgets to update the page in between CV updates, which should be quite frequent since they are also an adept of continuous delivery.
using nextjs, tailwind, and react for a portfolio is overkill, if you want to show off your skills build actually interesting applications, the CV is supposed to highlight what you have built in the past and not how nice and fancy the CV is.