Sam Schillace writes: I was talking with the engineering team at Box about what I’ve learned along this journey, and what came out of that conversation were my personal engineering principals. These aren’t rules or engineering guidelines. They’re simply the principles that I pay attention to when I write and operate code. These include: Be paranoid. Don’t lie to the computer. Keep it simple. First rule of optimizing: don’t.
Jim Bird writes: Using run-time flags like this isn’t a new idea, certainly not invented at Flickr or Facebook. Using flags and conditional statements to offer different experiences to different users or to turn on code incrementally is something that many people have been practicing for a long time. And doing this in mainline code to avoid branching is in many ways a step back to the way that people built software 20+ years ago when we didn’t have reliable and easy to use code management systems.
Never say: “Do as I say, don’t do as I do” Create An Environment Of Play Manage What They Consume Interrupt Negative Self-Talk Actively Remind them to be Grateful Make Rigid Routine Days Mandatory Encouraging Curiosity and Asking Questions Encourage Independence From Diaper Years Never Teach Them Ugly Ideas About Money Let Them Have A J.O.B. Answer Their Questions With A Question Pour On The Hugs and Kisses 12 Ways To Instill Your Kid With An Entrepreneurial Mindset
Bruno Filippone writes: One of the easiest tricks to ensure your software will live longer is avoiding to write code tightly coupled to libraries and frameworks. Reducing the number of dependencies of your codebase is always a no-brainer. Making sure the majority of the code you write does not rely on a gazillion third-party libraries should be a priority. How Code Becomes Legacy
Ruairidh Wynne-McHardy writes: We are all attached to the things that we create. From our relationships, to our work, to trivial things like the way we decorate our home — we don’t like to destroy things that we have put effort into. That’s why it’s even more important to delete your code. Never be afraid to throw away code that’s not working when the requirements change. You know more about the reguirements now than you did when you first wrote the code.
Entrepreneur has a list of their tweleve most common writing mistakes. These mistakes are targetted to business style writing: You use industry buzzwords that are hackneyed and phony. You assume the reader knows the acronyms or identity of the people you mention. You overuse CAPS and punctuation. You compose overly complicated, overly abstract or flowery writing. You mix single objects with plural pronouns or single subjects with plural verbs. You make one of these common mix-ups.
Brett Terpstra explained how to perform a “safe mode” boot of MacOS. Shut down the computer Hold down the Shift key as you press the power button Keep holding the shift key until after you hear the chime Wait for macOS to boot Shut down and start again without the Shift key Have You Tried Rebooting?
This Chapter is focused on efficient scanning a large table using pagination with offset on the primary key. This is also known as keyset pagination. Efficient pagination of a table with 100M records The key insight is to use the primary key as the offset to avoid missing records (if they’re deleted between invocations) and to increase performance by using a RANGE join type, which is much faster (constant time.
Back in May, CGP Grey posted a video based on Randy J. Paterson’s book How to Be Miserable: 40 Strategies You Already Use . After watching the video, I had to read the book. Both Rosey and I finished it in one night. Within his 40 lessons, we each found a least a few that applied to us. The book is structured as a series of 40 “lessons” on how to be miserable.