Skip to main content

ArcReady

One of the avenues for learning I've leveraged this past year is the Microsoft-sponsored ArcReady three hour in-person, bi-monthly seminar. It's held in a dozen or so cities but mine (Columbus, OH) is coming up on February 4th. Click here to register.

[...and before you look at the remaining post and say TLDR: ArcReady is free, there's usually good swag and there are some very cool/smart folks that attend...]

I enjoy ArcReady because more than likely, you won't see a line of code. As developers, we're constantly exposed to writings and presentations with lots of code. For the most part, I like that and feel it's the best way to learn about software development. However, always approaching from a developer perspective tends to lose the forest for the trees.

My opportunities to code have certainly declined over the years but I enjoy coding and can [gasp] actually read a code book and enjoy it (vs. using it as a reference). However, I'm constantly amazed at how frequently technologists fall to pieces when it comes to compiling an entire solution. We spend so much time and expend so much effort in becoming great developers that we never take a breath and say, "Hmmm, should I really have coded a message queueing application from scratch?" Or, for example, we never stop to ask ourselves, "Can I really create something superior in security to Active Directory?" Or even, "These classes are brilliant, but should I have used interfaces instead?"

At times like these, your 5% time investment into something like ArcReady comes in handy. ArcReady (among other venues) helps you to think about software solutions holistically. We need to be more aware of solutions that are out there, tested, in production, and providing value. What's SaaS? What's SOA? What's PopFly? Should I be using them? Are they a better solution than custom application development?

This type of exposure to non-development learning helps us as technologists remain aware of what's out there and help prevent the limiting of our thinking. So, if you're a developer, considering branching out of developer-only content and expose yourself to a bit of solution architecture. ArcReady is a great venue for this.

Comments

Unknown said…
Nice post, man. Good points. Agree!

Popular posts from this blog

Hero Write-up: Now this is Customer Service!

My best friend Scott is president/C-everything of a small northeastern Ohio manufacturing concern, KirkKey Interlock . I hadn't spoken with him for a while and wanted to see how Canton fared with the Blizzard of '08 (that's what they're calling it...not me). I say, "So what's new?" He replies that on Tuesday his primary server (which essentially runs the business) came up with lame with not one, but [a statistically improbable] *two* physical disk failures on a RAID5 hardware array. My friend attempts the fix but gives up pretty quickly after seeing some Linux nasty-grams on the boot screen. His service provider is an old college buddy who lives down in Raleigh, Cerient Technologies led by Jason Tower . Scott couldn't email out because Exchange was on the toasted server. Being creative, Scott started Treo-emailing photos of the screen. Unfortunately, Jason couldn't receive email because a storm had knocked out a lot of local hosting. [Sigh] After...

Certified or Certifiable?

As a senior technology professional, I interview a lot of candidates. I also maintain solid relationships with other folks in the community. Frequently, the topic of certifications arises: A good investment? Valuable? A clear measurement of skill? Consensus appears to draw the line related to one's seniority. If you're (for example) just out of school and looking for an instant creditability boost, by all means pursue a certification. Likely, this credential will assist you in overcoming the "junior" tag and likely land you more interviews and client roles. (Note: I'm going to use the terms senior and junior here...no offense to either. Can't think of a better one word description. I was a junior once too.) In stark contrast, the value of certifications drops off the table around the 2-3 year mark. Some in my circles even perceive certifications as a negative for the senior professional. They think, "If this guy is so solid, why is he wasting valuable...

Lab Management in Visual Studio 2010 Released

In my experience, there's a lot of animosity and poor communication between Development and QA . It's not that they don't appreciate one another so much as they never seem to stay on the same page. QA : "What's the status on defect #4874?" Dev: "Done." QA : "Done?" Dev: "Yeah, I fixed that Tuesday." QA : "Err, ok . Well where is it? I mean where can I verify it?" Dev: "No clue. I committed it Tuesday. It passed unit tests and built successfully." QA : "Alright. I'll track it down." Invariably , QA speaks with the build manager (if there is one) to find the build in which that defect was repaired. After discovering the correct build, now QA needs an environment stood up to house that build. But wait, the UAT environment is currently testing the next release. It can't be disturbed for another week. At this point, the QA person's blood pressure heads for unsafe levels and the Dice.com bro...