You should be forced to write efficient code and know how to do it in situations where it matters. You should also be able to recognize when it’s more important to optimize for readability, maintainability and clarity.
…now please copy and paste the information about every job, every school you’ve ever gone to, every project you’ve ever done, and every technology you’ve ever used from the above resources into this horrible template.
If you haven’t figured out how to get the most out of what you already have, don’t ask me for more RAM/disk/CPU or anything else. Buy a Pi Zero and use it’s limitations to force yourself to write tight code.
It’s possible to simplify the “normal” things for normal users while still providing source code and repositories that allow us strange creatures to continue experimenting, testing, and yes, struggling with inevitable incompatibilities all night long.
I had a great time at SCaLE 16x the past four days. SCaLE was one of the first big conferences I went to when I got myself back into the technical side of the tech business, and remains my favorite. It’s a special time and a special place with special people.
SCaLE is special and this worked well for the crowd there. There’s a reason I wanted SCaLE to be the first conference where I gave a talk, and was happy for UpScale to be the first place I tried out a funny lightning talk.
I got good feedback on the content if not the delivery, and some additional feedback about how to improve. So I think I’ll rework it and try again. Maybe at All Things Open later this year. I’ll also make sure to practice more in advance so my delivery is more natural, more dynamic and more polished.