Code & Pepper

29/09/2026

We put our team into four randomly selected teams, handed everyone a GPS, a crossword, and a flag. Then, we sent them into the woods to crack Sherlock Holmes-like puzzles. 🔒

This turned out to be a mistake. Apparently, putting a bunch of developers in front of locked boxes and telling them there’s a logic problem involved means asking for trouble.

The team solved the codes and opened the boxes much faster than expected...

That was one part of our team offsite at Zamek Janów Podlaski.

We also visited the legendary Janów Podlaski stud farm, operating since 1817. We heard the stories behind horses like Bandos and Pianissima, spent a long evening around the BBQ, and had a lovely time together. All without a Jira ticket anywhere in sight.

There were a few moments worth stopping for, too. We celebrated people who have been building Code & Pepper with us for 3, 5, 8 and 13 (!) years. We handed out awards for our internal competitions.

And we recognised people who keep pushing things forward inside the company, from AI and sales to public-sector projects.

Most of our work happens in code, calls, Slack threads and project channels.

For one weekend, it happened around horses, locked boxes, a grill, and a castle!

02/07/2026

E-commerce rebuilds don’t have to break your business. We've built serious ecommerce platforms for companies with messy catalogs, complex logistics, niche industries, and real operational pressure.

Automotive parts.
B2B distribution.
State-specific sales flows.
Inventory-heavy businesses.

The kind of platforms where Magento, Shopify, and WooCommerce can't do it anymore.

See what we've built and how we've done it in our article:

How we shipped a production-ready marketplace faster using Medusa JS, Mercur JS, and Payload CMS instead of building core infrastructure from scratch.

24/06/2026

Before you build healthcare software, name the category. EHR? RPM? Practice management? Diagnostics? Patient app? That decision changes compliance, integrations, data model, and product risk.

Guide here:

15/04/2026

eMerge Americas next week. April 23-24, Miami.
19 years. 500+ projects. 35+ FinTech clients. Here's what we're bringing:

AI integration: Custom LLM deployment, fraud detection, AI-driven analytics. Our engineers build with AI and teach your engineers AI.

MVP development: From idea to live product, fast. We've done it for startups across payments, insurance, and digital health.

Marketplace development: Lending platforms, healthcare staffing, multi-sided marketplaces with real transaction logic.

codeandpepper.com

07/04/2026

We published a guide covering what Rails is, where it fits, where it does not, and how it compares to Node.js,

What is Ruby on Rails? How the framework behind Shopify, GitHub, and Airbnb helps teams ship web apps faster. Use cases, comparisons, and when Rails fits best.

03/04/2026

May your deployments be bug-free and your chocolate eggs plentiful. Happy Easter from Code & Pepper.

02/04/2026

18,3 mln zł w pół roku. Dwa systemy informatyczne dla resortu finansów. A rok temu jeszcze zero kontraktów publicznych... Miło nam poinformować, że podpisaliśmy drugą umowę z Centrum Informatyki Resortu Finansów!

Code & Pepper, software house z Suwałk wygrał przetarg na rozwój i utrzymanie systemu EMCS PL2 nadzorującego obrót wyrobami akcyzowymi w Polsce i UE. Wartość nowej umowy z Centrum Informatyki Resortu Finansów to 11,9 mln zł brutto.

31/03/2026

76% of DevOps teams added AI to their pipelines last year. The DORA report says some of them got worse, not better. Turns out AI code generation without automated testing is just shipping bugs faster.

We wrote a DevOps tools guide that skips the 50-tool listicle format. Each tool is explained by pipeline stage, with picks by team size and a section on what AI tooling is actually ready for production.

Come on, read it.

DevOps tools explained by pipeline stage: CI/CD, IaC, containers, monitoring, security, and AI. Practical guide with tool recommendations for every team size.

24/03/2026

We put together a guide on the 10 practices that actually move DORA metrics, from IaC and trunk-based development to FinOps guardrails and blameless post-mortems. If you are shipping to production in a regulated environment, the compliance automation section is specifically for you.

Probably worth giving it a read.

DevOps best practices for 2026: the principles, activities, and workflows that separate elite teams from the rest. Practical guide with DORA metrics and examples.

17/03/2026

42% of startups fail because they build something nobody wants. Not because the code was bad. Not because the team was weak. Because they spent 12 months and six figures building a full product before a single user touched it.

An MVP prevents that. You build the smallest version that solves one real problem, ship it, and let user behaviour tell you what to build next.
Sounds simple. Most teams still get it wrong.

They build too much (9-month "MVPs" that are full products in disguise). They build too little (a landing page is not an MVP). Or they launch and never look at the data.

We wrote a complete guide to MVP development: what it means, the step-by-step process, realistic cost ranges, and what changes when you are building in FinTech or HealthTech, where compliance is not optional even at the MVP stage.

What is an MVP in software development? Learn the MVP meaning, how to build a minimum viable product, the MVP development process, costs, and common mistakes startups make.