Monday, February 22, 2010

Taking Notes

Recording things is part of how you frame the design and understand the problem. It helps to break things down, and build up solutions. It enables to identify what the hard parts will be, and what is low-hanging fruit.

Having the original notes written down when you come back is key to making sure you don’t forget a bunch of details.

Another benefit is in the trail you leave behind. So take notes. Jot stuff down. Use any method that suits you (freemind, notepad, Onenote), but your great thoughts never really happened if you didn’t write them down.

Friday, February 19, 2010

Componets Contributing to the performance of Page load

Network time represents how long a user is waiting while data is transmitted between their computer and your server. We can't completely control network time since some users are on slower connections than others, but we can reduce the number of bytes required to load a page; fewer bytes means less network time. The 5 main contributors to network time are bytes of cookies, HTML, CSS, JavaScript, and images.

Generation time captures how long it takes from when your webserver receives a request from the user to the time it sends back a response. This metric measures the efficiency of our code itself and also the webserver, caching, database, and network hardware. Reducing generation time is totally under our control and is accomplished through cleaner, faster code and constantly improving the backend architectures.

Render time measures how much time the user's web browser needs to process a response from the web server and display the resultant web page. Like network time, it is somewhat constrained here by the performance and behavior of the various browsers. The less we send back to the user, the faster the browser can display results, so minimizing bytes of HTML, CSS, JavaScript, and images also helps with render time. Another simple way to reduce render time is to execute as little JavaScript as possible before showing the page to the user.

Thursday, February 18, 2010

Goals At Work

  • Equity: To be respected and to be treated fairly in areas such as pay, benefits, and job security.
  • Achievement: To be proud of one's job, accomplishments, and employer.
  • Camaraderie: To have good, productive relationships with fellow employees.

Thursday, February 11, 2010

From the CheckList manifesto

Checklists are often between five and nine items and fit on one page. They don't try to spell out everything; rather, they provide reminders of the most critical and important steps. With a checklist, you "improve your outcomes with no increase in skill." the checklist gets the dumb stuff out of the way, the routines your brain shouldn't have to occupy itself with, and lets it rise above to focus on the hard stuff."