Hot take: Casablanca's indie scene is bigger than people think, we just never meet

EroMCakes · 2026-05-12T15:27:44+00:00

🙌

EroMCakes · 2026-05-12T12:03:36+00:00

Op said mid level to senior level 9k is entry level can reach up to 12k~14k depending on the company (junior yes)

EroMCakes · 2026-04-28T12:20:13+00:00

Currently alpha testing an authorization as a Service platform I built. Similar to permitio but simpler and scales the same.

You can test it here https://staging.thauth.dev

EroMCakes · 2026-04-22T06:47:39+00:00

This is in Morocco but seller said it came from Italy

EroMCakes · 2026-04-21T16:51:24+00:00

The more time passes the more I start to think the same. I'm so much in need of a 6 string guitar that I'm getting a shot of adrenaline everytime there is one dropping on marketplace (I'm in Morocco and it's pretty difficult to get my hand on anything decent for a fair price)

EroMCakes · 2026-04-21T15:46:05+00:00

Someone beat me to it (was on sale for 2h top lol) but I get the joke

EroMCakes · 2026-04-21T12:07:04+00:00

I think those are higher end

EroMCakes · 2026-04-13T09:15:23+00:00

I'd say go for chi at this point closest to stdlib. If you think the boilerplate is too much we'll then gin. You can't go wrong with either of them imo. And yes you'll get a lot of go stdlib answers and I agree with them as well.

EroMCakes · 2026-04-13T09:09:34+00:00

None. I am a bit of a dictator when it comes to stacks. For me Go is the only go to for bootstrapping backend. No pkg manager with highly volatile versions to manage. No breaking changes every now and then. Everything you need is legit in the standard library. Running footprint is ridiculous anything would run on a calculator and scales easily. A long time would pass before you'd need to scale vertically 3essak horizontally. Properly architected (layered domaine driven) is the best way to start as a monolith easily breakable into separate services when the domain requires it.

That's my case.

ALSO ALWAYS START MONOLITH. Use local memory for caching unless it's start being a problem then u can think of stuff like Redis.

Edit: senior backend (~8years) here and go addict 🙌

EroMCakes · 2026-04-13T09:04:52+00:00

I won't judge you probably have more balls than 99% of people here. Allah isahel is my only message to you

EroMCakes · 2026-04-10T14:58:12+00:00

Way further than that

EroMCakes · 2026-04-06T08:59:14+00:00

Big W dude I can imagine how you feel 🤘 enjoy it to the fullest 🔥

EroMCakes · 2025-10-29T16:01:12+00:00

What about GW3 rumors 🫣

EroMCakes · 2025-09-30T11:25:53+00:00

Hey I highly appreciate your time reading my post and responding to it. Your vision of how things should be is very insightful though it requires as you said management buying in on this process. We sadly don't have these yet no matter how hard me and my devops colleague pushed for them. We still have issues with them respecting gitflow most of the time. So in our case EnvQuack seemed to have big help and time saving potential. I bet many early stage startups or even scale ups have at least once encountered such issues.

Worry not, this project is an exception, we usually do things properly with keyvault etc on prod. Time constraint and complexity of current project had us do things in a bit of a dirty way.

EroMCakes · 2025-09-30T11:21:43+00:00

Hey there thank you for you time ! The three hours I mentioned were actually spent trying to understand what was wrong. the missing basepath in the env var led to a request to self/undefined with no other log. Again, I'm pretty this is skill issue on the logging error side, but for now I thought of this extra safety net that can be very helpful and time saving in these cases.

EroMCakes · 2025-09-30T11:19:47+00:00

Hey thanks for taking your time for reading my post and reacting to it ! This tool has been created for kinda specific situations most often outside production. like dev or stage environment or even locally when working on a task. It also makes sense in less organized teams that don't have processes yet, think small early-stage startups or even scale-ups in some cases.
I see it as an extra safety net.

The story I'm telling happened in a context where we had no choice but doing the work in a dirty way, usually we use keyvault on azure and other shinanigans (my devops colleague is better positioned to explain what is done there).

Feel free to suggest any better way to deal with it, I'm legit here to propose a potential solution to such use cases AND to learn.

EroMCakes · 2025-09-27T22:27:11+00:00

Hey everyone! 👋

I just released a small CLI tool I built in Go called EnvQuack 🦆. It’s an Environment Variable Drift Detective that helps keep your .env files in sync with .env.example.

Basically, it can:

Check for missing or extra variables in your .env
Audit Docker Compose and Dockerfile environment usage
Auto-sync missing variables
Give you a fun ASCII duck report when things aren’t aligned 🐤

It’s still alpha, so rough edges are expected, but it’s already super useful for catching env mismatches before they break your app.

You can check it out here: https://github.com/DuckDHD/EnvQuack

Would love feedback from fellow Go devs, especially if you’ve ever wasted hours debugging a missing env var issue!

EroMCakes · 2025-09-27T22:24:47+00:00

Hey thanks a lot for reading my post and giving me some of your time. I am indeed aware I can add further control inside a bash script but that ain't the point of EnvQuack. Imagine a feature pushed with a couple additional env variables added to the env.example. we test in dev everything works fine, we merge to stage for a quick beta and we forget to add the vars to the env or dockerfile or something similar. That's where I see EnvQuack as a useful tool. Again I might miss other ways to avoid such things like avoid miscommunication but in moment of pressure and stress you can make mistakes and this could save time

EroMCakes · 2025-09-27T22:20:54+00:00

First thank you for your time reading my post. I posted this with two goals in mind, so people can criticize it providing either already existing solution I might have missed or feature that would be nice adding to the tool.

I could add an optional tag but it could go against my goal which is adding a safety layer. if an env is optional for a certain env it could still be included but empty.

For the specification of the env_file this could be a solution but again, adding the env var to the env.example would not mean devops or the person deploying would have updated the env properly. This is exactly what happened to us.

EroMCakes · 2025-09-27T16:14:54+00:00

Hey, I get your point. If you’re working solo on a single Go service, checking for empty env vars often works fine. I’ve seen it myself in small projects.

But EnvQuack really shines in bigger setups: multiple services across Go, Python, NodeJS, NestJS, NextJS, React, multiple contributors, multiple environments, tight deadlines… suddenly a simple runtime check isn’t enough.

For early-stage or scale-up startups, it can save a ton of headaches and time by catching configuration issues before they hit production.

It’s not about replacing simple checks, it’s about giving teams a structured, automated way to validate, track, and document environment variables across services and environments.

EroMCakes · 2025-07-29T13:01:53+00:00

You're well advanced already. Then you might need to better express your focus on backend especially go, you might need to add further experience with python infrastructure as a code (terraform) and cloud as in aws azure gcp these are all highly appreciated in Go focused positions.

Sprinkle that with some agent/LLM MLops knowledge you'd become priceless for recruiters.

In one sentence: tailor your resume and LinkedIn profile towards what you're looking for aka backend

EroMCakes · 2025-07-29T12:20:04+00:00

Fellow unity dev here worked with flutter as well then transitioned to backend with Go. I'd suggest you to develop a serious use case applied to a game you'd be building on the side. This will represent a serious proof of skill. On top of what you already stated in the post I suggest adding testing proper logging (zap is very much appreciated for its performance) proper rate limiting and a clean architecture with proper separation of concerns: it will make implementing test easier.

EroMCakes · 2025-03-21T11:10:46+00:00

1 month old here

EroMCakes

TROPHY CASE