Quality Stuff

Content STOP DOING AGILE REQUIREMENTS ARE NOT SUPPOSED TO CHANGE EVERY TWO WEEKS YEARS of ESTIMATING yet no real-world evidence of anything getting done faster "In order to reduce process we add more process" - statement dreamed up by the UTTERLY DERANGED POKER is a GAME not a PLANNING TOOL T-shirt size estimation belongs in the CLOTHING STORE not SOFTWARE DEVELOPMENT "Points represent complexity, not time" YET YOU KEEP MEASURING HOW MANY POINTS FIT IN A WEEK?? People who want to "BURN DOWN" belongs in JAIL not run software teams Same goes for people doing GROOMING This is REAL SCRUM done by REAL scrum masters: Planning Work ACTUAL IDEAL Start: 50 points Done: 70 points Remaining: 100 points ????? ??? ???? They have played us for absolute fools

Content Related What personality trait makes a bad developer? Thinks like a normal person, not a programmer. Normal people get things done; programmers get computers to do it. I am extremely lazy; I will spend 12 hours programming something that would take me 2 hours to do, because: 1. It takes me 2 hours to do it the first time, and 2 hours to do it the second. But it takes my program 0 hours to it the first time and the second time and every futire time, 2. you NEVER do stuff only once. 3. I make mistakes. When I do it the first time, I will get something wrong, but I wont want to spend another 2 hours to do it again. But I can test the program and run it until it gets it right.

Content "My life is boring and repetitive. I must change something" "Me after changing all the color combinations in my IDE"

Content if messages for massage in messages message.tags 'success' scriptM. toast (fhtmI: " message?" displayLength:2000);script elif message.tags 'info' scriptM. toast(htmI: " message" displayLength:2000);script elif message. tags 'warning scriptM.toast (htmI: "message?" , displayLength: 10000) ;script elif message.tags 'error scriptM. toast (htmI: " message" displayLength:10000);script endif ? endfor endif

The horror! Using exceptions as a data transport mechanism is like using a fire alarm as an intercom. Some backend dev actually built a system where they're intentionally throwing exceptions to pass data between services! That's like deliberately crashing your car to change lanes. Exception handling is meant for exceptional circumstances, not as your primary API. The stack traces alone would make any performance profiler weep. Imagine the logs: "ERROR: Everything's actually fine, we just needed to send some JSON to the payment service." This is the programming equivalent of using a sledgehammer to insert a thumbtack.

Content 3 V 5 6 7 8 9 10 11 12 A V 13 14 15 16 don't touch this V V V