Just a while ago, I chanced about this article, briefly explaining about memory utilization of
File.foreach . It made sense — read all the contents of the file at once and “pay the price” in memory cost.
How about writing to a file? I wasn’t able to find any articles directly referencing file write. Well, let’s test it then, shall we? 😆
Writing unit tests in Go ain’t the easiest thing to start with.
Note that I didn’t say that it’s hard to write unit tests in Go. Rather, the “vanilla” test tools may not represent the most intuitive usages, to begin with. However, if you know where to look, it is possible to write effective and understandable tests for your Go applications. It’s even possible to integrate these tools into your environment, and use them to enhance your team’s experience with testing.
I’m here today to share 3 tips I’ve learned over the years, in testing with Go.
As an engineer…
“Why do we declare more than one “class” in a single .go file?”
“That is a very interesting question”, I thought to myself. As I scrambled to find an answer to this very intriguing question, a phrase appeared up in my mind — Go packages.
At school, that was when I was first taught the basics of using Git. The most important and essential of all were
git clone and
git commit, and those were within the first of Git commands that I learned. However, for those who have used Git extensively, these commands barely scratch the surface of this version control software, and there is much more that can be done with Git.
Cue to my amazement when I first learned about Git rebasing many five years ago. …
Speed is of the essence!
API documentation. We need it, we write it, we share it with our teammates. However, to kick start the documentation can be a painful and arduous process.
You got to choose, do you want to generate the documentation automatically from code comments and unit tests, or manually craft the documentation.
The API documentation is usually compiled into a set of HTML files and assets, which brings us to another problem, how and where can we host these files, and can we automate this process?
This is probably a problem that not everyone faces (at least…
Site Reliability Engineering (SRE) and DevOps — these are two terms that have been used commonly over the last decade. It is most commonly used in understanding what goes on “behind the scenes”, as we move from a more traditional on-premise infrastructure, to using cloud providers — like Google Cloud Platform, Amazon Web Services, and Microsoft Azure.
As simple as these terms can sound, it is certainly not a simple task to raise an effective SRE culture in companies, big or small, traditional or progressive. …
Can you only say that you have achieved the status of being a good Software Engineer (SWE), only when you have joined established companies like Google or Facebook? Or do you consider yourself as an established SWE, only when you have attained some senior position, such as Senior SWE, or Engineering Manager?
These were questions that I asked myself ever since graduating from college and joining the workforce — how do I attain my ideal of being a better SWE?
In fact, becoming a better, successful, and respectable SWE is somewhat of an abstract concept. How does one even measure…
It’s been a speedy October, and some would say, November too. Though we are only midway through the month, it’s time for an OCTOBER+NOVEMBER special recap edition 🔥
Why a special edition, you may ask? It’s because of this awesome collaboration:
Once upon a time, I wrote a post about 5 tips to supercharge your learning with Qwiklabs. With the recent surge in many exciting games in Qwiklabs, I decided to write about it again!
For those who are new to Qwiklabs, or even Google Cloud, Qwiklabs is an awesome platform that you can use to learn about Google Cloud. Admittedly, I’m addicted to using Qwiklabs, due to its harnessing of gamification via badges, as evident from my Qwiklabs profile.
“I can’t believe I put off this book for so long… it’s awesome”
I wouldn’t classify myself as an avid reader, which shocked me when I found myself glued to “The Phoenix Project” over the course of 3 days! This book definitely caters to DevOps, developers, IT professionals, and more, but it’s nothing like a technical textbook — rather a journey of an earnest engineer looking at doing things the right way.
This fictional tale follows our protagonist, a VP of IT Operations of a fictional company. Don’t be fooled by that lavish executive sounding position, our protagonist has very…