• 1 Post
  • 77 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle


  • I’ve been using Netlify for smaller apps, but lately Railway has been my go to. Pretty cheap too and it covers mostly everything you’ll need to deploy app regardless of language or framework. Their UI makes it all very easy to manage with the “nodes”.

    Both of those services (as do most) give you the option to load environment variables onto the app itself.

    So the process is normally this: You have env vars you’re using locally like API tokens that you’re putting in your .env during development. Now you’re ready to deploy. Because you’ve gitignored that file locally, you don’t have to worry about secrets being in your code base, but also, because they’re environment variables, you’re framework will see those variables available in the “box”.

    Ultimately, there’s no difference between having stuff in your local .env and injected by a service during deployment. Just make sure the env var keys are the same in each case.

    Hope that’s not too confusing. If so, I’m happy to clarify anything.

    EDIT: also wanna add that Supabase isn’t that bad. It helps you know exactly what you need it to provide for you and then start searching away to see how to slowly put together each of those pieces. With them, I usually start with the Auth stuff, then move on to my database and storage. Functions last if the project calls for them. There’s quite a bit of info out there if you know specifically what you’re wanting to solve at the moment.







  • I personally prefer consistent and smaller releases. It offers less opportunity for big bugs to creep in along with smaller fixes and features.

    I saw agile mentioned here but here’s another suggestion. Agile can be helpful in the right situations but for solo devs/tiny teams, I really recommend looking into Basecamps “Shape Up” method. It uses longer cycles vs shorter sprints with a cool down period in between.

    So in the case of OP, they could set a 6 week cycle and plan for things that can definitely be completed during that time period. Right at the end of the cycle you release. The goal is to finish before the cooldown to give yourself time to breathe and plan what to do for your next cycle. Play around with a fun feature, learn about a new tool or technique you wanna try, organizing your backlog, etc. You don’t want to spill tasks into the cooldown. Else it’s not a cooldown.

    The online version of the Shape Up book is free and can be found here.


  • This is a big one. One of my friends would constantly berate himself like “I’m such an idiot”, “I’m a dumb old dinosaur” anytime he couldn’t fully grasp a new concept. Over time I could tell that it was actually making him less likely to give himself a chance at understanding. And he truly is a smart dude. One day I called him out on it and he just stayed quiet, took a deep breath and said “you’re right. I’m not an idiot, just need time to understand”. He no longer says it and now embraces a mental challenge.




  • I wish I could vape. This is gonna sound stupid, bc it is, but I’m a chronic asthmatic who has smoked for about 20 years now. Been intubated twice for asthma. And yet I still can’t put the damn cigarettes down. I’ve tried patches, gum, hypnotism, medication, you name it.

    Vaping was the only thing that was helping when I switched but believe it or not, it was bothering me way more than a cigarette. Immediate throat scratchiness and shortness of breath. That doesn’t happen with smokes though. I’ve tried all sorts of vapes too. All with the same result.

    Smoking is probably gonna be what takes me out and it sucks that I feel totally powerless. I will say though, that the book “The Easy Way to Stop Smoking” by Allen Carr got me off cigs for about 3 months. Then my grandpa died and it all spiraled back from there.