If you create an application that streamlines a regular hour-long operation in a two-minutes one, you might have a successful company on your hands. You’ve created value by saving time (and therefore money) to a business, and your client thanks you by giving you a share of the savings.

Keeping data secured online is cumbersome. Nothing beats in simplicity: reusing the same short password, avoiding IP filtering, sharing passwords in clear text, and not having 2FA. Business owners and engaged employees will work through some hoops, knowing what’s at stake. But not everyone will care, which will create vulnerabilities.

Our default approach to productivity is to think of increasing our output. How can we avoid distractions? The afternoon slump? Need less sleep?

When well funded, growing, continually hiring startups are in a market, it’s not necessarily bad news for bootstrapped companies. After some time, a pattern emerges on their pricing pages: High prices with a lot of emphasis on reaching out to the sales team — Or even no publicly available pricing at all.

If for your job, you get a bonus over a certain NPS score, then here is how you can game the system to get it.

“Any plans to raise funds?” is a question I get a lot. Here are a few of the reasons why we intend to stay bootstrapped.

When building a SAAS, every week comes with opportunities to use news tools. Maybe we need to add a new database or to track a new project. Those are almost never first-times. You most likely already have a database currently online.

Lately, we’ve been told HTTPS is finally faster than HTTP. Mostly because of HTTP/2’s multiplexing. In this post, I want to highlight an issue we rarely think about with HTTPS: the slowdown it implies for users far away from your servers. Since we’re usually on the same continent as our servers, we never get to think about this.

I’m sure you’ve had to write some code where you have a few hundred thousand items and need to do some work on them. Performing the jobs serially would be too long. And launching everything at once with goroutines isn’t possible because of some other limitation. You need a worker pool.

They are cases when you need to disable some endpoints of a website as fast as possible. For example, in the case were an issue on an endpoint is causing all of your website to go down. Or because you need to limit the traffic load quickly by sacrificing parts of the API, instead of losing everything.

A few weeks ago we launched our security bounty program. This was a great decision and we should have done it earlier. Over the last few weeks, we learned some key lessons.

Over the last few months, I got to do about a hundred interviews to hire new members of our remote team. Here are the most frequent issues I experienced. Most of them seem obvious, but you would be surprised how frequently they happened.