Nothing really prompted this blog other than a cheesy reminder today of a pathetic programming language: ColdFusion. ColdFusion sucks.
If anything can rot the brain more than a crap server side language more, then I haven't found it yet. I mean seriously - ColdFusion blows some serious chowder all over what should or could be a very lucrative internet experience.
I was so pleased when Macromedia was bought by Adobe, for but only one reason - that they would likely KILL ColdFusion. Otherwise I thought "way to go Macromedia! Don't sell out to that (albiet) industry standard and monolithic Adobe!" And then they finally bent over and gave Adobe the keys. Boo Macromedia - BOO!
That's okay though. I was only really invested in Macromedia because I at one time did work in Flash - and used Dreamweaver primarily for coding. Granted, I did not use the WYSIWYG functions - hell no. But I grew accustomed to the coding interface when I worked at that one nameless company that canned me. (I'll get you yet, Jon.) Now I use Eclipse - and couldn't be happier. Plus its free! So screw you guys.
I was a Teenage Web Developer
Just perfect: the internet went and passed me by. Time to put the training wheels back on.
March 11, 2011
February 13, 2011
Perfect Timing?
Its been just a bit weird these last two weeks. I've gotten just as many project requests, although nothing has panned out. Kind of looking forward to maybe busting out of this funk and getting into the swing of things again. I think anyone who's been out there looking understands that there is success in momentum. Just being and doing seems to breed more positive results, regardless of the immediate outcome.
So one unknown project (just word of notice from a coworker with a friend seeking) and one veterinary clinic possibility, are very inspiring to me. I know that these would be tiny projects for sure, but would definitely light the fire and get the ball rolling.
After admitting my lack of business cards, and web site that have not been updated in AGES, it'll be a good place to begin and to be ready. Prepare a portfolio and start networking. WordCamps are coming again - and though I think I already missed the Cloud computing conference in California, I'm going to just have to get out there and find out what more I don't know.
Here's to yours and my... OUR success!
So one unknown project (just word of notice from a coworker with a friend seeking) and one veterinary clinic possibility, are very inspiring to me. I know that these would be tiny projects for sure, but would definitely light the fire and get the ball rolling.
After admitting my lack of business cards, and web site that have not been updated in AGES, it'll be a good place to begin and to be ready. Prepare a portfolio and start networking. WordCamps are coming again - and though I think I already missed the Cloud computing conference in California, I'm going to just have to get out there and find out what more I don't know.
Here's to yours and my... OUR success!
February 7, 2011
Knocked for a LOOP
My first real programming/web dev gig was in Tacoma, Washington. My friend Joel had started a company with three other guys and decided they could take me on.
When they first came up with the idea to make a company like this, I was invited to give it a whirl - but I had some brand new kids that needed something stable, so I had to delay my joining them and kept my illustrious career at Kinko's and then eventually office manager for a Vendor's Rep company in Issaquah.
Their company wasn't bad at all for the most part. All the parts/members of their business were good fits, and what they lacked in business acumen they made up for in dedication and scrappiness. They began with a designer (Joel), two programmers (Joe and Tim) and a sales/project manager (Jon). The only down side to the makeup of the company was that it was a four way partnership - and all four heads were steering the ship, which frequently made conflict resolution difficult.
Ah yes, conflict resolution. The lack of this is why I ended up leaving. While I would suggest my departure was pre-mature, others might suggest that it was perfect timing. When the final pen strokes hit the pages, we agreed that I would quit and go along my merry way. What was the conflict, you may ask? I'll tell you (and for the first time ever).
The company was in the middle of a large project, for their largest client at the time - and I was in the position to animate a demo version of a piece of software. I had just enough experience with Flash to perform the task, though I am sure I was going about it all wrong. While the finished product looked good enough, the actual construction of the animation was a real mess. I took issue with the effort required to pull off the tasks, but with no other options or methods, without learning some serious Action Script (which there was no time for) I was flying solo to meet a deadline that just couldn't be met.
I missed my deadline and the project manager, Jon, ripped me a new one, via email. He made several demands in a demeanor that I thought were uncalled for. After many more hours of work, the demo was done and in his, and the client's hands. A meeting was held with him and our lead programmer, Joe, to discuss the stumbling blocks. They agreed that it was project communication and the strict deadline that was to blame, and that in the future: the programmer to be doing the work would in some way be consulted about feasibility of critical items, like deadlines. All was well in the world again and we were ready to depart the conference room, everyone planning for a great weekend. Right?
You'd think so, but I needed to get something off my chest. I brought up the tone and lack of professionalism in the emails sent to me, and how I felt I didn't deserve that treatment one bit. I ended up missing a family event to complete the project, while Jon spent the weekend with his son, sending me demands remotely from home. I went so far as to say that if he had spoken to me in that tone, in person, to my face, that I would have knocked him out. Probably not the best choice of words.
The next business day I returned to find all of my belongings in a box waiting for me at the front door. The reason being that I was being let go due to threatening the Project Manager with physical violence. Wha!? Truth be told it really wasn't that I threatened him, since it could hardly have been construed that way - but I did tread pretty heavily on his ego. Proof to that point being that in exchange for saying I quit instead of fired, I needed to produce a letter of apology to Jon, and one to the company. Later when I pressed them for specifics on exactly what I was apologizing for - their lawyers had told them to drop the matter and to just agree that I left on my own accord, stripping me of any unemployment benefits, etc.
However, like all good bed time stories - this one has a happy ending. I learned an awful lot about working with designers, and made some lasting friendships, which I would not have had without them. I have gone on to be successful by many standards, and have continued to keep my principles about me. Likewise, I have always treated those I work with and for with total respect and civility... and if I ever run into Jon - I will knock him out! Ha ha ha!
When they first came up with the idea to make a company like this, I was invited to give it a whirl - but I had some brand new kids that needed something stable, so I had to delay my joining them and kept my illustrious career at Kinko's and then eventually office manager for a Vendor's Rep company in Issaquah.
Their company wasn't bad at all for the most part. All the parts/members of their business were good fits, and what they lacked in business acumen they made up for in dedication and scrappiness. They began with a designer (Joel), two programmers (Joe and Tim) and a sales/project manager (Jon). The only down side to the makeup of the company was that it was a four way partnership - and all four heads were steering the ship, which frequently made conflict resolution difficult.
Ah yes, conflict resolution. The lack of this is why I ended up leaving. While I would suggest my departure was pre-mature, others might suggest that it was perfect timing. When the final pen strokes hit the pages, we agreed that I would quit and go along my merry way. What was the conflict, you may ask? I'll tell you (and for the first time ever).
The company was in the middle of a large project, for their largest client at the time - and I was in the position to animate a demo version of a piece of software. I had just enough experience with Flash to perform the task, though I am sure I was going about it all wrong. While the finished product looked good enough, the actual construction of the animation was a real mess. I took issue with the effort required to pull off the tasks, but with no other options or methods, without learning some serious Action Script (which there was no time for) I was flying solo to meet a deadline that just couldn't be met.
I missed my deadline and the project manager, Jon, ripped me a new one, via email. He made several demands in a demeanor that I thought were uncalled for. After many more hours of work, the demo was done and in his, and the client's hands. A meeting was held with him and our lead programmer, Joe, to discuss the stumbling blocks. They agreed that it was project communication and the strict deadline that was to blame, and that in the future: the programmer to be doing the work would in some way be consulted about feasibility of critical items, like deadlines. All was well in the world again and we were ready to depart the conference room, everyone planning for a great weekend. Right?
You'd think so, but I needed to get something off my chest. I brought up the tone and lack of professionalism in the emails sent to me, and how I felt I didn't deserve that treatment one bit. I ended up missing a family event to complete the project, while Jon spent the weekend with his son, sending me demands remotely from home. I went so far as to say that if he had spoken to me in that tone, in person, to my face, that I would have knocked him out. Probably not the best choice of words.
The next business day I returned to find all of my belongings in a box waiting for me at the front door. The reason being that I was being let go due to threatening the Project Manager with physical violence. Wha!? Truth be told it really wasn't that I threatened him, since it could hardly have been construed that way - but I did tread pretty heavily on his ego. Proof to that point being that in exchange for saying I quit instead of fired, I needed to produce a letter of apology to Jon, and one to the company. Later when I pressed them for specifics on exactly what I was apologizing for - their lawyers had told them to drop the matter and to just agree that I left on my own accord, stripping me of any unemployment benefits, etc.
However, like all good bed time stories - this one has a happy ending. I learned an awful lot about working with designers, and made some lasting friendships, which I would not have had without them. I have gone on to be successful by many standards, and have continued to keep my principles about me. Likewise, I have always treated those I work with and for with total respect and civility... and if I ever run into Jon - I will knock him out! Ha ha ha!
February 5, 2011
I might as well start over
I started web developing back in 2002, when: if you could understand HTML and could copy and paste - you were considered a Web Master. Oh my how that title has been misused and now laughed at. I don't think if I ever used that as a description of myself (it was pretty pretentious) - but I know the stigma that came with using it, regardless of your intentions or ability.
Self taught, just enough to land a job at a friend's web dev company, I was slammed face first into server side scripting and the wonders of slicing and dicing web designs. Oh the joys of learning, mastering and then becoming bored with Active Server Pages. Yeah, I was ruined by Microsoft's near-English driven language making it forever more difficult to pick up something more common sense-ical like PHP and even Javascript.
Oh the mass wonder and amusement that followed working with accomplished headstrong designers, and trying to mash the concept of designing for a grid, rather than in their curved, rounded and warped way of designing interfaces. There were no rules or sets of compliances that they would dream of adhering to. But you learn to compensate and make concessions. I did, they did, we all did. Thanks, internet bubble!
I transitioned out of that job and went right into self-employed web development contract work.And of course since I was the first to ever dream of this - I blazed a new trail and became the Lewis and Clark of how running an independent, solo developer web-house should be! I made my millions and retired happy. I failed pretty miserably.
I never got over my apprehension to charging the right rates, or valuing my own experience. While I did become a darn good web site engineer, I succumbed to the the fatal trap of landing one large client. My independent days filled with inspiration and a free-will, slowly were absorbed and I became nothing more than a responsive robot performing the bidding of a client that would frequently ask for unconventional, unacceptable, and just plain wrong application of the web development arsenal. Looking back, which is more criminal: the violation of the awesome code of web developers, or knowingly crossing those lines?
Back in the saddle and ready to re-brand myself an internet professional - I know enough to to know what I don't know. HTML5? CSS3!? At least the more things change, the more they stay the same. I mean, there is still no standards that are adhered to by all web browsers. Its still a challenge to have your sites look dazzling in all clients, without a mountain of code (something I am opposed to). I have been well trained in still having my work appear as well in IE6 as it does in FireFox (current). Ugh.
So here we go. Time for this pre-apocalyptic 2012 internet makeover. I might as well chronicle it here for future civilizations to read!
Self taught, just enough to land a job at a friend's web dev company, I was slammed face first into server side scripting and the wonders of slicing and dicing web designs. Oh the joys of learning, mastering and then becoming bored with Active Server Pages. Yeah, I was ruined by Microsoft's near-English driven language making it forever more difficult to pick up something more common sense-ical like PHP and even Javascript.
Oh the mass wonder and amusement that followed working with accomplished headstrong designers, and trying to mash the concept of designing for a grid, rather than in their curved, rounded and warped way of designing interfaces. There were no rules or sets of compliances that they would dream of adhering to. But you learn to compensate and make concessions. I did, they did, we all did. Thanks, internet bubble!
I transitioned out of that job and went right into self-employed web development contract work.
I never got over my apprehension to charging the right rates, or valuing my own experience. While I did become a darn good web site engineer, I succumbed to the the fatal trap of landing one large client. My independent days filled with inspiration and a free-will, slowly were absorbed and I became nothing more than a responsive robot performing the bidding of a client that would frequently ask for unconventional, unacceptable, and just plain wrong application of the web development arsenal. Looking back, which is more criminal: the violation of the awesome code of web developers, or knowingly crossing those lines?
Back in the saddle and ready to re-brand myself an internet professional - I know enough to to know what I don't know. HTML5? CSS3!? At least the more things change, the more they stay the same. I mean, there is still no standards that are adhered to by all web browsers. Its still a challenge to have your sites look dazzling in all clients, without a mountain of code (something I am opposed to). I have been well trained in still having my work appear as well in IE6 as it does in FireFox (current). Ugh.
So here we go. Time for this pre-apocalyptic 2012 internet makeover. I might as well chronicle it here for future civilizations to read!
Subscribe to:
Posts (Atom)