![]() If it’s a larger piece of work I’ll try to think about the smaller tasks involved and write a TODO list on an index card or something, which helps keep me focused. When I have a UI that I think will work, I start coding. If I feel like I’m onto something good, I’ll sketch out some UI screens. When I’m thinking about a new feature, I usually start by writing my ideas out with a pencil in my notebook. I learned a lot from the way people work at Google, but coming away form that process-heavy environment, and working by myself instead of on a team, has given me a lot of freedom to be fast and flexible instead of process-driven. Up until about a year ago I was working at Google, which has a very comprehensive set of practices they follow for development. How would you describe the development process you follow? One of my first college web projects was a Javascript-driven webmail app, and I’ve spent most of my career since then writing programs that run in web browsers. I’ve been building applications for about 12 years now. It was one of the first websites that allowed multiple people to collaboratively build a playlist and listen to it together in real time. I built and run Listening Room, a website for listening to music for other people. The notes on how Redis is used in the architecture are especially interesting: Who are you? In this edition of What’s In Your Stack? we find out how a cloud-bound application is developed and architected. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |