Launching Real Soon

Posted by Shaza Hakim on June 1, 2010

Up to this hour, we’re still doing last minute removal of things from the original Stampede v3 design. With the amount of content we’re dealing with – 24 dissected portfolio pieces at last count – 8 months of detailing work on weekend and after hours don’t seem at all extravagant.

All in all, I spent around 180 hours of design time and that’s not only because of the level of complexity involved, but mostly the routine of going macro when everything is done, then removing almost half of it.

I still do incremental design change after sending the templates for Joomlafication, some so minute that only the most observant will notice. If we don’t have our own internal programming powerhouse, I can only imagine the costly bleeding.

Because this is the most ambitious project we have done for ourselves just yet, tension does run high and heated arguments over design vs code were so commonplace that when we finally come to an agreement, it was worth sitting back to take in what just happened. Such is the merry partnership I have with Dov.

It took 4 major revisions, countless minor ones, a bit of going back and forth with the rest of the team for valuable insight (whether to place this element or that on the right or left or scrap it altogether). Stampede v3 was almost a practice of convoluted layering (up to 400 at last count) to achieve a particular blend, testing out new composition for different content type, revising typography properties. Let me not bore you. Needless to say, it required plenty of patience as well.

Though I must say the only constant throughout the revisions was our signature color red. Our new logo and branding does not go through multiple iterations like most design agencies do. The branding – if you can call it that – was a split second decision of deciding what embodies Stampede. After that was decided and validated by the rest of the team, we now have a new logo, polished and all but still represents the very same identity.

Stampede has been very blessed and lucky, to say the least. We have a good score of clients who pretty much leave most design and development decision to us. We also get smart young people generous enough with their passion and time to become part of our team. I felt it’s about time for us to share values that have prevailed since Stampede’s very early days so we have designed and built a special page for this. As co-policymaker at Stampede, I probably have more fun with the Values page than most people expected.

So when v3 is finally launched, you may find it look way simpler than the actual effort – I sure hope so after the many hours spent mulling over what to safely remove and what to keep.

But then again, Stampede’s own website design has always been a sort of escapism for us from daily client requirements. It’s something we don’t do everyday and probably will never do again. For that reason alone, I know a few more days of punishing pixels is worth it.

Posted in Design, Team 1 Comment »

On Good Communication

Posted by Anita Zein on May 8, 2010

Good communication attracts great clients and bring about the happiest of team.

Anita Zein writes about the importance of communicating good especially in the wonderful chaos that comes with her project management turf. Anita is the Project Manager at Stampede.

In the work we do, everything involves multi-directional communication: telephone, messages, faxes, emails, even notes. A successful project or product is often achieved only if all parties involved truly understand each others motivation and goals.

In almost all aspects, communication is the one definitive role in the success of a project.

Working separately of distance and time with the team and the client is a new experience to me. Face to face communication is easier, but it’s not always possible. Even so, there is no excuse for a disconnect in communication, especially with a number of supporting facilities that allow for effective and accurate transfer of information. Distance and time is no longer an obstacle now even if your team and your clients are not in the same location, or in the same country.

Here at Stampede, we use all sort of communication tools: Basecamp, instant messaging, voice conference, email, telephone. We even send each other reminders via ReminderFox. All these tools, when applied right, greatly facilitate the type of work we do, to help deliver ideas and keep us focused on details. I do find written communication more productive. To me, everything noted and recorded can always be quickly reopened and referenced at any point of project development. There is very little margin of misinterpretation too.

Nevertheless, you shouldn’t depend sorely on communication tools. The most basics of communication delivery is also important to master. Firm messages are easiest to understand while properly composed questions will encourage productive discussion and further attention to details. Keep your communication clear and concise. Without it, misinterpretation is bound to happen and I have seen plenty of problems resulting from the tiniest of misunderstanding.

Any successful project accounts for delivery of work product on time and with agreed and planned quality. Poor communication can result in severe delays, uneven workload and consequently, hinder a company’s growth. Good communication, on the other hand, will attract great clients and bring about the happiest of team to work with.

(Image from MIX’s brilliant Building a Website, Explained)

Posted in Team Add Comment »

My Path So Far

Posted by Syazwan Hakim on May 1, 2010

“We are a company of perfectionists and working in this team has made me one too.”

Syazwan Hakim writes about the experience that led him to Stampede and what has transpired since. Syazwan is the Front-End Developer at Stampede.

My first experience with computer started in late 1997. Internet was still new and hype for many back then. I remember paying MYR1 for an hour of internet surfing at the nearby cybercafe. Since then, my interest in computer and internet blossomed quickly.

That was the era of addictiveness to Internet Relay Chat for windows or better known as mIRC. I did my very first mIRC Remotes against room menace such as spammers and abusive operators. That was the start of my programming experience.

In 2006, while studying at UniKL Malaysian Institute of Information Technology (UniKL MIIT), I learned to code in C++ and Java. I also did some part-timing, working on simple image processing. It was then that I recognized the importance of web image optimizing and how many different factors affect website load time. I also did some odd jobs at editing content in Joomla. That gave me a whole load of insight as to how Joomla works with HTML and CSS.

The Stampede Time

I was having my internship with a data company in KL when I was asked to try out the position of Front-End Developer at Stampede. Being an undergraduate, seeing real web developers in action has always interests me so I jumped on the plane to meet the lead developer, Dov. With what very little knowledge in programming, I absorbed the work culture and training pretty quickly.

Throughout the learning process in April 2009, I was in Langkawi during the weekends and then hurry back to KL for my internship work during weekdays. Because of the limited time, most of my practice happened remotely.

Dov taught me a few essential front-end guidelines that are important to Stampede: paying very close attention to design details in PSD artwork, W3C validation, cross-browser testing, semantic code and proper documentation among all. Most importantly, he also encouraged me to Google things up to build my web vocabulary.

Under Dov’s guidance, I began work with my first project. It was for one of our clients in the US. I didn’t look back. Back in KL, I started to explore more about HTML/CSS. I’ve found that the only way to truly master building front-end pages is through a lot of practice. So practice and practice I did.

As a rookie, I did encounter issues that I was too green to fix myself. But then again, I have Google. During my first few months at Stampede, I relied heavily on Google and the rest are pure trial-and-error until I’m satisfied that the issues are fixed. Like most of us, I was having a hard time trying to render everything correctly on IE6 and IE7. I didn’t know that Stampede used to cater to IE 5.5 even!

How It Has Been

I think that a front-end developer holds a very unique position in a team. You have to be well-versed in both design and web programming. You need to know what the web designer wants to achieve and how to build the code efficiently for the web programmer. We’re very particular about design details (whitespace, text leading, typography etc) and it’s a very rewarding challenge for me to build webpages that are as accurate to the artwork as possible while still keeping them organized, efficient and valid. We are a company of perfectionists and working in this team has made me one too.

The Road From Here On

Despite the workload, learning new things is necessary too. You shouldn’t get too comfortable with the knowledge you have at present. Take the initiative to try something new and see how far you can go. I’m now going into some Javascripting and using frameworks like Mootools and jQuery. XHTML/CSS templating into Joomla is next on my list. Huge thanks to my Stampede team for their encouragement and guidance.

So that’s my story of how I became Stampede’s front-end developer. How about you? What’s your story?

(photo and more Lego Star Wars by Mike Stimpson)

Posted in Team Add Comment »