Middle Stack Developer

"Hi I'm Klee." "What do I do? Well... I'm trying to coin to term Middle Stack Developer." was the way I introduced myself across my time at Web Directions Code this past week.

I like the idea of calling myself a Middle Stack Developer because I don't like the term Full Stack Developer. I don't believe that one person is able to fill out all the roles of a software delivery team. No, not even with so many companies providing SASS solutions that effectively provide specialists as a service. 

What's a Middle Stack Developer? A general purpose developer, a willing generalist, someone who is happy to work across the the scope of software deployment and delivery while acknowledging that there will be places where they need to differ to a specialist.

That is to say I can work in the browser but need someone to help me make things accessible and beautiful. I'm comfortable with Cloudformation but you'll need someone else to make your AWS instance PCI compliant. I can work with a database but wont be able to define a multi region sharding strategy. I love agile and software development best practices but might not be the best person to drive your organizational change.

In the end my point is a Middle Stack Developer fills out the middle of the software solution. The gooey nougat goodness the is the center of the chocolate bar while the specialists harden the edges with amazing chocolate. In some areas the chocolate will be thinner and some areas it will be thicker and some times the nougat may even poke through, but in the end nougat and chocolate working together is better than either on their own.

I may not always be a Middle Stack Developer but for the moment, I think it's the best way to describe how I see myself with in a software team.

Comments

  1. Anonymous17 May 2022 at 02:32

    I need someone to recommend the best service among those listed on this site?Fullstack Developer

    ReplyDelete

Post a Comment

Popular posts from this blog

Testing functions that use local storage with Jest

Testing functions that use the browsers local storage API seems easy when you know how. Here's a quick run down on how to mock it out with Jest if, like me, you're not familiar with how to test it. In the end it's very little code. Consider the following TypeScript code. import { get, save, key } from "./storage"; describe(save, () => { let setItem: jest.Mock; beforeEach(() => { setItem = jest.fn(); Storage.prototype.setItem = setItem; }); it("should call set item with predefined key and json object", () => { const valueToStore = { value: "toStore" }; save(valueToStore); expect(setItem).toHaveBeenCalledWith(key, JSON.stringify(valueToStore)); }); }); The key lines are in the beforeEach call where the setItem function of the Storage prototype is assigned to an instance of jest.fn() . This allows us to make assertions on what is passed to the local storage setItem API.
Read more

Solving `Empty reply from server` in DotNet Core

tldr; If you’re getting  curl: (52) Empty reply from server  check that you’ve configured Kestrel correctly. Long version I’ve started playing with Dotnet Core and Docker and have had a few issues getting started. I’ve had a little bit of experience with Docker, though only a little. I’ve worked with DotNet previously but never with Core. Environment The setup I’m using is a Windows laptop running Vagrant. Via Vagrant I’m running an Ubuntu Virtual Machine with the Docker run time installed. Feels a litle like inception. Key Problem The key problem that I’ve had getting started was having my Docker container not responding correctly to my curl commands. I get this: curl: (56) Recv failure: Connection reset by peer curl: (52) Empty reply from server Given that I’m not all that familliar with Docker or Dotnet Core I decided to remove one of the variables and set up a simple Express app in a different docker container. This validated that the commmand I was usin...
Read more

Can't resolve DNS Aws

Image
I recently registered a domain for a joke website  saladsimulator.com .  I figured I could whip up the page in a couple of minutes and throw it up on AWS using S3 static site hosting.  All done in an hour or so. What I thought would take an hour ended up in a multi-day ordeal while I tried to get the DNS to resolve.  I went through what seem to be the typical problems. The bucket wasn't configured to be accessible as a website. My bucket wasn't named the same as the website; the bucket needed to be saladsimulator.com to match the domain saladsimulator.com . I got these fixed up and found that it still wasn't working.  I added extra routes in to see if I could Alias or CNAME to a known working site, but they didn't work either. So it seemed it was a problem with something to do with the DNS configuration. After searching around I found a mention in a thread that the name server records in the hosted zone needed to match those in the domain name registrat...
Read more