Development

The internet is full of information, mostly related to learning how to do something, but when it comes to software development, I feel the bigger question is why we should learn something.

I love watching the masters at work. Trying to keep up as Rick Harding plows through code in vim, riding along as Sam Jones conducts multiple sessions in tmux, or marveling at Suz Hinton’s setup for live coding inspires me to up my own game and become a more productive developer.

CRUDy contexts can jam up the works in an Elixir/Phoenix application Contexts allow for a separation of concerns between data and business logic. Often times, the first thing we do is add many basic CRUD functions to our contexts which essentially delegate to Ecto.

Web apps are born with a healthy amount of naivety. There aren’t many expectations of what the apps should do so they have the freedom to do… well, anything. This is great for the early stages of development, but as these apps grow and take on more responsibilites a flexible, little app can quickly become hard to manage.

Music composition and production is a large part of my life outside of software development, so much so that I often find myself thinking of ways to draw parallels between the two.

GitHub Actions, the new offering for CI/CD and other automated workflows, is still in beta just out of beta and looks promising. In order to get myself acquainted with GitHub Actions, I used the nodenv test suite as a chance to try it out.

Despite the fact that it’s been around longer than I’ve been a programmer, I feel like the buzz around the Go programming language has increased of late. This might be why, a few weeks ago, the company I’m working with announced their intention to start migrating portions of their Node microservices into Go.

Origami, the ancient art of paper folding, has gone through a modern mathematical renaissance. The folding process was originally passed down between generations orally. Recently, though, artists have developed a way to document the steps to fold a shape with a diagram called a crease pattern.

As promised in “Getting started with FFI: Rust & Unity”, the next steps for any FFI binding is a “zero-copy” bridge for complex data types. In other words our current goal is to pass classes, objects, or structs between the two languages.