Show more

I keep telling myself I should switch to stable Rust, but here I am, still on nightly.

I'm sorry...

I couldn't resist...

These new features...

They're just too tempting...

I love places where you can see "Good night" and "Good morning" at the same time

Goodnight Merveilles Town. I'm off to catch some 💤

I spent some time tonight working on Ledge, a command-line utility I'll be using to help me with my time tracking.

Ledge is written in Rust and is open sourced under the MIT license.

How is anyone supposed to have a serious conversation about Mastodon when the primary terminology is "toot"?

Now what shall I get up to now that I don't have work for the rest of the year?

Step 1: Set up your own Mastodon instance
Step 2: Don't invite anyone else

I wanted to share that Tape is currently 50% off on

I was making a list of walls and junctions needed for an isometric game project and it seems I have accidentally created an alien alphabet.

But all that being said, I am already looking forward to getting back to work in 2019.

I want to come back refreshed and ready to hit the ground running to continue solving problems.

If anyone else has faced similar challenges in your workplace, I would love to chat with you about your experiences.


Slowly but surely I am wooing other developers to my side, but the process is taking much longer than I would have hoped.

I would say that the pace at which change occurs, particularly organizational change, is my biggest area of frustration. I like to "move fast and break things" when I write code, and I keep that same mindset when trying to solve organizational problems.

There are still plenty of challenges that lie ahead, the biggest of which have to do with people.

Some of the older members of the team are very resistant to change in how the code itself is written. It often feels like an uphill battle trying to get everyone to adopt modern standards for writing code. Things like Hungarian notation, too many noisy comments, and other code smells continue to plague our codebases. No matter how hard I try I can't seem to get people to see the light.

I can already feel all these improvements start to pay off and help myself and the rest of the team build better software faster to deliver value to the customer.

3. We upgraded all of our projects to use Paket for dependency management, which should solve a bunch of the pain that comes from trying to manage Nuget packages.

4. We started using FAKE for instrumenting our build and deployment tooling, with the goal of being able to rebuild the world consistently on any machine at any time.

On the flip side, some of my other initiatives are starting to bear fruit.

1. We now have two API services that are fully written in F#, and other bits of F# have squeezed their way into some of our other codebases.

2. Our main React application now uses a design system built on top of styled-components and styled-system, which has done wonders for improving development speed when working on that app. It's taken about 2 years, but all the hard work put into this project is starting to pay off.

As a development team we've been able to complete a lot of deliverables, but in terms of my personal goals I still feel like there are a lot of unresolved tasks.

One of the things that I wanted to accomplish this year was to modernize our legacy API codebase. This is something that has been hanging over my head for a while, but it just seems like it will never get done.

Tomorrow is my last day of work for the year before I take some time off for the holidays and I've been taking some time to reflect on this past year at my day job.

Show more

Revel in the marvels of the universe. We are a collective of forward-thinking individuals who strive to better ourselves and our surroundings through constant creation. We express ourselves through music, art, games, and writing. We also put great value in play. A warm welcome to any like-minded people who feel these ideals resonate with them. Check out our Patreon to see our donations.