Tag: 'programming'
Variable Declaration Performance
Often when coding, we use a single local variable multiple times, overwriting the value many times. It is considered good practice to move the variable out of the looping overwrite and into the smallest scope of code that is run once. But, this makes the code a little bit less concise. So, how useful is it, anyway? I wanted to run a few little tests and see if there's really a noticable difference in performance.
Log Files
Last week's log files are about as interesting as a book full of actuarial tables. A few rare, special people would be delighted to pore through them. The rest of us regard them as warmly as the dumpster behind a sushi restaurant.
Seagull
The human users of a system have this knack for creative destruction. When your system is teetering on the brink of disaster like a car on a cliff in a movie, some user will be the seagull landing on the hood. Down she goes!
So, code to a standard!
Designers who don't know -- or care -- about the implications of proprietary extensions to HTML spew out Web sites that work only in Internet Explorer for Windows.
Sweet Summer
Here comes the biggest event of the summer... no, really. It was our killer-of-vacation-hours vacation. And it was all totally worth it!! It was fun to go to the beach again with my honey (April for Jake, Jake for April). Lincoln City was fun, but I think we determined to try something new in the future. The tradition was awesome while the tradition was awesome.
In other news, we're back in Utah and life here happens to also be awesome, especially when you have such an awesome spouse (April for Jake, Jake for April)! Our love of this wonderful life that Heavenly Father has given us just exudes from the podcast. Download 'er today!
Life in Audio
This is our inaugural podcast, broadcasting our life in high definition audio (or as high definition, well-mastered as we have skill and equipment to muster) to the world. This is an update of the past few weeks.
Slow the Flow
Recently, I've been appalled at a stated software development management strategy: slow down your development. To aid slowness, perhaps we could:
1. Pair keyboarding
2. Use Windows
3. In addition to kickoff and handoff, add halftime shows to stories
4. Left-hand only days
5. No hotkeys days
6. Triple programming
7. Switch roles: dev and dba, designer and qa
8. No IDE days, or better yet, use Eclipse
9. Do spikes on interesting, yet inapplicable things
10. Stay home and mow our lawns
11. Alternate foosball between every step of the dev process
12. Downgrade hardware
13. Lower screen resolution
14. Call more meetings
15. Naps (made better with cups of cheerios and water)
16. Spray Endust upside down around your desk
17. Afternoon LAN parties
With all this fun, one might ask why we didn’t think of going slower sooner.