Will Microsoft Meet Occupational Programmer’s Needs?

Contents Defining “Occupational Programmer“ Professionals need Industrial Strength Hobbyists need to Learn Occupational Programmers need Productivity Occupational Programmers need Discovery Occupational Programmers need to Experiment Occupational Programmers need Progressive Disclosure Occupational Programmers need their Skills Grown But Don’t Sandbox Occupational Programmers Focus on Languages and Frameworks, not GUI Tools Not Hard to Serve this HUGE …

Clarifying my Microsoft Developer Division Rant

Contents I Ranted and Eric Rebutted While I Respect the People at Microsoft… …They Become Detached Eric Unconsciously Supports my Thesis! Dismissing the Proposal, Not Solving the Problem Not More Power; Transitionality! Today’s Potential Didn’t Address Yesterday’s Deficiency Nor Does an Orphan Address Yesterday’s Deficiency And a Potential isn’t a Solution Yes, there’s Powershell, but… …

Can Microsoft’s Developer Division Compete Moving Forward?

I’ve been planning to blog about this for some time but just haven’t gotten to it. Well here goes… Contents Is Microsoft’s Approach Failing? After Ten Years; Too Little, Too Late? Providing Solutions Frequently Just Not a Priority Core “Real World” Problems Not Addressed Values “Sugar”-Free Over Productivity Focuses on Details, NOT the Big Picture …

Monolithic Complexity vs. Lots of Little Layers

In my opinion, there two (2) approaches to software development methodologies and resultant architectures[1]. In the beginning: Monolithic Complexity Photo by JamesEverett I call the first approach: "Monolithic Complexity" which I characterize by the following: Grand Visions, Marketing defines Software Architecture, Significant Development Budgets, Attempt to Eliminate Constraints, Requirement to Accommodate Infinite Future Scope, Feature …