You don’t see things things as they are, you see things as how you are.

I thought was rather wise.  I heard that from a friend and googled to see if I could find the original.  Appears to be from Anaïs Nin, the real version is:

“We don’t see things as they are, we see them as we are.”

Source

Advertisements

Message to Gina Sosa

On the top of Google news today was a Newsweek post in which (my bold):

Another panelist, Gina Sosa, said of the allegations by Ford: “I mean, we’re talking about a 15-year-old girl, which I respect. I’m a woman. I respect. But we’re talking about a 17-year-old boy in high school with testosterone running high. Tell me, what boy hasn’t done this in high school?

Excuse me, Gina, but I’m one of those boys that didn’t do that and would never do that.  And I knew a lot of other 17 boys that were my friends that would never do that.

Sad, that Newsweek gathered a “panel of Republican women” and one of them said this.

 

What is a Full Stack Developer? Two Takes

Take #1

Laurence Gellert’s blog post on “What is a Full Stack developer” is a good summary on the high level expectations of what this phrase might mean to an employer or manager.  He breaks it down into the following categories:

  1. Server, Network, and Hosting Environment.
  2. Data Modeling
  3. Business Logic
  4. API layer / Action Layer / MVC
  5. User Interface
  6. User Experience
  7. Understanding what the customer and the business need

Read his post for a more detailed breakdown if those 7 categories.

Take #2

As John Simmons / Outlaw Programmer so succinctly put it recently:

…”full stack” developers (another way of saying they don’t want to hire enough people to do the job right) that can work on a technology mix that would make most real programmers wince in pain, and nine times out of ten, all they want is to hire someone long enough to clean up the last guy’s mess, or to implement some tech agenda based on some idiot manager’s wrong-headed view of how things should work.

Personally, I think John’s view is more accurate with regards to the reality of how employers use the term “full stack.”  Laurence’s post is accurate at a technical high level but in my opinion is also growing obsolete, particularly items 2-5, when one starts to take into account emerging technologies such as AI, microservices, agent-based and context-based computing.  These technologies completely reshape how we think about data modeling, business logic, the old Model-View-Controller paradigm, and user interfaces.

Junior Devs, Training, and Management

Just a random observation — I’m saddened when I encounter a management mentality that makes no effort to educate their junior devs so they can eventually become senior devs.

If you don’t have a decent knowledge of the programming language, framework and tools you’re working with, the way you “code” is like someone with a 3rd grade vocabulary trying to express a complex thought.

How do you educate junior devs?

  • Code reviews by senior devs.
  • Training sessions given by senior devs.
  • Having time allocated to learn.
  • Instilling an interest in learning!

Realistically though, nothing can overcome the “it’s a job, not a passion” attitude in the junior dev him/herself.  If the junior dev has a passion for software development, they’ll most likely educate themselves on their own time, not just the company’s time.

But then, when they have learned, they’ll move on because the work environment suddenly becomes limited.  An interesting dilemma for management, especially as they can now ask for a considerably higher salary than the company wants to pay for, which is why they hired junior devs to begin with.