Post details
Before we begin: The content in this article assumes knowledge of table-driven tests in Go.
Before we begin: The content in this article assumes knowledge of table-driven tests in Go.
So, GitHub just got bought by Microsoft and this got me and a bunch of people thinking about the dependence of Go on GitHub as a piece of…
Introduction If you have been working with Go programming language for a while, you would have noticed that a lot of open source packages that you import start with github.com/…. You would then use go get command to download the package and add it to your go.mod file. For instance: $ go get -u github.com/abvarun226/goiplookup What if you did not want this dependency on Github and rather wanted to host your own git server?
Lightspin obtains credentials to an internal AWS service by exploiting a local file read vulnerability on the RDS EC2 instance using the log_fdw extension.
Do you need a staging environment? We've written this short blog post to share how an alternative approach is saving us time, and helping us ship better code.
With all the fuss about Twitter’s promised edit button, and how they might design it, we’re missing a disturbing development — Twitter is using its embedded javascript to edit other people’s sites.
This post is written by Mark Sailes, Senior Specialist Solutions Architect. This blog post shows how to optimize the performance of AWS Lambda functions written in Java, without altering any of the function code. It shows how Java virtual machine (JVM) settings affect the startup time and performance. You also learn how you can benchmark […]
Managing teams has taught me a lot about my own behaviors and motivations. For example, I overworked for a long time. This left me continually teetering on the brink of burnout, and I had no energy left to absorb the typical sorts of organizational changes that happen at any company. Despite doing good work, I handled change poorly, and I picked up the reputation for being difficult to manage. I’d like to say that I learned from my mistakes directly, but the honest version is that I came to understand this dynamic mostly through working with folks struggling from the same issue.
Want to keep up to date, automatically, easily and for free? You Need Feeds. Read an introduction to feeds, view providers, and you'll be well on the way to your own personal one-stop-shop for all your favourite sites.
This was a great talk at Women in Tech when Carol Gilabert did it, and there was a lot of really great things that I took away from it for my own application process 👀
I’m playing Wordle. I love a word puzzle and like many have been hooked by the daily game. I wrote wordle-to-yaml-action to archive my Wordle games to a yaml file....
API-first. "Headless" e-commerce. "Headless" BI. We've seen a resurgence of startups reimagine startups like Shopify and Wordpress, but built for developers and built for composability. The API is the product. There's three major risks to building on an API. (1) Requests and responses aren't always the full contract. What happens
Using else often encourages complexer code structure, makes code less readable. In most cases you can refactor it using early returns.
This is a good tip for any language!
Is the idea after the first resolution it'll rely on OS caching? Still this seems inefficient and in cases of multiple domains resolving to the same IP, incorrect. What am I missing?
I've recently been doing similar with some of my utilities, albeit with an informal comparison between Ruby and Go versions, but would agree that for large, production critical scrips, this is a great way to do it
I've been bitten by pinning to latest versions before and definitely agree that where possible we should make sure that things are pinned exactly.
Then we can use tools like Whitesource Renovate / Dependabot to manage updates automatically.
My colleague Bethan wrote about the work we're currently doing on Federated API Discovery across government. Very much recommend a read about why we're doing it, and we'll be doing more posts in the future about progress, but until then, you can check out the repo
Will work ever love us back? Two millennials disagree.
Thanks to Carol Gilabert for sharing this podcast last week.
Since leaving Capital One, I've realised that a lot of my self esteem and self worth has been poured into my work, and I was (mostly) getting a lot of satisfaction out of work, and enjoyed the fact that I was always busy, with sprint work, out-of-sprint work, and a tonne of internal side projects to work on, as well as general maintenance of libraries, as well as a wealth of proactive production support.
With my new role at the Data Standards Authority, I've been working to strike a better life-work balance, and the lack of "here's a billion things to work on at the same time" that I thought I was thriving on has made me realise that maybe I've been so used to being in this mode that I just assumed that I did enjoy it.
This podcast (and its transcript) is a good look at The Great Resignation, the way that workers across industries have been reconsidering their relationship to work, and with a wealth of options for jobs out here, as well as thinking about not what they want, but deserve.
I'm still working on my own relationship with work and how I find fulfillment in my life, and would recommend you have a listen/read to see if there's anything in there for you, too.