Brian Blake’s Post

This is actual footage of a programmer dodging changing requirements, merge conflicts, bugs, tight deadlines, burnout, outdated documentation, layoffs, and then heading into the weekend. #softwareengineering #programming

One little tip for junior developers and engineers looking to find their first job in the space: Personally if I don't see any well-put-together project made during nights and weekends that isn't a copy-paste of a YouTube video, it raises a red flag. Put in the effort to create something unique and show your passion. This will make you stand out and demonstrate your ability to think independently.

Software Developer 🧑🏻💻 VS Software Engineer 👨🏽💻: Are they interchangeable terms or distinct roles? Cast your vote: A) Same thing, different name B) Developer focuses on coding, Engineer on architecture C) Developer handles front-end, Engineer handles back-end D) Other (share in comments!) Share your thoughts and experiences! #SoftwareDeveloperVsEngineer #TechDebate #CareerGrowth #CodingCommunity #coder

I have a sincere question for all you veteran programmers: What happened to the skill of programming? I hear stories about how it used to be that you could really get any programming job as a programmer because you knew programming with no ifs, ands or buts. These days, all I ever see is "How many years of professional programming experience do you have..." and immediately following, some programming language, framework, industry, dog's breakfast, the whole nine yards. This stratification of the profession once known as programming into "front-end software engineer", "back-end software engineer", "gameplay programmer", "landscape surveying software engineer" (This one isn't a joke), embedded, "fintech", etc feels insulting for my (and presumably any competent programmer's) ability to ***program***. The worst part of course being it feels like what super niche specialization you start out as is where you are kept forever. I have my own suspicions, but I want to hear from others.

🚀 Engineering Leaders! Struggling with a growing product backlog but hesitant to hire full-time engineers in this unpredictable market? 🚀 You're not alone. It's like trying to solve a Rubik's Cube in the dark. You need more hands on deck, but considering long-term hiring commitments feels like a leap of faith. Well, leap no more! Planet Argon is here to lend those hands without the long-term strings attached. We're a team of experienced #RubyOnRails developers ready to tackle that backlog head-on. Our approach? We dive into your project, align with your goals, and push that progress meter forward. All this without the stress of adding permanent seats to your already crowded boat. So, if you're ready to make a significant dent in your backlog this quarter without the hiring drama, let's talk. We’re here to make things happen, and it might be a lot easier on your budget than you'd think. Interested? Drop a comment or send us a message. We're all ears and ready to roll. 🚀 🔗 https://lnkd.in/gH8H2Tzd

The world needs 1000x or more software... Today, one key constraint is the lack of software developers. (over 500k open positions)! It's because tools used by devs are so bad, it takes SO long to build anything? Now, imagine a world where you can build at the speed of your imagination! And, imagine it's at production-worthy scale, resilience, redundancy, etc. That's the world we're building with Canopy! #compose #codeless

Why we hire traditional developers to develop in no/low-code? Last week I had a short discussion about our hiring process and hiring strategy (we have coding assessment in 1st round). The guy asked me why we want people who love to write code for "clicking and drag'n dropping". 1️⃣ No, we do not hire people who LOVE TO CODE. We want people who LOVE PROBLEM SOLVING and creating tech solutions. That's a big difference because the second group is indifferent on how to solve the problem. (code, no-code, 3rd party, sth. else) 2️⃣ Why coding Interview? Coding skill is the best proxy to evaluate your skills as a no-code developer. If you can write a clean code and solve algorithmic assignments, there's high chance you'll do great as no-code developer

I've said the same thing. DX, reusability, clean code, etc, is nice, but it's not a bottom line. It's not user focused. It’s not “the goal”. https://lnkd.in/dxgJv-JK PS: The hallmark of a true "senior engineer" is someone who can align development to a user driven roadmap, but keep the code "clean" along the way.

This is the most common question I receive. Do you have ______ developers? The thing is that it would be risky for you to hire #developers sitting on a bench waiting for projects. #software #tech #softwareengineer #staffaugmentation