First, by learning what the agents were and weren’t good at, the team could switch from babysitting every small task to directing agents toward broad, goal-driven outcomes. Second, the velocity of our teams was tied to how many agentic tasks they could run simultaneously. Third, the longer the agents could operate on their own, the better.
When did the amount of time a coding agent can run without intervention become a priority metric? I understand how it can be useful and that we need agents that have the right ability to overcome obstacles, but it feels like a lot of the labs & agent makers out there are focusing on it as it's own metric, which I don't think benefits users nearly as much as it benefits those labs & agent makers. And I think this quote kind of exposes that. They have rationale for points one and two, and then agents running for longer is just... 'better.' Feels like a setup for one day these agents taking 10 hours and 1 million tokens just to come back and say that they updated a single CSS class and now your problem is fixed.
I love what this guy's doing.
He's a purveyor of 3D-printed flutes, both the flutes themselves but also the 3D printing files so you can make them yourself. Cool enough in its own right.
But what really caught my attention was that he figured out how to vibe code his own tuning software. So he prints a flute, then runs the software while he plays the flute and gets immediate feedback on how well it's tuned. He then uses that data to modify the design and just keeps iterating.
I haven't spoken to the guy, but based on some of his reels, I'm assuming he never could have done this without AI-assisted development.
Now I'm off to print some flutes.
The animal mix-up is not ideal, but it’s not a major hurdle to usability. I didn’t seriously entertain the possibility that a deer had wandered into the house, and it’s a little funny the way the daily report continues to express amazement that wildlife is invading. It’s a pretty harmless screw-up.
“Overall identification accuracy depends on several factors, including the visual details available in the camera clip for Gemini to process,” explains a Google spokesperson. “As a large language model, Gemini can sometimes make inferential mistakes, which leads to these misidentifications, such as confusing your dog with a cat or deer.”
Google also says that you can tune the AI by correcting it when it screws up. This works sometimes, but the system still doesn’t truly understand anything—that’s beyond the capabilities of a generative AI model. After telling Gemini that it’s seeing dogs rather than deer, it sees wildlife less often. However, it doesn’t seem to trust me all the time, causing it to report the appearance of a deer that is “probably” just a dog.
I can't tell you how amusing I find it when the AI doubts the user.
Self-hosting just hits different.
I paid my $100 to become an Apple developer, only to be blocked 24 hours later. And Apple couldn't care less.
My journey navigating the sea of options for publishing my blog and portfolio site.
I released my first production app to the Google Play store today!
The app is a timer/reminder for resting your eyes when working at a screen for hours on end. It’s intentionally simple as the purpose of making it was just to go through the process of testing, packaging, and releasing an app to the store. I didn’t want to include any kind of payment processing or user data so as to minimize security risk.
But now that’s done, time to move on to the next one.
I know full well the right way to improve as a dev is to build every day.
The real obstacle for me is deciding what to build. Ideally, I would be working on a unique idea that at least has the potential to become a valuable product. But boy oh boy am I great at talking myself out of just about every single idea. So absent that, I should at least be building replicas (another to-do list app, recipe manager, etc.) just to get in the reps, but then I convince myself that is a waste of time because none of them would ever be able to stand out in the crowd.
Gotta get out of this loop. Just gotta build.
Time to get this blogging party started. I’ve heard consistency is key on these things, so that’s what we’re going for.
I’m nowhere near qualified yet to comment on the actual merits of Tailwind as it relates to most of the other common CSS frameworks (Bootstrap, Bulma, etc), but I do know why I chose to implement it on this blog.
I don’t even remember where I heard or read this, but an experienced dev said that he could immediately identify a site that used one of the more opinionated frameworks, whereas Tailwind wasn’t nearly as easy to spot.
I decided in that moment that using anything other than Tailwind would be the equivalent of showing up to prom in what I thought was the coolest, most unique tux, only to discover that two of my least favorite people were wearing the same thing.
Now it’s been a week since I implemented it (with considerable help from Cursor), and a one hour struggle with a simple alignment issue has shown me just how much I’m in over my head in the CSS waters.
However, and perhaps misguidedly, I’ve decided that I’m not giving up and I’m riding the horse I came in on.Dave Gray's Tailwind CSS Full Course for Beginners has been great so far, although even it is moving pretty quickly for me. And I’ve already gone through most of the CSS stuff on freeCodeCamp.
Yet another example of how AI code assistants can quickly get you over your skis as a novice. Another a reminder to start with basics (even if it makes me look... basic) and then upgrade later as I get more proficient.
Just finished three of the bash tutorials on freeCodeCamp and feels like I’m driving on a freshly plowed road. Not sure how universal this is, but I’ve been blindly copying so many bash commands along this journey so far, and it bothered me so much that I didn’t understand why so many of them worked, or how they worked. I realize that it might be putting the cart in front of the horse a little bit, but I would definitely recommend learning bash earlier than later. Between having the context while you’re developing and also being able to significantly improve your development efficiency, it’s such a great tool to have on your belt.
When individuals “change careers” or “build a new career” they’re careering! They’re swerving to another lane, jumping over the high credential barrier to do so. This introduces the The Careering Model of working. Its based on the verb of career, meaning to move swiftly and in an uncontrolled manner in a specified direction.
Such a carefully considered and well thought out approach to ‘careering.’ Absolutely love this.