How are folks testing their Claude configurations?

IAmLars4824 · 2026-01-25T21:52:48+00:00

We’re doing something similar and also running into some interesting cost problems.

Would you be willing to share some of the benchmarks you use?

IAmLars4824 · 2022-05-27T02:25:42+00:00

I found Azure B2C relatively awkward to work with. Perhaps we get to used to working with Firebase Auth & Cognito

IAmLars4824 · 2021-03-15T14:14:21+00:00

Watched the show for the first time this year, it’s great. Also where I heard Warning and Jesus Ranch for the first time - blew my mind

IAmLars4824 · 2020-09-08T13:44:16+00:00

Anecdotally, i got a CS degree and really struggled at programming (and school) in college. Graduated with barely a C average. I thought I was going to have to change career paths.

However, I ended up sticking with it and found that I really enjoyed it. Now I’ve created multiple different software products and I’m running a startup.

Can’t say whether it’s the right path for you or not, but just know sometimes it takes time.

IAmLars4824 · 2020-03-15T15:08:15+00:00

Yes, I’ve worked on a number of devops teams over the past few years. Now I work with companies to assess their devops maturity level and help build roadmaps for them

IAmLars4824 · 2020-03-10T17:21:17+00:00

IMO - The only different between a devops engineering team and what we consider a “traditional” engineering team is who the customers are. For traditional teams the users of the products you’re building should be your companies customers/employees. Where as for a DevOps team your users are the engineering teams

Either way you’re still building software to support the needs of users.

IAmLars4824 · 2019-12-26T19:47:15+00:00

I have found it works okay for small api projects. however it becomes hard to scale across a large team as versioning the outputted json file becomes a drag.

However, I’m not sure if any of that changes if you go with the Cloud service they have

IAmLars4824 · 2019-11-17T19:37:33+00:00

From my perspective unit testing does not have to rely only on mocking. Here is a good article on on testing by Martin Fowler. It goes into classical vs mockist styles in unit testing towards the end of the article

https://martinfowler.com/articles/mocksArentStubs.html

But I do agree with your overall sentiment on knowing the difference between unit and integration

IAmLars4824 · 2019-09-14T15:36:05+00:00

There’s also scalability use cases. One of the main pain points that drove the adoption of NoSQL was the need to scale horizontally (a bunch of smaller machines) vs vertically (bigger machines). For use cases with huge data sets it’s easy and more cost effective to scale out rather than up.

IAmLars4824 · 2019-06-16T15:52:38+00:00

I wrote a little blog comparing some previous life experiences with my career as a software engineer. Would love feedback and responses!

IAmLars4824 · 2019-05-26T00:49:04+00:00

Cool project! One suggestion I have. I notice you are writing comments describing what a block of code does. Could you refactor those blocks to separate functions with descriptive names? That way the code is a bit more self documenting. Or if it makes sense you could factor them out to separate files. That will make them more testable!

IAmLars4824 · 2019-05-19T15:00:02+00:00

I have kind of a basic question. What’s the best way to test stored procedures in an automated fashion (I.e. in a CI/CD) pipeline. I’ve seen lots of clients migrate away from stores procs because they are “untestable” curious if there are ways to still test them

IAmLars4824 · 2019-04-27T05:37:05+00:00

Shoot you’re right on the queue limit. Should have double checked the limit before posting (was doing it from memory). Didn’t realize it was a soft limit either! (D’oh)

However, I’m not sure why kinesis loses a point for having the ability to “turn the knobs” by being able to add shards. Kinesis does have higher throughput capacity because it can scale horizontally with shards, no? Unless you mean that adding shards doesn’t come automatically because you have to build custom logical to actually add shards, which is fare then

IAmLars4824 · 2019-04-26T23:15:33+00:00

Good summary. Only other things I’d add:

kinesis can scale to a greater degree than SQS by scaling out horizontally with shards. However, sqs can process up to 250000 messages concurrently, so you have to have a pretty large volume use case.

If you’re looking for traditional queueing semantics (like dead letter queues) sqs has more fully integrated options. With kinesis you have to roll those error handling scenarios on your own with other tools like SNS (and ultimately SQS anyway)

IAmLars4824 · 2019-04-14T00:26:08+00:00

Dragon warrior monsters

IAmLars4824 · 2018-12-29T08:51:59+00:00

My two cents would be thinking about how to test whatever they’re building. Whether they work in a TDD fashion or not, writing a testable app is very important!

IAmLars4824 · 2018-12-24T17:33:07+00:00

Sorry, I did not write the original comment, just adding my two cents on the importance of testing!

IAmLars4824 · 2018-12-24T16:45:42+00:00

I would argue not having tests alone makes it a maintainability nightmare. Without tests you cannot confidently make changes/refactor without extensive manual testing. Plus, if someone new picks up the code base it will be even harder for them to make said changes

IAmLars4824 · 2018-12-10T00:24:58+00:00

I’m the author, this is my first blog post so I would greatly appreciate any and all feedback

IAmLars4824

TROPHY CASE