2\ Naming stuff: Every name has implicit meaning attached. A function called `doEverything()` will never feel too big. A method called session.close() that doesn't close the underlying DB connection will come back to bite you. (Should've RTFM for SQLAlchemy)
-
-
Prikaži ovu nit
-
3\ Becoming confident about deleting shit code: There’s code you don’t understand, and there’s code you know you’ll never reach. Delete code you’ll never reach, and be cautious with code you don’t understand. https://en.wikipedia.org/wiki/Wikipedia:Chesterton%27s_fence …
Prikaži ovu nit -
4\ Testing: I think of testing as documentation. It’s documentation for my assumptions about the code. Tests tell me how I (or the person before me) expect the code to work, and where all they expect things to go wrong.
Prikaži ovu nit -
5\ De-risking: The art of reducing risk with the code that you deploy.
Prikaži ovu nit -
6\ Design: Systems degrade. Best way to reduce rate of degradation is to factor this into the design phase. - Keep business logic and infrastructure separate. - Design processes around maintenance.
Prikaži ovu nit -
7\ When things go wrong: Despite the instinct to push a fix for the change, the first thing to do is rollback to a previous version. Minimize client impact!
Prikaži ovu nit -
8\ Monitoring: If you don't find out when things go wrong, can you do anything about it? This is something I never did in my school projects, and something I can't live without in the world where code is supposed to run for more than 30 minutes.
Prikaži ovu nit -
9\ The rest: I haven't cracked the code of software engineering, yet. There's much more to figure out. Find the list of things I know I don't know at the end of the post!
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.