I don't remember where I read it but I now understand the statement that an API without rate limiting is an exception generator waiting to go off. More specifically, about a week ago I noticed an increased load on my server and several notifications from my uptime monitor.
A few thoughts about my experiences switching from Mac to a ThinkPad with Linux the past year. For context, I'm the founder and maker of Wobaka.com and Bootstrap.email. I work with front/backend development, design, marketing and sales every day. I code primarily in Clojure + ClojureScript
design
I've made quite a few apps the past years. A social network for travel, local activities directory (kind of like Foursquare but for activivites), a word game, a screenshot and bookmarking tool, a design curation, data driven color palettes, a CRM for small businesses. Well. I think you
code
I recently had an issue working on Wobaka.com where the contacts table were taking too long time to re-render. What happened was that when more than 100 contacts were rendered, the UI felt laggy and sometimes froze when changing filters (free text, lead status, etc). I wasn't
bootstrapping
I've spent the past 8 years or so making web applications. Not full time, but as side projects while studying or working. Some have been quite ambitious (a TripAdvisor competitor). Some have solved a problem I've had (Klart, bookmarking with screenshots). Some have accidently become quite
About three years ago I couldn't find a nice way to save inspiration while working on projects (screenshot folder hell 🔥) so I made Klart.io, a place to save bookmarks and screenshots. A few months later I made Pixels, a collection of handpicked lovely designs updated every day.
code
Recently I was working in a monorepo and wanted to set up continuous integration and devlivery for a bunch of microservices. I was surprised that I didn't find any popular library for this and a little excited about coding my own 🤓. The basic idea is that if a
Today I tried to add some user context to Klart.io's issue tracking. This is helpful since it allows you to track which users get what errors. Klart's backend is based on Node and Express so naturally this will target those technologies. My first atempt was
I've been working a lot on improving the test coverage for Klart.io recently. When the app was small I only had a few integration tests doing some API requests and asserting the response. The rest was tested manually in the browser. Now it's growing bigger
code
For the past one and a half year I've been working on Klart.io — A bookmarking with screenshot service. Lately, I've been thinking a lot about whether or not I should make a mobile app for Klart. Sometimes when I'm browsing Twitter, Hacker News
design
One of the best things about making something for yourself is that when you use something every day you will notice issues and make minor improvements all the time. Sometime you find these issues yourself and sometimes users mention them and you realize that, "Oh, yeah, this is a
code
After over a year of collecting designs with Klart for Pixels I thought it would be fun to visualize everything in some way. I really wanted to display all the designs together so I built One Year Of Design ✨ where I show everything in one big grid. If you'
