Vibe coding is sitting back and letting the LLM drive. It is accepting that I don't care what my assembly looks like, why should I care what my javascript looks like? It is trusting an LLM more than the hundreds of library authors who's code I run every npm install.
Interesting conference vibes. There were a few really interesting people doing interesting things. There were also a whole raft of really ambitious people wanting to tell you about the product/company they were launching.
AWS is incredibly powerful. Their products are awesome. Their ability to execute is unparallelled.
Their ability to fumble the ball so completely in some areas is also breath taking. Tagging is one of those features.
Dear Users,
We are shutting down Cyclic.
Effective immediately we are turning off signups by new users.
In two weeks, May 10th, we will begin turning off free tier usage.
We will begin turning off all usage May 31.
In software value is produced by features running in production. Let’s assume a team delivers on average one feature per unit of time. We will call it team velocity. We can plot their feature delivery curve.
When building a startup I rarely have the time to build software in the way I think of as correct. In these situations I find particular pleasure when simple solutions can be "good enough". Best yet is when one of these solutions holds up to increasing numbers of users, employees and use cases. One pattern that manages all of these is using Slack as a searchable event stream DB.
In our journey as Node.js developers, we often deal with various external services such as Google Cloud or Firebase. These services require us to provide credentials that authenticate our application and grant it the necessary permissions to interact with the respective service. This post is about to handle large secrets or files that contain private keys. Google provides files like this. You will see them named a few different things: serviceAccount.json or sometimes serviceAccountCredentials.json. This file contains secret data and is used to authenticate against Google Cloud and/or Firebase.
There are three types of software systems that any company runs. First, high value software systems that drive customer value. Second, the systems necessary to deliver the product or service, but not sufficient as stand alone products on their own. Third, systems that support the business but are not related to the competitive advantage of the company. The fourth type of software system is one that doesn’t exist. Every company has software they chose not to build. This is "Unbuilt Software". To understand how much value organizations are missing out on, we must first better understand each type of software system and how software investment decisions are made.
As an engineer I like to talk about the features of a product. I talk about the product’s implementation and how it was built. I get excited about the internal workings. I have spent days of my life working on features that were never used. I operated under a mental framework that users came from outside and were external to the product. I was concerned with building the product. The users would be there when I was done. So I spent most of my time heads down writing code.