Markizano.NET

After giving it a good trial, Supabase is just not working for me. I really did put in some effort to learn how this works and to try to run this stack. For a self-hosted setup, Supabase is just not for me. Here’s why: Out of the Box Docker Functionality Poorly documented issues AI Access is not built-in (as advertised) Self-Hosted != BaaS Scale? Out of the Box Docker Functionality They say it’s supposed to work out of the box … Just clone the code. Copy your project over. Run docker compose up and you’re off and running to the races! Want more customization? Configure as needed! This was not the case for me. I had to heavily mull thru the docs, configuration, learn the setup. Then on top of that, I HAD to setup my own domains (e.g. studio.mydomain.com, analytics.mydomain.com, functions.mydomain.com, et al) because it didn’t do service discovery properly. I also had to change the network type to bridged because the native network type obscurred all the services and for...

I thought this was a great prompt and does well to represent me in this current snapshot of me. This will help others understand me better in the near to mid-future. Prompt If you were to guess at my management style, based on what you know about me now. What would you say that style is, where are my strong points and where are my opportunities for improvement? ChatGPT-4o Based on everything you’ve shared, including how you structure your thinking, prioritize autonomy, and navigate emotional and technical systems, here’s a clear profile of your likely management style , along with strengths and areas for growth. 🧭 Your Likely Management Style 💠 Visionary Builder (with Technocratic-Purple Leanings) You’re someone who: Builds from first principles , not just trends Sees the big picture long before others do Thrives on autonomy , mastery, and meaning Wants others to grow through trust, not control Balances logic with deep emotional awareness You're not the kind o...

Regarding: ChatGPT's recent release of Codex I can see so many ways in which this can go right and wrong and in between. Ways it can go right: Vibe Coding : Developers are starting to learn how to incorporate and use LLM's with coding software. This whole "vibe coding" movement is another tool, not a replacement to writing code. There are far too many edge cases and problems with Vibe Coding that warrants a skilled developer to be able to troubleshoot issues and offer a creative hand where LLM's cannot provide. Developer Workflow : I've seen where folks are starting to learn how to spoon feed the LLM a prompt about a specific context, let it work on that context, review the changes, then work on the next context as completion runs along. This isn't new. I've seen devs plan out their functions before filling the body of them with the operations they should consume. This results in more efficient development and hence the reason why TDD ( Test Drive...

The messed up part about AI that nobody's talking about is how it slows down senior engineers. While it may be great at "Hello world" and simple algorithms, many times, senior engineers are way past this, and don't really need help building boiler plate code because it just doesn't scale. I find myself more often than not, fighting with AI in some cases rather than using it to write stuff for me that I need done quickly. From custom algorithms or complex situations where scale, multiple contexts or hidden details about how computers and coding works that you don't gain from the RactJS tutorials, even design patterns that are gained from learning other languages cannot be captured and implemented by AI just yet (learn how C and C++ works and then tell me you know how to code properly in JavaScript) to its inability to write in Angular vs ReactJS or even use a different language other than Python for a product solution. We all know JavaScript and Python are not...

Scope creep: When the scope of the project exceeds the original instructions and additional features get added in the sprint. Be mindful of this because its very common in various places. Ways to protect yourself: Document every meeting. Don't just take notes, identify action items, who's responsible for them and a summary of what's expected. I usually email them to the team as well, so I have a paper trail of the discussion to be referred later. Identify the full scope to the best of your ability. What will it take to get started? What will it take to completion? Are there any blockers? Are there any dependencies? Where are the blind spots in the project? Stick to the immediate task of the sprint. I have historically been really bad about this because I want to be able to do everything including deliver the moon! However, when assigned a task for a sprint, its important to stick to the ask at hand to avoid having added responsibility mid-sprint and then being ...

I've had a lot of folks around me say they are jumping from their current careers and wanting to get into IT, but don't know where to start. My advice: JUST START. Just like learning a new language, any new skill is going to take time. There's no perfect entry point. With something and rapidly changing and evolving as IT, you will never find solid ground that will give you a lift off more stable than your own workstation or home lab and whatever documentation you can throw together for yourself. You will be your biggest blocker to learning anything. The very first thing you need to do is Dispel, Dismiss and Disprove is the idea that you are stupid and because you don't have any exposure to this you can't learn it or get to know any of it. Let's get one thing clear: you are smart, intelligent, and you CAN do this. I believe in you. And if you don't believe in you, believe in the me that believes in you! (yes, I totally took that from Gurren Lagan, for...