stevepotter

I wasn’t talking about unit tests. Was talking about tests that accelerate development, where you can setup everything and test a feature by just pressing enter vs clicking around or whatever. The tests are how you build features, so I don’t consider that boring

There is problem solving in coding, but the bigger problems exist at a higher level and that’s still on you to solve.

Also I’ve been messing with “ai-only” files recently. You make a markdown file that basically tells it what the file does, how it’s used, and point to an API contract in some other file. Then you can run async ai that will try things and only submit a PR of all the tests pass and the perf improves. The files become almost unreadable to be, but I decided to embrace it because they were already unreadable. But so is the output of, say, the protobuf code generator and I never had a problem accepting that

Which to me is why it’s so important to build cooler and crazier shit. A web app to facilitate some business process was always boring, but at least you got to code. Now it’s just boring. The thing I’m building right now is pretty wild, involving computer vision, robotics, and surgery. It’s super complex and without AI, the development would have bankrupted us. But because of ai, we did it and the product is going to FDA this year.

For me, if I can make a kickass testing system that people love so much that they actually build features with it and it’s not an afterthought, then maintenance becomes much easier. It’s often called test driven development but I’ve rarely seen it done in such a way that the dev ex is good enough for it to work.

But say you have that. Then you have great profiling. At that point you can measure correctness and performance. Then implementation becomes less of a focal point. And that makes it a lot easier to concede coding to ai

Agree. I didn’t like being forced to use it. There was some edict based on some different past problems. My service was a devops thing and didn’t really have a data plane. A regular db would have been perfect but would have required some silly high level approval we weren’t willing to get. All that despite being told service teams are free to build how they want

I was such a fan of it that I ended up working there for 4 years. Now I avoid it and encourage others to do the same.

AWS used to have a nifty tool called "policy analyzer" or something that monitored for permissions used by a role so you could scope it down. The other day I had the need for it and when I went to use it, found out they charge something like $9/resource. So I would pay $45/month for metadata monitoring on just 5 things? Nuts. If they knew how to build truly delightful products, they would make something like a role that starts with broad permissions and automatically scopes itself down after some point. And it would be free or at least really cheap.

DDB is hardly a database. The only reason I can think of to use it is for massive amounts of data whose schema and query patterns are guaranteed to almost never change, which is very rare. Need to sort data on a field? Then you have to create a 'secondary index', which is a copy of the table that they charge you for and that is not strongly consistent. Schema change? Good luck with that. And don't you dare ask to use a nice ORM library. But hey it's serverless.

Here's a good one: you stop an EC2 instance and its volume keeps running and you pay for that. If you detach the volume, you still pay. There is no way to 'archive' an instance. And the only way I found out about that was I got hit with a big bill for those volumes with the charge labeled 'EC2 - Other' lol. Not very 'customer obsessed' to me.

My gripes are clearly not important to them because this is old stuff. So all I can do is go somewhere else, which is fine with me

Upper management wants to say they use AI and spend is an easy indicator. That trickles down and ultimately the engineers spending a lot is seen as good. It’s just a lazy measurement, like cloud usage or number of microservices used to be.

Well played

A link to a project that does the exact same thing, except it’s built with Rust

Praise about one their older projects that I used in the good ol’ days

A condescending put down from someone who has expertise in this area but also didn’t read the article and just felt like feeling superior this morning

It would be nice to see some of the software source. I’m super interested and i think I helped pay for it

I keep hearing “they aren’t intelligent” and spit out “crap code”. That’s not been my experience. LLMs prevented and also caught intricate concurrency issues that would have taken me a long time.

I just went “hmmm, nice” and went on. The problem there is that I didn’t get that sense of accomplishment I crave and I really didn’t learn anything. Those are “me” problems but I think programmers are collectively grappling with this.

I used to work for AWS on a service team. I noticed we were spending way too much on provisioned concurrency for dynamo and would benefit from on-demand provisioning. After proving it worked, making the change, deploying, was rather pleased with myself. "Saved $2M in costs by switching to on-demand provisioning" barely made it onto my performance review lol.

I'm just going to stand by until Microsoft is back in everyone's good graces again by releasing some oss software that we all swoon over

I might be wrong but this sounds like an ego issue more than anything. Twice you berated less skilled programmers. I’m skilled as well and it did sting when I realized that a relatively new technology could beat me. But there’s so much more to it, especially PMs. PMs find big high value problems and solve them. The coding should be the easy part. If your coding skills are such a big part of your identity and you enjoy the feeling of superiority, a good therapist (chatgpt maybe lol) could be useful.

I still don't understand why someone would choose to essentially clone some code vs import a library. Suddenly you increase your maintenance burden, lose updates, etc. I've had no problems at all with UI libraries like Mantine. If you follow this logic, why not just clone all your npm repos and build from source. Ultimate control, right? Please help me understand the benefits here, because I tried out shadcn and wasn't into it

I don't think it's hard, it's harder than people think it's going to be. So they get frustrated and start abstracting away, ignoring history and hoping their fresh approach will finally make this thing easy.

We went out of business, but I made a web app for videographers to collaborate during production. Same things as frame.io. This was over 15 years ago. Frontend was pretty vanilla except relied heavily on jQuery. The main section of the app allowed you to commend on specific frames in a video. The code is split up amongst multiple files. Here is one: https://github.com/StevePotter/Takeoff/blob/main/Takeoff.Web...

Look at any of the sibling `app-productions-details*.js` files. Combined they formed a single interface. It was dicey. But damn the interface was snappy. I mean, instant. Code would have been much less these days but probably nowhere near as responsive.

Right. I encourage young devs to build a complex app using vanilla js. Feel the pain of two way state management. Then you’ll gain an appreciation for react. And you’ll learn browser APIs and know when react is overkill because it has its own pain

Can you please elaborate on “smashed”? I’m very interested

Yup. AWS went down at a previous job and everyone basically took the day off and the company collectively chuckled. Cloudflare is interesting because most execs don’t know about it so I’d imagine they’d be less forgiving. “So what does cloudflare do for us exactly? Don’t we already have aws?”

I got emotional thinking about a 13 year old releasing this. No brutal feedback, just proud of you buddy. Keep it going!

This ad nonsense aside, don't buy Samsung refrigerators. They are so awfully made and difficult to service that almost no appliance repair companies will touch them. I got suckered into buying one a few years back and it was awful. The ice maker didn't work, every few weeks I would sop up a gallon of condensation at the bottom of the cheese drawer, and eventually it just died. I went to a local appliance store and they chuckled when I told them. They would never carry that brand. Just fridges, don't want to talk about other appliances.

This was downvoted? That’s sad. I tell folks getting started that they should build something without any framework so they can feel the pain that things like React are built to solve. Understanding the fundamentals is important so you can look at something like hooks as cognitive overhead that needs to be accepted

Ex employee here who built an aws service. Dynamo is basically mandated. You need like VP approval to use a relational database because of some scaling stuff they ran into historically. That sucks because we really needed a relational database and had to bend over backwards to use dynamo and all the nonsense associated with not having sql. It was super low traffic too

Agree on the importance of testing. Among the production-grade codebases I've worked on, I've found that the dynamically-typed ones have more comprehensive testing. It's just so easy to think that a successful compile means your code will work. I've also found that it's harder to set up great test systems for static languages because you often have to modify your logic just to make it testable (looking at you, IoC). A delightful test system is one that engineers will use during development because it saves time, not an afterthought. For whatever reason, I haven't ever found something that provides this type of experience out of the box. In one organization, we spent months building a rig and achieved true TDD. The result was fewer production issues, faster development, and of course, better test coverage numbers. We eventually switched from javascript to typescript, but it didn't compare to the difference that test system made.

Building something that combines software and hardware is so rewarding. Reach out to me if you have questions - steve at redefinesurgery.com

Great analogy!

Hey there, thanks for writing. For those who don't know, the sales reps have to carry in racks and racks of parts. Most go unused but the last thing you want is something to go wrong and not have the piece you need readily available.

I've been in many different ORs and I've found that the rep's knowledge and level of participation varies a lot. Some of these reps have been working with the same products for years, the doc fully trusts them, and could probably perform the procedure themselves. Others not so much.

Thanks, buddy! I'm having fun. There are a few sides to it. There are the actual physical surgical tools that you have to design, test, and manufacture. Then there's the robot that adjusts those tools. That stuff is a lot of CAD and 3D printing. The camera is a big deal and it's a ton of work to get that right. Then of course you have all the software, which is a slew of computer vision models that operate on a local computer in a careful dance of resource orchestration. The software has a lot: UI, grpc services, ml models on containers, inverse kinematics for calculating robot position, hardware interfaces, etc. Then there's a bunch of regulatory, validation, compliance, etc.

To answer your question about expertise, it really depends on what you are interested in. We have some dedicated mechanical engineers with medical device experience. The software is handled by a few computer vision and full stack folks. So there's different skillsets.

I'm a bit of a journeyman and as a result, I am decent across all of it. I always did software and went where the wind blew. It's been 20-something years since I graduated so I've seen a lot. About 10 years ago I got a job I was totally unqualified for, which was R&D for a company that made lab equipment for testing gas and oil. I was solo and had to learn all the mechatronics stuff - CAD, microcontrollers, electronics, etc. Check out this video: https://youtu.be/MA6hnyXx4p4. That specific experience allows me to be the glue in our engineering org.

To work here, you don't need medical experience. We have plenty of that. One of the cool things about engineering, especially software engineering, is that you can float around between verticals. I've learned all about media, finance, petroleum, insurance, waste disposal, etc. The skills translate. If you are purely software, I recommend picking up an Arduino and some motors and building something like a simple pan/tilt mechanism with an accompanying mobile app. Just do it. It might inspire you. I think curiosity and enthusiasm are the most valuable traits one can have.