You must log in or register to comment.
Run it in your head, find the edge cases yourself, fix the bug… weakling.
Or do what I do in real life which is patch in new bugs and even a security flaw or two.
tests are for confirming your code STILL works if someone ever changes something
Oh I trust my code, but I don’t trust my coworkers not to break something on the very next commit.
I physically reacted to this post with a combination of disgust, anger, and fear. Do tests. All of the tests. Randomize the order in which your tests run. Cover all branches.
Tests? Pfffft. I am the test.
And while I’m here: https://blog.jim-nielsen.com/2024/sanding-ui/
Users are the acceptance testers.
It baffles me when people use flex layout when it’s clearly visually a grid layout. Nothing here is flexing with varying element sizes and auto-fill-wrap-break of items.
A colleague of mine prefers flex too. But to me, grid is so much more intuitive and simple.
https://css-tricks.com/quick-whats-the-difference-between-flexbox-and-grid/
Tbh I’m not a web person (more of a backend person) and don’t know the recommended practices.
display: grid;is a good friend of mine xDI think using
display: grid;as your default is the better default, so you’re all set. :)
Why do you need either? Just throw the both in the html
People can pull <table> from my cold, dead hands.
(though I’m usually only using it to display some status just for me and not for external consumption; the UI side can have a JSON if it ever comes to that).
I used to be a full-stack dev, but I’ve been pure backend for so long now, everything I knew is outdated or deprecated.
everything I knew is outdated or deprecated
Given the way the frontend world seems to work, this means you’ve been backend-only for at least a week lol
I get a small amount of joy from clicking the “request changes” button and blocking some doofus from merging lazy untested code.
I love going into a PR with 3 approvals already and shitting all over it
Weak code lacks tests
Alt: if strength relies on unity I need to switch to game dev
“Tester, c’est douter”
You can’t trust others to not break your wonderful code. Write tests for the regression.
Just wow bug free code y’all smh
The best way is to try it over and over until it works and then assume it works but then go insane wondering where all the edge case bugs are coming from.
I wrote a test one time.
