April 13th, 2021
If you do Rails, check out this ebook.
I'm working on getting Starter Story down to 100ms server response time. Working on performance stuff is fun and rewarding. Starter Story is so much faster now.
My main takeaway is cache, cache, cache, cache, and cache again. Cache everything.
There is really no downside to caching, other than the risk of showing something outdated if you don't cache in the right way.
My other takeaway is that it's usually something really stupid that makes your app run slow. For me, I finally found it: one line of code that was taking 300ms on every server response. It was so dumb and it was causing nightmare performance issues...
I feel so much more confident on how to get a Rails app to respond in <100ms.
Now I'll start learning more about the frontend and how to serve up JS and CSS faster... That's something I can learn a lot about - I'm basically a n00b on that stuff and it's always scared me.
--
It's kind of crazy just how much you can learn as long as you're motivated. Back when I was a software engineer with a six-figure salary, I knew diddly squat about caching and server performance. I'm such a stronger engineer than I was back then.
It's at least comforting to know I can always be a decent SWE if I'm somehow banned from entrepreneurship.
It also brings me joy to know I could make a lot of money writing code for 2 hours a day for someone else with no stress, yet I choose not to because that would be the easy way out on life.
I'm working on getting Starter Story down to 100ms server response time. Working on performance stuff is fun and rewarding. Starter Story is so much faster now.
My main takeaway is cache, cache, cache, cache, and cache again. Cache everything.
There is really no downside to caching, other than the risk of showing something outdated if you don't cache in the right way.
My other takeaway is that it's usually something really stupid that makes your app run slow. For me, I finally found it: one line of code that was taking 300ms on every server response. It was so dumb and it was causing nightmare performance issues...
I feel so much more confident on how to get a Rails app to respond in <100ms.
Now I'll start learning more about the frontend and how to serve up JS and CSS faster... That's something I can learn a lot about - I'm basically a n00b on that stuff and it's always scared me.
--
It's kind of crazy just how much you can learn as long as you're motivated. Back when I was a software engineer with a six-figure salary, I knew diddly squat about caching and server performance. I'm such a stronger engineer than I was back then.
It's at least comforting to know I can always be a decent SWE if I'm somehow banned from entrepreneurship.
It also brings me joy to know I could make a lot of money writing code for 2 hours a day for someone else with no stress, yet I choose not to because that would be the easy way out on life.