- Open source contributions to Forem and Virtual Coffee highlight how consistent community work compounds over time.
- A Gemma 4 AI post submission shows how open source contributions increasingly intersect with generative AI tooling.
- Three merged pull requests on Forem in a single month is a meaningful benchmark for any early-stage contributor.
- Cleaning up a portfolio and learning Ruby signal a developer deliberately shaping their career trajectory.
- Open source contributions to Forem and Virtual Coffee highlight how consistent community work compounds over time.
- A Gemma 4 AI post submission shows how open source contributions increasingly intersect with generative AI tooling.
- Three merged pull requests on Forem in a single month is a meaningful benchmark for any early-stage contributor.
- Cleaning up a portfolio and learning Ruby signal a developer deliberately shaping their career trajectory.
Open Source Contributions Are the New Resume
Open source contributions don’t get the credit they deserve as career-building tools — until, suddenly, they do. Francis, a developer documenting his monthly progress on Dev.to, just dropped his May 2026 report, and while it’s framed modestly as a personal update, there’s actually quite a bit here worth unpacking for anyone thinking seriously about how developers build credibility in public.
The headline numbers: three pull requests merged into Forem, the open source platform powering Dev.to, plus one additional PR merged into the Virtual Coffee community website. For context, Forem is a non-trivial codebase — it’s a production Rails application serving millions of developers. Getting anything merged there takes real understanding of the codebase, proper testing, and patience with the review process. Three merges in a month isn’t a small thing for a contributor who’s still building momentum.
The Virtual Coffee contribution adds another layer. Virtual Coffee is a developer community focused specifically on inclusion and mentorship — getting a PR accepted there means your work meets the standards of a team that’s very deliberate about quality and culture. Two separate projects, two different codebases, both accepting your work in the same month. That’s a signal worth paying attention to.
The Gemma 4 Angle — Where Open Source Meets AI
One of the more interesting open source contributions this month wasn’t a code commit at all. Francis submitted a collaborative post covering Gemma 4, Google’s open-weights language model, featuring perspectives from developers including @javz, @konark_13, and @codingwithjiro on their real-world use of the model. The post was entered into a Dev.to writing competition with a top-five finish as the goal.
This matters beyond the contest itself. Gemma 4 is part of a broader push by Google to compete with Meta’s Llama series in the open-weights AI space — models that developers can actually download, fine-tune, and deploy without being locked into an API. The fact that developers are writing collaboratively about hands-on Gemma 4 experiences signals genuine traction. These aren’t press releases. They’re practitioners comparing notes.
It also reflects something real happening in developer communities right now: the line between open source software contribution and open source AI contribution is blurring fast. A pull request and a detailed technical post about an open-weights model are both forms of community knowledge work, and smart developers are doing both.
Community Curation and the Posts That Caught His Eye
Beyond his own output, Francis highlighted several community posts that stood out to him this month — and the selection is telling.
The Tailwind CSS debate featuring @sylwia-lask and @freshcaffeine is basically perennial content at this point. Tailwind has been polarising since it launched, and the community never really stops arguing about it. What’s interesting is that Francis admits he likes Tailwind, which puts him in the camp that’s probably more comfortable with utility-first CSS. The debate still has legs in 2026 partly because the tooling around it — particularly with frameworks like Next.js and Astro — keeps evolving, giving both sides new ammunition.
The post from @klaudiagrz, a technical writer sharing how engineers actually perceive documentation, is the kind of content that doesn’t get enough signal boosts. The engineer-versus-documentation relationship is genuinely one of the most underexplored dysfunctions in software teams. Engineers rarely like writing docs; technical writers often feel siloed from the product. When someone bridges that gap with direct observation, it’s worth reading.
Then there’s @jasmin‘s post on LLM API calls, which used GIFs to illustrate request-response flows. Simple, visual, accessible. As LLM integration becomes a baseline skill for working developers — not just AI specialists — this kind of approachable explainer content fills a real gap.
What the Monthly Dev Report Format Actually Reveals
Monthly progress reports like this one are becoming a small genre of their own on Dev.to and similar platforms, and they’re worth taking seriously as a format. What Francis is doing — logging open source contributions, curating community posts, setting explicit goals — is essentially building a public accountability system. It’s uncomfortable to write down goals and then report back on them. That discomfort is the point.
Looking at his June goals, the priorities are: continuing Forem and Virtual Coffee contributions, cleaning up his resume and portfolio, tackling HackerRank, and starting to learn Ruby. The Ruby goal is interesting specifically. Forem is a Rails application. If Francis is getting PRs merged into Forem and then deciding to formally learn Ruby, that’s not coincidence — that’s someone recognising they’ve found a project they care about and deciding to go deeper. It’s the kind of deliberate skill-stacking that compounds over a career.
The DEVenger organisation cleanup he mentioned — inviting what he describes as great-minded individuals — suggests he’s also thinking about collaborative infrastructure, not just individual contribution. Building or maintaining an organisation around developer tooling, even at a small scale, teaches skills that pure coding alone doesn’t: consensus-building, onboarding, governance.
Why This Kind of Consistent Open Source Work Matters
There’s a wider point here that goes beyond one developer’s monthly update. Open source contributions have always been a credibility signal in tech hiring, but the way they’re valued is shifting. It used to be enough to have a GitHub profile with green squares. Increasingly, hiring managers and technical leads want to see the quality of contributions — were they meaningful? Were they accepted by maintainers? Did they fix something real?
Three merged Forem PRs in a month tells a clearer story than a hundred solo-project commits. It says: this person can read existing code they didn’t write, understand its conventions, communicate with maintainers, and produce work that meets the project’s standards. Those are professional skills, not just hobbyist ones.
As developer communities like Dev.to, Virtual Coffee, and others continue to invest in open source infrastructure, the developers who show up consistently — not just for hackathons and sprints, but month after month — are building something that doesn’t show up cleanly on a resume but matters enormously in practice: a track record. That track record, maintained in public, is increasingly the thing that gets developers noticed when it counts.
Source: https://dev.to/francistrdev/monthly-dev-report-may-2026-3gjj
