Good code, Bad code
Hussein Nasser
Software Engineer | Talks about backend, databases and operating systems
Code is just code, until bugs appear.
Then we label it “bad code”.
Bugs are fixed.
The new fixed code is no longer just code
It is labeled “good code”.
Good code isn’t appreciated without bugs.
Engineers writing good code are good engineers.
But only because of bugs.
For if it weren’t for bugs,
Code would be just code,
and engineers would be just engineers.
Therefore good code needs bugs to be good.
And so do engineers.
It is a symbiotic relationship.
One must not detest bugs,
as this creates a hostile environment,
raising anxiety and stress
and leading to unwise decisions
that one might regret.
For a change, approach bugs knowing
that you can’t be you without them.
well, every line we write can be a candidate for bugs, so no code is a good code ??
Systems Analyst at Aptiv
3 个月i only take it serious when if is closed with fi ??
Software Developer @ Nextview Consulting | Salesforce Commerce Cloud, Demandware, JavaScript, Node.js
3 个月This is poetry.
SOFTWARE ENGINEER + JAVA 21 + SPRING BOOT + KUBERNETES + KAFKA + AWS + QUARKUS + ELASTICSEARCH + WEB DESIGN + ANGULAR + SVELTE + CI/CD + API REST + TESTING JUNIT + MOCKITO + DOCKER + SERVERLESS ARCHITECTURE + ENGLISH
3 个月Be more productive and code everything in one line, the whole proyecto. The truth is that you spent 80% of your time reading code instead of writing so, if it's more clear is better . But you are not prepared for this discussion ??