LLMs Need Context, Just Us Context. I need context to understand what you're talking about. Give me a one line Jira ticket and I'll spend the next half hour finding context and probably pestering you for more information. Once I have that, I'll probably
I have worked from home for most of my career and have gone through a few different work space setups to make the most comfortable, productive environment for myself. I am someone who finds office spaces incredibly distracting. They are useful for face-to-face conversations and collaboration, but when I need
tools
As many people have I've been trying out a handful of LLMs to assist with coding. I've found them very useful tackling mundane tasks that might otherwise take me a few minutes, or at times hours, to accomplish on my own This reminds me of a
As software developers it is our job to test our assumptions. So how do you go about knowing, testing, and rethinking them?
In my last post, Strategy First, I explored the importance of having principles behind technical strategy. Starting with guiding principles is important, but team members can feel left adrift if they are only left with principles and no specific actions. Will Larson suggests: ...executives are generally directionally correct but specifically
Technical strategy is not about technology choices. It is about the principles we use to guide our technical decisions.
🎓I am working in Kotlin for the first time. I'm using Kotlin examples in this post to get used to the syntax. See a mistake? I'm still learning! You can treat the examples here as pseudo-code. Happy to hear about better ways of doing things. Composition
I was working on a project recently that had a set of tests titled "Benchmark Tests." "Oh, nice," I thought, "someone was thinking about performance when they wrote this." Then I ran the tests and realized that they were testing that the web server&
GraphQL Tools is a powerful library and has a great handbook to get you started. I wrote a workshop to help people build an understanding of the basics of schema stitching. Follow the README in the workshop below and you'll learn how to merge types, stitch queries across
Ah, morning tea. My favourite. Plug the kettle in and get it going. Oh! How about some toast to go with that. Plug the toaster in and pop a nice slice of sour dough bread in. My favourite. 💥 Power goes out. What happened? "The toaster flipped the breaker!"
graphql
Subschemas in this project often share types, meaning these types need to be merged into the superschema for the gateway. When these types are merged, we have no easy way of knowing which service each field comes from.
performance
Middleware is a piece of code that mediates the request and response to the application server.