greenido

yep... we are living in a time that the role of the developer is changing quickly. Boris (Cherny) wrote about it and the TL;DR:

1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship 2. Builder: quickly turns a prototype/idea into production-grade product/infra 3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance 4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit 5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales

More context: https://greenido.dev/2026/05/21/unlock-whatsapp-data-with-lo...

I'm doing it with gemini-cli: 1. analyze '/Users/YOURNAME/Movies/' and for each mp4 file give a meaningful name base on the content of the video 2. analyze '/Users/YOURNAME/Pictures/' and for each image file give a meaningful name base on the content of the image

very cool!

https://ido-green.appspot.com/ started while I was having fun at Google... long long time ago.

Comments/suggestions are most welcome

Still in the early stages...

I still love solving them myself (30-90 min/day, no copy-paste), and private leaderboards with friends feel as human as ever.

If you’ve been coding anytime in the past year, you’ve probably heard the buzz about Cursor — the AI-powered IDE that promises to write your code, clean your code, and maybe even refactor your soul.

It’s built on top of VS Code, so it feels instantly familiar. But the moment you hit that shiny AI shortcut, you realize: this thing is smarter than your codebase and hungrier than your wallet.

After a few months of using Cursor — and after accidentally vaporizing a scandalous number of API tokens — I’ve learned how to stay productive and solvent. And yes, the TL;DR is that you can still combine Cursor with Ollama + local models to get many of these benefits for free. Here are my 8 hard-earned tips to make Cursor your loyal sidekick within the limits of your budget.

Here’s the uncomfortable truth: attackers don’t discriminate by company size. They discriminate by vulnerability.

If you’re a cyclist, runner, or triathlete, chances are you’ve spent more time than you’d like clicking back and forth between Strava tabs to figure out where you gained or lost time on a ride. I’ve been there — juggling two activity pages, scrolling, mentally matching segments, and trying to keep my eyes from glazing over.

A lightweight, self-hosted, dead-simple way to keep an eye on system health without setting up a full Prometheus stack

LLMs are best used as powerful amplifiers of developer productivity—not as autonomous builders.

Like most things in life... the answer is: It depends. In the case --> mostly on the price and the ratio.

What do you wish a new full-stack developer to do before their first day to ensure a smooth onboarding experience?

neuronOS | Bay Area | On-site / Hybrid | Full Time We're a dynamic startup on a mission to revolutionize security and IT software with cutting-edge AI technology. Our goal is to create a next-generation platform that will transform how Security & IT professionals manage and monitor their systems. We're looking for a passionate and experienced Lead Developers to join our team and help shape the future.

More details are here: https://gist.github.com/greenido/692fb7c037946d979d5b23a4fee...

Have a great weekend

Looks interesting - Thank you. I checked some frameworks like: https://builder.vueform.com/ (and the similar ones for React) but not sure yet.

We are using both openAI and Google's Bard. There are some aspects to each of them - but it's still mostly 'WIP'. The main challenge is how to 'tune' these LLMs with our own data as another layer that can improve the overall performance (=quality of answers).

“One of the most important books you’ll ever read.” – Steven Levitt

Google, Meta, and Netflix are part of a small elite group of innovative and successful tech companies of our time. They have made a name for themselves in business and technology.

But what can we learn from them?

This doesn't sounds right on so many levels.

vectra.ai and openai.com

Writing a useful bug report is a critical part of the software development process. A good bug report can help developers quickly identify and fix the issue, while a poorly written one can cause confusion and delay the process. What are your tips to write it?

Are you tired of the never-ending back-and-forth of trying to decide where to meet up with your friends? Do you ever wish there was an easier way to figure out the perfect spot for your next coffee date?

Look no further—Middle Point Calculator is here to save the day :)

This new app takes the hassle out of meeting up with friends.  Just enter up to five different addresses and Middle Point Geo Calculator will quickly calculate the exact middle point between them.  But that's not all—Middle Point Geo Calculator also recommends some of the best coffee shops in the area, so you can get your caffeine fix while you catch up.

Say goodbye to the days of endless texting and arguing over where to meet. With Middle Point Geo Calculator, you can finally find the perfect spot for your next get-together. 

So what are you waiting for?  Try Middle Point Geo Calculator today and never waste time trying to decide where to meet up with your friends again!

It looks like a super helpful option to any commerce site out there. Thank you for sharing it!

I created this project with my kids: https://greenido.wordpress.com/2018/10/09/raspberry-pi-as-se... Fun stuff!

Some books I've enjoyed in the past year:

Wish to laugh?

* Born a Crime, by Trevor Noah

* Yes please! by Amy Poehler

Think?

* Outliers, by Malcolm Gladwell

* Where Good Ideas Come from, by Steven Johnson

* The Emperor of All Maladies and The Gene: An Intimate History both by Mukherjee Siddhartha

Learn (more) about great thinkers?

* Einstein or Leonardo da Vinci or Steve Jobs, by Walter Isaacson

* Shoe Dog: A Memoir by the Creator of Nike, by Phil Knight

Yuval Noah Harari 3 good ones:

* Homo Deus: A Brief History of Tomorrow

* Sapiens: A Brief History of Humankind

* 21 lessons for the 21st century

From time to time, I try to put some good ones over here: https://greenido.wordpress.com/?s=book

The short answer is that you must identify the minimally viable product first. The way to reach this MVP is not easy, but you must do it in order to keep focus and build the most important thing at the start.

As for libraries - You wish to avoid re-inventing the wheel (as it's not moving you forward vis a vis your MVP). So invest time and research for SDKs/Libs that can boost your productivity.

Other good rules to follow: 1. Build a user testing focus group and see if your ideas got a true connection with reality. You will learn A LOT from this. 2. Plan for multiple releases - Don't try to do too much for the first release. Iterate quickly and build your service/product in layers. 3. Measure and analyze your users' actions - It will give you a powerful tool to decide what to do and how to improve your releases. 4. Monetization plan - https://greenido.wordpress.com/2015/07/31/app-monetization-c... (disclaimer: this is a course I've helped to build)

Good luck!

Your product looks very good. But from a browsing 'around' I can't tell how it's different from Medium (and others).

I would focus on that and try to make it clear to the clients (=the ones who pay not consume the content).

Good luck.

Hey Jamest,

I hear you about "...Firebase-powered apps are only as secure as the developers make them..." but I guess, you should try to do your best in order to 'tunnel' developers into the best practices of validating input/output and not relying on the client to send 'safe' data. I know it's easy to say and hard to do :) Nevertheless, it's a great goal to have.

Good luck! Ido