Pinned
I don’t wanna “build software” so much as
build understanding and express it in software.
Jessica Kerr
21.6K posts
Jessica Kerr
@jessitron
- Computer Science Principles: 1. Binary 2. Photoshop This is a real book!!?
- Abstraction is a great tool and a terrible goal.
- Software is not a craft. Nor is it an art. Nor is it engineering, or architecture, or anything we've ever before. I now have words for what development is: the practice of symmathesy.
- Great code doesn't come from an environment of fear, pressure, worry whether we belong. It comes from welcoming and interchange of ideas.
- OH: “you can build anything in C” is true, like “you can count to any number”
- When we rush development, skip tests and refactoring, we get “Escalating Risk.” Please give up the “technical debt” description; it gives businesspeople a very wrong impression of the tradeoffs. From @janellekz #deliverAgile
- Me: <tries to explain software> He: so it’s kinda like a genie problem, you need to word your wish better? Yes. Exactly.
- If you try to schedule a meeting with me at 5pm on a Friday, you will see that I am busy.
- Don’t organize code according to its job title (model, view, utility); sort it according to its purpose (feature). This reveals interdependency between features, and finds service boundaries for later.
- I sat down to learn enough PowerShell to recreate one of my bash functions. What have I learned so far?
- “Software architect” is out of fashion “architect” implies “design (mostly) before building starts” We need design in software dev, design that never stops
- People. There is a difference between a backend and an API. Taking the endpoints that you wrote for your site, slapping some documentation on them and publishing it does not make an API.
- Once a company reaches thirty people or so, the context starts to split: founders have the contextual knowledge of “why”, while newer hires only have the “how” — so how can anyone make good decisions? ~ @estherderby #uberconf
