Kylee Tilley

The current E2E suite for the language. Total: 3369 | Passed: 3369 | Failed: 0 | Skipped: 0 | Suites: 1123 Overall coverage rate: source files: 34 lines.......: 91.5% (8616 of 9420 lines) functions...: 97.5% (699 of 717 functions)

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

It was actually an enlightening conversation as I could tell this IC, with 30+ years of .NET enterprise experience and extremely strong opinions on systems design, was fully in on telling the agent what to build, not how to build it.

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

The interview went well, they scheduled a second one that was supposed to be with an executive if they wanted to offer but it was the IC again. He grilled me on my thoughts on system design, on software delivery, and building robust systems. This spoke to me, it's in my handle here.

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

I'm curious how someone could be such a full believer after my experiences. I asked them a lot of questions to understand because they were clearly very experienced devs. How were they actually using it?

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

What was interesting to me was how they were using agents. These were 50 java/spring boot services/libraries and that senior IC about to retired? A C# dev their entire career. No joke. I luckily have a ton of java/spring boot experience.

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

They were also very open about this team being the first to be using agentic coding at a large level. They were looking for a senior level developer to take over the support side of things so a replacement system could be developed by the IC dev about to retire. I didn't know what to think honesty.

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

So back to my current role. So 50~ APIs & libs exposing a common interface for data from a range of sources out to app dev teams to use. The two senior ICs that have been developing and maintaining this retired. The only dev on the team is a senior architect about to retire. I have an interview.

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

I mentioned being a control freak when it comes to dev & honestly its less about control and more about understanding the systems at work. That is a direct factor in my enjoyment with coding. Analyzing the problem, designing a solution, and iterating. Vibe coding does not check that box for me.

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

I rejected code at a 20:1 ratio easily. It didn't feel like a performance gain. The bigger the task, the worse the rejection rate. It was frustrated as context slowly gets polluted and the problem got worse.

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

Play testing was instant so having hands on the wheel was easy. But this was a well known algorithm. No heavy lifting here at all but that work flow of a tiny piece, rigorously reviewed and tested felt ok to me. Ok enough to see there might be use here.

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

Those two senior level ICs both retired at the same time. They were an all knowing, doing a lot of "hidden" work to keep things going and it was a complete silo. When I applied for the role, I missed the part about it being an AI "augmented" role. I noticed an hour before first the interview.

I was pairing with a dev who commented on the fact that I always resolved merge conflicts by hand versus using a UI. I joked that it's because I'm a control freak and without missing a beat responded "Yup." 😅 Let me tell you about my experiences with agentic coding these last 3 months...

I've started implementing a second number type in the language: u8 I figured it was about as distant to f64 (existing number type) as I could get. After that the rest will be a breeze. Plus that gives me a char type too.

I can now SSH my Mac Mini and start tmux. No more getting up and going to the room to run things.

Maybe one of the biggest diffs I've had.

I've start implementing more than just basic examples in my language. Actually trying to built with it to feel the pain points. I started with a really basic stdout/stderr Logger with log levels. Not too bad but basic. Today I implemented a Date struct with to/from timestamp conversion.

Almost 90% line coverage, 95%+ function coverage. 2346 E2E tests + a few dozen unit tests. There's a lot of low hanging fruit that could push this close to 98% across the board.

I might get string interpolation done tonight. We'll, the start of it at least. let name = "World"; $"Hello {name}"; Nesting is supported and eventually any value that implements the right trait will work.