I think there's a lot to pick apart here but I think the core premise is full of truth. This gap is real contrary to what you might see influencers saying and I think it comes from a lot of places but the biggest one is writing code is very different than architecting a product.
I've always said, the easiest part of building software is "making something work." The hardest part is building software that can sustain many iterations of development. This requires abstracting things out appropriately which LLMs are only moderately decent at and most vibe coders are horrible at. Great software engineers can architect a system and then prompt an LLM to build out various components of the system and create a sustainable codebase. This takes time an attention in a world of vibe coders that are less and less inclined to give their vibe coded products the attention they deserve.
It doesn't always 10x my development but on certain problems I can work 30x faster. In due time, this is only going to accelerate more as tooling becomes more closely integrated into dev workflows.
I wanted to see what you could do to train GPT on custom data. Fine tuning was a dud but I was amazed at what composition tools like LangChain were able to accomplish even on a small dataset.
SEEKING WORK | Based in Laramie, Wyoming looking for remote work
I'm looking to team up with an early stage startup to help them build their MVP to get them to their next round of funding.
I'm a full stack web and mobile application developer with over a decade of experience building a wide variety of apps for companies big and small. I've worked alone and I've also lead teams. I love Elixir & Phoenix, Ruby & Rails, React, React Native, Relay, and GraphQL.
SEEKING WORK - Rails/Elixir/React(Native) Full Stack Web (and Mobile) Developer
Location: Laramie, Wyoming, USA
Remote: Yes (but I'm happy to travel from time to time)
I've got over a decade's experience building innovative web applications using Ruby on Rails. Lately I've been increasingly interested in Elixir and Phoenix for building realtime applications. Also over the past several years, I've witnessed the heavy lifting move to the frontend and I've embraced React, Relay, GraphQL, and React Native on this path. I've worked on large teams, I've worked alone. As such, I've got experience across the full stack ranging from CSS pixel pushing all the way down to writing provisioning scripts for scaling servers.
Over the years, I've worked on a variety of projects from clients as big as a Fortune 50 company to early stage startups. Most recently, I've been working on an IoT/Mobile/Web platform for a very large company. I've spent many years in the eCommerce space helping streamline sales for hybrid online/B&M eCommerce companies. I've integrated with countless APIs.
I'm very interested in building cutting edge interesting apps. If you're looking to build another Facebook, I might not be for you.
I am in the early stages of growing my freelancing into an agency so I've also got a team on call for building out larger projects.
I'd avoid the public shaming but I would threaten legal action even if you aren't prepared to follow through. I might even hire your general counsel to write a threatening letter. And yes, stop working now. As you probably know you should have stopped months ago.
SEEKING WORK - Remote or Short Term On-Site Anywhere in USA
I'm a full stack Ruby on Rails web developer with over 7 years of experience in fields ranging from eCommerce to CMS to VoIP and beyond. I've got experience with legacy Rails, RSpec, Redis, MySQL, Postgres, git, and most other commonly used Rails technologies. I've been doing the HTML/CSS/JavaScript thing for well over 10 years but I've recently begun taking on Ember.js/HTML5/PhoneGap projects.
I also am experienced at system administration and security, especially when it comes to scaling, caching, and optimizing dynamic web applications.
Shoot an email to me at [email protected] and let's setup a time to get on the phone or Skype and discuss your project.
I feel very bad for anyone that uses Nano for any kind of terminal editing. Not to mention there's a whole class of very serious developers that live in the terminal. Nano is the notepad.exe of *nix.
I think many of these comments are failing to mention one of my primary reasons for using vim... the power of being able to use the same editor in a GUI and a shell. It takes me at least a day to setup my workstation for development but if my laptop crashes I can always SSH into my workstation VPS and get work done. It's also nice to be able to edit server configuration files with the same editor that I write code in.
Vim isn't for everyone but if you're a power user that wants to master one text editor and use it for the rest of your life then Vim is that text editor.
I can't connect to any Wi-Fi networks at all. This was an issue introduced by iOS 7. If a software update can break it, a software update can fix it. From what I understand the strain on the CPU from the additional processing required to run iOS 7 causes heat to become an issue for the Wi-Fi chipset.
I witnessed this turnover first hand when I was hired on as a customer service representative at the launch of QuarkXPress 5. This was a major release given that they hadn't released a major version for 5 years! Hilariously enough, we were trained to tout OS X support... via Rosetta. Native support didn't come until QXP6.
While I do think the major reason why Quark failed was due to a lack of a native OSX app, I think there's another major reason... Creative Suite.
The vast majority of desktop publishing users required Photoshop and the pricing difference between Photoshop and Creative Suite was much less than adding (or even upgrading) QuarkXPress. There's also the integration between CS apps that Quark couldn't compete with.
On a sidenote, people have mentioned how Quark was sold to Fred Ebrahimi and he outsourced the vast majority of the engineering staff to India, but did you know he also created Quark City? http://www.quarkcity.com/
I use icinga extensively. It has a better UI but still suffers from the same downfalls the presentation presents. With that said, the solution proposed seems to be incomplete and a step back from what icinga/nagios provide.
I've always said, the easiest part of building software is "making something work." The hardest part is building software that can sustain many iterations of development. This requires abstracting things out appropriately which LLMs are only moderately decent at and most vibe coders are horrible at. Great software engineers can architect a system and then prompt an LLM to build out various components of the system and create a sustainable codebase. This takes time an attention in a world of vibe coders that are less and less inclined to give their vibe coded products the attention they deserve.