It's been around for a long time, and it's had its fair share of abuse. If you're like me, perhaps you can recall when one of the most popular uses of JavaScript was for dynamic looking buttons. Do a little mouse over on the button and the button glows, or changes shape, or some other little effect which really amounted to swapping out an image. It was often being used more obnoxiously than elegantly.
Then came Flash. Everyone loved it. And again, everyone over-abused it. Finally, it became obvious (at least to me...) that people tend to prefer simpler design with occasional purposeful animation. In walks JavaScript (again).
Developers began using JavaScript in much more powerful, interesting, and ultimately elegant ways. One of the biggest ways being accessing and modifying the DOM. By listening to user initiated events (mouse clicks, keyboard entries), a developer can dynamically alter, rearrange, delete or create new document objects, all on the client side. A user can even initiate a server request (via the XMLHttpRequest object) and receive its reply without reloading the entire page.
The power, flexibility and standard implementation of JavaScript make it a powerful tool in building web-based applications. It would be a mistake to ignore it. I'm certainly getting my hands dirty with it (honestly, more by chance than anything else) and I've been loving the experience. A book that I've really found a great tool in helping me get the most out of the experience is called The Art & Science of JavaScript. I'd recommend it to anyone in the business or habit of building web-based applications.
Showing posts with label Software Development. Show all posts
Showing posts with label Software Development. Show all posts
Sunday, June 8, 2008
Friday, February 22, 2008
AutoSave Anyone?
(Reader Beware - Oncoming Rant)
The initial keystrokes were hard enough just to get the thoughts flowing. I was able to get out of the mental rut and put down a few good paragraphs. Unexpectedly Pages crashed. No issue there, it should just restore my document...Right?
Lets pause there for a moment to note a few things:
1. In the time that I've started this blog the automatic autosave in blogger.com has protected my work every minute, autosaving some 15 times.
Lets pause there for a moment to note a few things:
1. In the time that I've started this blog the automatic autosave in blogger.com has protected my work every minute, autosaving some 15 times.
2. TextEdit, a very basic word processing program has an autosave feature backing up SQL code I was messing with.
3. Time Machine on my MacBook Pro has backed up my system 12 times since the start of today.
In our world of computing backups, redundancy and autosaving, being able to recover has become common-law! So it was in disbelief that I re-opened my Pages file to find that NOTHING was recovered. There wasn't even an indication that it tried! Thats right...no autosave in Pages!
I won't drag on with any more rhetoric on the subject. This isn't a bash on Pages. Just a rant that the simple programmable things in life should never be forgotten. Autosave is one of them!
Command - S
Wednesday, January 2, 2008
Be Agile, not Fragile!
All you want to do is write some code, and somehow remain profitable. Well, maybe that's not all you want to do. If you have one, you might be interested in fulfilling your client's needs, while not going on any "death marches" in the process. You probably want to work on features that excite you with technology you want to use. You might want some flexibility on deadlines in response to unexpected problems. Ok. Great! Now, choose your flavor of methodolgy: Agile, XP, RAD, TDD, Waterfall, RUP, SCRUM...should I go on? Which do you choose? How do you know what will work best for you and your needs? When in doubt, do what everyone else is doing!
Agile with SCRUM is certainly en vogue. The values of Agile development are captured by the Agile Manifesto: http://agilemanifesto.org/ (also see: http://agilemanifesto.org/principles.html) SCRUM is a way of managing the work and communicating status. The two combined certainly make for an effective set of tools and guidelines to make everyone happy. But the first thing you learn about SCRUM (or the first thing I learned anyway) is: SCRUM is common sense! Meaning, if you have bad developers, or good developers with bad practices, SCRUM/Agile won't help you; firing the developers will! See, common sense at it's finest.
But seriously. One of the advantages of Agile with SCRUM is that work is clearly exposed as knowledge changes. For example, say you agree to deliver the user administration widget in 4 weeks. But as the days pass, you complete work, but new features are discussed. You can choose with the stakeholders what to do with those features: do we try to squeeze all of them in, or can we release the most essential ones first and then the others as enhancements later? Developers get to talk to stakeholders without all that messy project management stuff getting in the way. Of course, there's a Product Owner (Team) and a ScrumMaster. But their roles are mainly about helping the developers work on the most important features without any impediments.
I've worked with Waterfall, Spiral, a little RUP, and now Agile with SCRUM. I love it! It's lightweight, it's simple, it allows for quick response to unexpected issues. I'll be posting more on this topic as my experience as a ScrumMaster increases.
Agile with SCRUM is certainly en vogue. The values of Agile development are captured by the Agile Manifesto: http://agilemanifesto.org/ (also see: http://agilemanifesto.org/principles.html) SCRUM is a way of managing the work and communicating status. The two combined certainly make for an effective set of tools and guidelines to make everyone happy. But the first thing you learn about SCRUM (or the first thing I learned anyway) is: SCRUM is common sense! Meaning, if you have bad developers, or good developers with bad practices, SCRUM/Agile won't help you; firing the developers will! See, common sense at it's finest.
But seriously. One of the advantages of Agile with SCRUM is that work is clearly exposed as knowledge changes. For example, say you agree to deliver the user administration widget in 4 weeks. But as the days pass, you complete work, but new features are discussed. You can choose with the stakeholders what to do with those features: do we try to squeeze all of them in, or can we release the most essential ones first and then the others as enhancements later? Developers get to talk to stakeholders without all that messy project management stuff getting in the way. Of course, there's a Product Owner (Team) and a ScrumMaster. But their roles are mainly about helping the developers work on the most important features without any impediments.
I've worked with Waterfall, Spiral, a little RUP, and now Agile with SCRUM. I love it! It's lightweight, it's simple, it allows for quick response to unexpected issues. I'll be posting more on this topic as my experience as a ScrumMaster increases.
Subscribe to:
Posts (Atom)