I have long had a habit of lurking on the edges, processing what I could pick up from others brave enough to speak. I had the attitude "Better to remain silent and be thought a fool than to speak out and remove all doubt." However, lately I have started to agree with a line of thought that it is ok to share ideas that may even be wrong - as long as I am willing to update based on conversations around the topic. So, that gave me the impetus to start this blog.
I thought it would help to identify where I have come from, and what lessons I have picked up along the way. Hopefully, I can expand on some of the lessons in future posts.
From school:
- Actively seek learning opportunities
- Value of internships pursuing your career before you get there
- Lessons evolve over time - if you make time to ponder.
- Rounding Errors caused by digital sampling
- The process of Troubleshooting
- Engineering Estimates for sanity checks
- Equivalence Classes
- Test Plans
- Metrics will get gamed
- Processes - the wrong way (looking at you, Mr Waterfall). Setting the stage for agile
- Let the computer do the work for you. Beginnings of DRY
- Repeatability is even more valuable than speed
- Favorite shell commands
- Set Math: union, intersects, etc
- In databases, null <> null
- Sub-Queries for readability & modularity
- Religion is overrated (Oracle vs SQL Server)
- Performance Tuning such as inserts cheaper than updates.
- Profiling Data - helps identify which inputs exist, what/how much should exist in output
- Extract Transform Load. Consistent approach helps decompose any conversion of data.
- Hammers. People have their comfort zone. It doesn't mean those are appropriate solutions.
- HTML5 & Avoiding the lowest common denominator
- Find smart resources, including people smarter than you
- Find existing solutions.
No comments:
Post a Comment