wtroughton

I think what’s universally important is to keep active and engaged in what we’re doing. Some of us have to tell fictions that what we’re doing has meaning, whilst others just know what brings meaning to their life.

My initial approach was to store IP addresses into a hashmap but if the average query was to check address blocks like /24, then it'd turn out to be very poor data structure to search through.

Consider: is there an equivalent concept of Turing Completeness for compilers with respect to computational propositions?

Thanks for writing this, I've been struggling to write about fallacies in software verification for over a month now.

I realized that I wasn't writing for myself, or even folks who are likely to agree (mathematicians, logicians) with my viewpoint. I was writing to convince and justify, instead of examine, teach, or tell.

I think what it important in this discussion is the fact that "software engineer" right now is an aspirational term and that we don't use formal methods to verify software behavior, and instead rely on changing best practices.

Egineering implies a more rigorous process than most software really gets.

As a software developer who's interested in this but has no experience with low-level hardware interface, how does one debug with the microUSB connector? What displays the console output?

I keep a list of all my skills, experience and education in a YAML file and have a LaTeX template that I clone when creating a new resume. Then it’s just a matter of replacing the template fields with YAML metadata and running Pandoc.

The process of figuring out what's valuable is different from person to person. Some people know from a young age. Others figure it out in college or post-education. My values have been shaped and refined over the course of high school, college, and work. The high level picture may not be clear, but I believe it's beneficial to hone in on what you find valuable and see where it takes you.