Author: Adam Grant
Total read time: ~12 hours (audio book was used)
Rating: This was a good book! The later parts were abit slow, but overall a good read even for myself where I rarely finish books in two sittings or less!
Are you a giver, a matcher, or a taker?
At least, that was the feeling that the book left me with, throughout the time I was reading it. The book defines these three philosophical stances as the following:
Taker — Someone who takes more than gives to the people around him/her, most often to forward himself/herself.
Matcher —…
There is always the first time. Your first language. Your first script. Your first website.
Not only developers can own websites. With the right knowledge, anyone can do it!
So…how exactly does one get started?
In today’s ecosystem of tools and services, bringing up your own website that is uniquely yours, is no longer an insurmountable task as it was decades ago. You do not need to have your own server rack (or laptop) running persistently in the corner of your room to host your own website/online portfolio.
In fact, it can be quite easy to bring up a site…
CODEX
Just a while ago, I chanced about this article, briefly explaining about memory utilization of File.read vs 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? 😆
Initial hypothesis
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.
Tip #1 — Behaviour Driven Development (BDD) with Ginkgo and Gomega
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.
I’ve used Go for about four years now. In this time, I’ve used it for different purposes — creating scripts, HTTP applications, to name a few. It’s not the easiest language to pick up, as compared to other languages like JavaScript and Ruby (and yea, I love both of these languages too), but you could…
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…
Time flies, even if Turkeys don’t 😆 .
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:
