SShortSingh.
Back to feed

Developer Builds AI-Powered Zakat Calculator App in 48-Hour Sprint

0
·1 views

A developer has created Give Zakat, a web application designed to help Muslims accurately calculate and fulfill their obligatory annual charity known as Zakat. The app was built over a two-day sprint using TanStack Start and Tailwind CSS for styling. An AI assistant powered by Google Generative AI was later integrated to answer user questions about Zakat and help locate charity-collecting organizations. The project was initially submitted as part of a Weekend Challenge focused on generosity, then extended using Google AI Studio. The tool also includes a search feature to help users find where they can distribute their charitable contributions.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

How One Dev Team Built a Safer, Smarter AI-Assisted Coding Workflow

A development team has shared the internal AI setup behind their daily engineering work, centered on running AI assistants directly inside a code editor rather than a browser chat window, giving the assistant full access to files, commands, and test results. They run models from two different AI families simultaneously — one to build and one to critically review — exploiting the fact that different model families carry different blind spots. Recurring tasks are codified into structured recipes that embed hard-won institutional knowledge, including past mistakes, so that critical steps are never forgotten or skipped. The team also enforces hard technical blocks — not just text instructions — to prevent high-risk actions like server overwrites or bulk deletions, arguing that a rule without enforcement is merely a note. Their core takeaways are that AI tools should live where the work happens, review must come from a different source than the builder, and past failures must be systematically recorded to prevent repetition.

0
ProgrammingDEV Community ·

Why Shipping Fast Can Quietly Drain Your Startup's Future Capacity

A founder and builder reflects on the hidden costs of prioritizing speed over code quality during early product development. While moving fast to hit the market is often necessary, some shortcuts act as loans against future engineering velocity, making it harder to change or scale the product later. The author draws on firsthand experience building Tinker Payments, a unified payment infrastructure platform, where the complexity of real-world payments exposed the limits of casual engineering decisions. The piece distinguishes between speed that gets a product to launch and speed that keeps a team moving safely after launch, arguing the latter is undervalued by most early-stage founders. The core lesson is that not all technical shortcuts are equal — some are cheap, while others compound into serious long-term constraints.

0
ProgrammingDEV Community ·

Developer builds custom GPS watch app in ~7 AI-assisted iterations without learning the SDK

An experienced developer built a fully functional GPS route-recording app for his Zepp OS smartwatch without studying the platform's SDK, relying instead on AI-assisted vibe coding cycles. The app records motorcycle and hiking routes, allows waypoint marking via physical button without removing gloves, and exports GPX files. Rather than studying the platform first, the developer described desired behaviors in plain language, received code and a QR install link from the AI, then tested each version in real-world conditions. After roughly seven iterations, the original feature specification remained intact with no scope creep, as the developer focused on defending the spec while the AI adjusted the implementation. The process shifted his role from coder to specification writer and field QA tester, with his programming background proving valuable for scoping requests, spotting edge cases, and reporting precise bug descriptions.

0
ProgrammingDEV Community ·

Rising Power Costs Push Data Centers to Track Energy Use at Granular Level

Wholesale electricity costs in the PJM Interconnection region rose 76 percent year over year in Q1 2026, intensifying pressure on data center operators to manage power more carefully. While multiple factors including gas prices, weather, and market design contributed to the increase, the spike underscores that power is no longer a routine background expense for data centers. Operators are being urged to move beyond facility-level utility bills and track energy consumption down to individual racks, servers, and GPU clusters. AI infrastructure compounds the challenge, as large GPU deployments can rapidly shift both power and cooling demand, making idle or underutilized accelerators especially costly. Identifying and reclaiming stranded accelerator capacity can effectively expand usable supply within existing facilities, potentially delaying the need for costly new infrastructure.