Kylee Tilley ⚠️

Whoa, Rust HAD a garbage collector way back when? 🤯

I spent last night implementing hindley milner type inference in a small scale project. The type inference I have in my language now is largely adhoc rules that has started showing signs that it won't scale.

I'm just skimming through Rust's RFCs after seeing the become keyword make it to nightly. It's really interesting seeing earlier forms of a language and reading through proposals for syntax features you use every day.

So... let me tell you about the story I'm working on at work...

I've been asked a lot about what it takes to be a tester or think like one. For me it's my gut and that came from years (decades) of development experience and pain. When I look at systems, code, designs, what I really see are error scenarios and risk. That came before I became a tester.

If I'm feeling pain in my gut, something is wrong somewhere. I'm not talking about minor design issues either. I'm talking about things that WILL bite us down the road.

I've learned to really trust my gut when it comes to technical designs. Even if you can't put your finger one what's wrong, I'm feeling indigestion.

Ah... That's right. I was updating the language so that types are parsed as expressions. I can't remember why though. Time to slap these changes in to a WIP branch. I'm sure I'll run into the why again soon enough.

Maybe that's why I took a year long break from it?

GitHub - egonlang/egonlang: A toy statically typed interpreted language A toy statically typed interpreted language. Contribute to egonlang/egonlang development by creating an account on GitHub.

Me: Let me go check in on this project. Hmm. Last commit was almost a year ago...

Oh god. What are all these uncommitted changes in the typechecker? What was I doing?? 😭

Just throwing this out there, but if climate change was a hoax, republicans wouldn’t being trying to destroy the sensors that are measuring climate change signals, they’d just be publishing the numbers showing that it’s made up. #OrbitingCarbonObservatory #OCO

How I ported Penko Park to Switch: From crashes to rock-solid 60 FPS - Ghostbutter A technical deep-dive into solo-porting a Unity game to Switch, overcoming boot issues, memory crashes, and achieving stable 60 FPS performance while maintaining visual quality.

"that most performance wins come from iterating on small fixes and measuring a lot (not guessing)"

Sausages and cheese, German supermarket

the scenario we all feared

I wanted to be able to know the rolling balances based on planned, pending, and completed transactions to display them on the timeline.

I was able to piggy back off this to display those balances on each day on the calendar. This timeline data object might become THE api displaying data in frontend

Postage stamp style image of Golden Gate Bridge with San Francisco California text

Hey SF/Bay Area quality engineers!

We’re hosting a little summer social on Thursday, August 14th at 6pm.

Join us for craft brews, new connections, and great conversations. All are welcome. partiful.com/e/vC4tmRhHB3...

#SoftwareTesting #SanFrancisco

💯 Tests will still pass, even if you built the wrong thing. Tests are a reflection of your understanding of requirements.

Listen to your users. They will tell you if you're building the right thing. AI will never, accurately, automate that if there's a human users somewhere downstream.

Oh and the app runs from a single 7mb~ binary inside a native WebView.

This kind of setup isn't for every app but wow it's really nice to development in.

Maybe I should start a consulting agency where one of our primary selling points is not outsourcing to AI. 🤔

Mantine

The rest of the UI is almost entirely Mantine. Easily one of the best component libraries I've used for react.

Drag and drop to create transactions.

Other features planned

- Budget spans/ranges
- Expense buckets for those budget ranges e.g. food, gas
- Splitting a bill's payment (like a house payment) across multiple budget spans. Not making the payment but reserving the money

GitHub - wojtekmaj/react-calendar: Ultimate calendar for your React app. Ultimate calendar for your React app. Contribute to wojtekmaj/react-calendar development by creating an account on GitHub.

The calendar is powered by react-calendar. It's a powerful component out of the box but I plan on forking it at some point for some specific modifications

- Don't navigate when clicking neighboring month's days
- Provide the first and last displayed dates on the calendar at any given time

All the data querying on the frontend is being done through tanstack query. Mutations to transactions, bills, and other things invalidates the timeline query cache so everything stays in sync in realtime. It's very nice to develop against.

Speaking of the timeline data. It's really interesting because I generated it for the timeline view but that timeline data has become an API/data source for other parts of the app as well. The calendar view pulls next due dates and auto pays from the timeline data it caches for the timeline view.

There are still a lot of features to add

- Multiple bank accounts
- Checkpointing (this is the confirmed balance EOD this date, regardless of what transactions are entered in the app)
- Generating the timeline data out indefinitely. I already have the code in place for this

I've been working on a budget planning tool

- High level dashboard (still WIP)
- Timeline view of events
- Calendar view with drag & drop transactions (planned, processing, complete), drag & drop bills, due dates/auto pays, rolling balance updates

Note: This is all mock/generated data

I can't speak to the performance aspect but I really the IDEA of ECS for application design. The concept and my limited experience with it aligned nicely with how my brain solves problems.

In practice though most software I work on is not a fit for ECS. Some games I've worked on weren't either 😅😅

Tests tell us our software can work.
Observability tells us our software IS working.

From the rust community on Reddit: Suspicious article in this week’s TWIR issue Explore this post and more from the rust community

Scary stuff.

I'm really starting to see the influx of AI generated libraries being pushed out there.

Either the author has declared it's written by AI or it's obvious from looking at the code and commits/history.

new type of annoying pattern is people filing nonsensical AI-generated issues and other people sending nonsensical PRs trying to fix those issues