u/Pretty_Classic_5058

I kept failing to quit sugar at around day three, always in the evening, always at the same hour. Every app I tried wanted me to log meals. None of them were there at 6pm when it actually mattered. So I built the thing I wanted.

SweetProof is a quit-sugar tracker built around that one moment:

- One tap a day — clean, or slipped. No food diary, no barcode scanning.
- A character that reshapes across your challenge, driven by your real streak. There's no slider to skip ahead and preview it.
- A craving button: sixty seconds of guided breathing plus three alternatives, and it replays the reason you wrote down when you felt strong.
- Reminders that move to the hour you actually slip, instead of a fixed 9am "stay strong" you mute in a week.
- A slip resets the streak but never your total clean days or your badges. There's even a badge for logging a slip honestly.

Free, works fully offline, no account, no ads, no analytics, no data leaves your phone. I'm not selling anything — there's nothing to buy in it.

I need 12 testers for 14 days to get production access. Two steps: 1. Join the group: https://groups.google.com/g/sweetproof

2. Then open: https://play.google.com/apps/testing/com.onebytez.sweetproof and tap Become a tester → Download it on Google Play

Order matters — the Play link won't work until you've joined the group. If you see "not found", you skipped step 1 or the group hasn't propagated yet (give it a minute).

What I'd genuinely like to know: do the reminders arrive at sensible times, does the character actually feel like it's changing, and is the craving screen fast enough to reach when you need it? Bug reports very welcome, blunt opinions more so.

Happy to test yours back — drop your link and I'll join today and keep it installed the full 14 days. Just reply here or DM.

Hi everyone,
I have a question about cache synchronization in a distributed Spring Boot application.
Our current architecture looks like this:

Spring Boot
Deployed on GCP
Around 25 application pods
Redis is used for caching

Currently, when cache data is updated, Redis ensures that all application instances can access the latest data.

We’re considering replacing this mechanism with Kafka for cache synchronization.

My understanding is that when a cache entry changes, we could publish an event to Kafka, and every application pod would consume the event and update its own local cache.

My questions are:

Is Kafka a good replacement for Redis in this scenario?
If I have 25 pods, will every pod receive the cache update event, or does Kafka distribute the message to only one consumer?
Would I need each pod to have its own consumer group, or is there a better pattern for broadcasting cache updates?
Has anyone implemented cache synchronization using Kafka instead of Redis? What are the pros and cons?

I’m trying to understand whether Kafka is the right tool for broadcasting cache update events across all application instances, or whether Redis is still the better choice.

I’ve been thinking about building a password manager, but one question keeps coming to mind: is this market already saturated?

There are already a lot of well-established options like Bitwarden, 1Password, Proton Pass, KeePass, Dashlane, and others. As a developer, it’s hard to tell whether users are still looking for something new or if they’ve already settled on their preferred solution.

I spent most of this weekend debugging an issue in my password manager, and it made me rethink something.

When I started building it, I assumed cloud sync was the obvious choice because that's what almost every password manager offers. The more I worked on it, the more I wondered whether users actually prefer cloud storage or whether they've simply accepted it because there aren't many local-first alternatives.

Going local-first solved a lot of problems. I don't have to maintain authentication servers, store encrypted vaults, or secure customer data in the cloud.

At the same time, it introduced new challenges. Moving data to a new device becomes more complicated. Recovery is harder if someone never creates a backup. Multi-device sync is no longer automatic.

It made me realize that building security software is really about choosing which trade-offs matter most.

For those who have built products where privacy and convenience compete, how did you decide where to draw the line?

I’m looking for a structured learning path for AI. I don’t just want to learn how to use existing models—I want to understand how to build and train them from the ground up.

I want to dive deep into AI concepts, including machine learning, deep learning, neural networks, transformers, large language models (LLMs), optimization, training techniques, and model deployment.

I’m currently enrolled in AI for Everyone, but I’m not sure what the next step should be after completing it. Could you recommend a structured roadmap or sequence of courses that takes me from beginner to advanced, eventually enabling me to build production-ready AI systems and even develop my own models?

hey i am looking for power bank for my iphone 15 there is lot of options anyone using power bank more than 2 year suggest that power bank for me

Beyond communication and meetings, what recurring challenge do you see in fully remote engineering teams?

How have you addressed it?

Recently, our company hired two interns. Their resumes looked very strong, with projects and skills that made them appear to have the equivalent of 3–4 years of experience.

However, once they started working, I noticed a big gap between what was on their resumes and their practical knowledge. I’m not expecting interns to know everything—that’s the whole point of an internship. I also understand that in the AI era, people don’t memorize every syntax or API anymore.

What surprised me was that they struggled with very basic tasks. For example, I asked one intern to copy a specific key from a JSON object, but they copied the value instead. They also had difficulty figuring out a few other fundamental concepts without significant guidance.

This isn’t meant to discourage interns or entry-level developers. Everyone starts somewhere, and internships are for learning. My concern is the growing gap between what resumes claim and what candidates can actually demonstrate.
Has anyone else noticed this during hiring, or was this just an isolated experience?

After the arrival of Claude, my company has started building a lot of AI “skills” to automate the software development lifecycle.

Some of the skills our CTO has created include:
Jira Ticket Creator
Batch Ticket Analyzer
Interactive Tickets
Auto QA
Manual QA Assistant

For example, the Batch Ticket skill reads a Jira ticket, searches across all of our repositories, identifies the likely root cause, and prepares an implementation plan.

Once the code is implemented, it automatically triggers Auto QA, which runs Playwright tests, attaches the test evidence to the Jira ticket, creates a PR against the target branch, and updates the ticket status.

Lately, management has been saying that developers won’t be writing much code in the future—they’ll mainly review AI-generated code.

To be honest, this makes me a little concerned. It feels like they’re gradually building an AI-driven workflow that automates more and more of the engineering process, and I can’t help wondering whether this could eventually lead to layoffs.

Is anyone else seeing something similar at their company? Is your engineering team building internal AI agents or workflows like this, or is this still uncommon where you work?

I’d be interested to hear what your company is doing and how your developers feel about it.

I've been thinking about something lately.

With AI advancing so quickly, it feels like every country now has the technical capability to build its own communication platforms instead of relying on global ones like WhatsApp or Instagram.

Imagine if every country had its own messaging app, social network, cloud services, and AI ecosystem.

One reason this seems interesting is data privacy and regulations. If a country's citizens primarily used services built and hosted within that country, would concerns around GDPR, data sovereignty, and cross-border data transfers become much simpler?

At the same time, I can see some major downsides.

For example, how would communication work between people in different countries? Would we end up with isolated digital ecosystems? Countries like North Korea already have a much more restricted internet, which made me wonder whether this could become a broader trend.

What do you think would happen if every country built and primarily used its own digital ecosystem?

• What problems would this create?
• What benefits would it bring?
• Would it improve privacy and national security, or would it fragment the internet and make global communication much harder?

I'm curious to hear.

I’ve often heard people say that engineers and developers are great at solving technical problems but struggle to think from a business perspective.
Do you think this is just a stereotype, or is there some truth to it?

Why do you think this perception exists?

Have you worked with technical people who also had strong business instincts?

If you’re an engineer, how did you develop your business mindset?

I’m curious to hear perspectives from founders, engineers, product managers, and anyone who has worked closely with technical teams.

I wanted to share a small milestone that means a lot to me.

Today I got my first paying customer for my app on Google Play.

It may not seem like much, but after spending months designing, building, testing, fixing bugs, and publishing, seeing someone decide my app was worth paying for is incredibly motivating.

Building the app was only half the challenge. Getting people to discover it has been much harder.

For those who have already gone through this journey:

* What helped you get from your first customer to your first 100?
* What marketing channels worked best for you?

I'm excited to keep improving the app and learning along the way.

OneVault Password Manager

App Name: OneVault

What it does: OneVault is a private, offline-first password manager for Android that stores your passwords, cards, notes, and 2FA codes in one encrypted vault. No account and no company server — everything is sealed on your device with AES-256-GCM and unlocked by fingerprint, face, or PIN.

Key Features:

• Built-in 2FA authenticator + autofill, with password health score and breach monitoring (HaveIBeenPwned via k-anonymity, so your password never leaves the device)
• Optional encrypted backup to your own Cloud, restorable only with your private Recovery Key (zero-knowledge — not even we can read it)
• Import from LastPass, Bitwarden, 1Password, or any CSV, plus travel mode, secure send, and emergency access

Goal: Launch

Giveaway: N/A

Link: https://play.google.com/store/apps/details?id=com.venzor.lockbox