Skip to main content

You are NOT inadequate. Unless You Are.

Grabbed from Rick Borup

With all apologies to the secret geek!
You are NOT inadequate.: "YOU ARE NOT INADEQUATE.

* You do NOT have to refactor all your code. BUT it would certainly help if you had never written the spaghetti code in the first place.
* You do NOT have to keep up with the latest news from microsoft, and know everythnig there is to know about longhorn, whidbey, avalon, XAML, indigo and star wars III. But if you don't, you run the risk of feeling very sheepish when Microsoft decides to rename all of the technologies (DNA->COM->COM+, FrontPage->Expression, etc) in a few months or years. Just remember to read up on the nearest locations around Washington and BC and pretend they are the latest product code-words. After all, Sammamish will be the latest build of Yakima which will run Whatcom after Whistler gets it Gonads, oops, I meant Monad back.
* You do not have to have perfectly de-coupled tiers in your technology independent SOA software. But don't look for support afterwards from a software architect. After all, architects design solutions, they don't actually build.
* You do not have to comply to every standard, achieve the perfect balance between maintainability and performance. Usability and familiarity. But if you don't, the first time a new browser comes out, users will complain that you didn't keep your software standardized, even though your application was written 5 years ago.
* You don't have to do 'first things first every day' - But don't rely on Outlook to remind you when you need to get it done.
* You DO NOT have to memorize and understand every pattern the gang of four have catalogued. But at least remember to drop their names every now and then - so it appears you don't think Gamma and Helm is something Captain Kirk shot out in Star Trek.
* You do NOT have to read every technical blog, print out every technical article and learn every technical thing there is to learn. But be prepared to be asked about it on your next certification exam.
* You are beautiful just the way you are. And don't change the color of your hair.
* You are brilliant, interesting, wise and fun to be around. Except when you drink, then you become even MORE brilliant, interesting and extremely funny to watch singing karaoke at the conference that is held right next door of the next technical conference you attend.
* You rock. I roll.


Sorry - just had to to do it!

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP