Developer Environment


The Developer's Environment:

  • Building
  • Lighting
  • Desk & Chair 
  • PC/Laptop/Mobile
  • Mouse Keyboard & Wristpad
  • Display(s)
  • OS
  • Desktop Environment
  • Language
  • Tools
  • IDE
  • Target
  • Source Control
  • Code Reviews
  • Milestones
  • Test Plan
  • Network, Intranet, Internet
  • Continuous Integration
  • Documentation
  • StyleGuides
  • Code Of Conduct
  • Licenses
  • Forums
  • Wikis
  • Messaging Apps
  • Email
  • Maintainers
  • Release Managers
  • Users
  • Developers
  • Team(s) 
    • Upstream
    • UI/UX
    • Accessibility
    • Marketing
  • Social Media
  • Home Life
  • Existing CodeBase
  • Your Code

At any given point in any (or every) day, one or more of these can become disfunctional. Although it is not great for your productivity, Development can usually continue to get done in this Environment.

Onboarding is critical in a large organization to familiarize a Developer on the finer points of the Environment that the organization supports, supplies, requires, and expects you to integrate into without with little to zero disruptive disfunction introduced anywhere else in the Developer Environment.

Many default to criticizing a new Developer Environment when no onboarding actually took place and most of the availble guidance is: To each their own. Good Luck.

For these reasons and many many more most corporations insist on the dreaded "Standard Client" 

Breaking out of the Standard Client to utilize your preferred tools is a past time as old as coding itself. 

This does not negate the need for them.





Comments

Post a Comment

Popular posts from this blog

Can KDE Save a Dying Windows Platform?

Image
I want to start by telling a story. Bare with me. Once upon a time there was a software engineer. He wrote code, windows code, embedded firmware. He was happy. Then one day a new project is put before him, a project unlike any other he had encountered. It was going to require all new hardware, and the features, wow. Something like this is going to require a full blown Operating System not the usual rinky dink assembly program. Research leads to the inevitable conclusion, Linux. Further Research leads to a graphical toolkit called Qt (pronounced “Cute”.) A request was made and granted for a new workstation to create a new Linux development environment, after all the windows development machine was far too mission critical to muck about with dual booting and virtual machines. This engineer had some Linux experience on the desktop, having a PC or two running it on and off for the last couple of years. He picked his favorite distribution and after a bit more research had a fully worki...
Read more

Died in a Blogging Accident

Image
I keep a Google Trends Gadget on my iGoogle search page to check out what the world cares about. Todays Top ten had me laughing. First off, far too many people are watching "Are you smarter than a fifth grader?" Not only that, they are cheating while playing at home. If you have to use Google then you aren't. Second, I was intrigued by todays #6 entry. Searching on it didn't explain much until I came across this at xkcd.com. Nicely done, not only is it funny (as always with xkcd) , it also skewed Google's trend tracker. XKCD is one of my favorites and it's worth anyones time who enjoys geek humor. If you've never seen it before, be prepared to waste the next hour or so of your life. MrCopilot update 8:20am: There are now 1440 results from google making it the # 1 most dangerous on the list. I'm glad my warped sense of humor is shared. update 24 hrs later: Over 7,ooo results. I should really think about getting out of such a dangerous business. U...
Read more

Windows Platform Death Revisited

Image
After my KDE article , comments are everywhere complaining about the headline. OSNews , Linux.com , and even the Dot . One guy even blogged his grief about it. So here I offer a response. First off, Get a grip. Articles need good titles. This one was too good to pass up. Second, according to the company that produces Windows XP, end of life is Jan 2009, 11 months from now. See Microsoft Lifecycle Third, the article clearly states that my Windows development platform was going unused for months at a time. No more .Net and no more embedded coding. I preferred to use a text editor on the linux box. Kate for embedded, Kdevelop + QT for cross platform apps. In that sense it was dying. Giving me Kate on Windows does a world of good for it's usability. My only question is, Why don't these people ask these questions here? Windows is the market leader, it will be for some time. We all know this. However, I bought my last copy long ago. I recommend it to no-one, I support it not at a...
Read more