DAILY NEWS

Stay Ahead, Stay Informed – Every Day

Advertisement
From an Idea to a Hackathon: Lessons from Organizing Build with AI Makerere



After months of planning, countless emails, sponsor outreach, community workshops, and late nights, we successfully hosted the Build with AI Makerere Hackathon in partnership with Google Build with AI and Major League Hacking (MLH).

The event brought together student developers from universities across Uganda to build AI-powered solutions addressing real-world challenges using Gemini, Google AI Studio, and Google Cloud.

Along the way, I learned invaluable lessons about:

Building partnerships and securing sponsorships
Planning and organizing a hackathon from scratch
Leading a growing developer community
Navigating unexpected challenges
💡 Creating an environment where students could innovate and learn

This experience reminded me that community leadership isn’t about having everything figured out—it’s about learning, adapting, and bringing people together around a shared vision.

I’ve written a detailed reflection covering the journey, the challenges, the impact, and the lessons I’ll carry into future events.

👉 Read the full story here: build-with-ai-makerere-hackathon

I’d love to hear your thoughts or learn about your own experiences organizing community events!

BuildWithAI GoogleAI GDG @mlhacks Hackathon DeveloperCommunity ArtificialIntelligence OpenSource CommunityBuilding Leadership



Source link

Meta Reportedly Got Too Addicted to Google AI Tokens and Had to Be Cut Off



Meta was reportedly minding its own business this past March, just trying to gorge itself on Gemini tokens, and all of a sudden Google said it was cut off. This is according to an anonymously sourced story in the Financial Times. In March, it emerged that Meta was one of the largest companies taking part in the Tokenmaxxing trend—literally evaluating employees by how many AI tokens they were using at work. This moment coincided with another fad: the one for token-hungry agentic AI platforms like OpenClaw, which were being used by anxious software engineers to achieve ostensibly unprecedented new levels of workplace efficiency. Citing “three people familiar with the matter,” the Financial Times now says Google informed Meta that it wasn’t able to keep up with its AI use, and imposed limits on the company’s use of Gemini models. The move has, FT says: “…disrupted and delayed some of Meta’s internal AI projects. Owing to the restrictions, which remain in place, as well as a broader push to streamline AI costs, Meta has encouraged staff to be more efficient with AI tokens — the units that measure AI usage, several people said.” In other words, Meta replaced tokenmaxxing with judicious token-counting. Sad! The burden on Google’s resources, meanwhile, could have helped along Google’s decision in early June to rent compute from SpaceX, the parent company of xAI for $920 million per month.

The FT says other large companies also strained Google’s AI capacity and were subject to caps, but it sounds like those problems weren’t as serious. According to the FT’s sources, Meta was exceptional, even among the other AI high-rollers. Meta and Google declined the FT’s requests for comment.



Source link