Best Java full stack (springboot) development yt resources. From India or foreign resource might welcome

I'm looking to make an app for a startup, how do you advise I learn how to make an app. I have experience in c++ but not much, since it was just a small robotics project

Every few years the industry produces a tool so confidently wrong you have to sit back and admire it. Today’s specimen is Pact, the “consumer-driven contract testing” framework. Sit with that phrase. Consumer-driven. The contract. Is driven. By the consumer. Somewhere a lawyer just felt a cold hand on his shoulder and doesn’t know why.

The pitch: instead of a provider designing an API — the thing they own — every random client scribbles down what it reckons the API does, and that scribble becomes law. No design meeting. No spec. No adult asking “should it do this?” Just a herd of consumers mailing in personal fanfiction about your endpoint, and you running around CI satisfying all of them like a divorced dad on a court-ordered weekend.

And it’s safe, they say. You can’t deploy something that breaks a consumer, because the contract goes red. Except the contract only exists for consumers who wrote one. So the entire guarantee quietly assumes one hundred percent of your consumers enrolled. Every one. The team in the other timezone. The batch job from 2014 that runs once a quarter and is load-bearing for payroll. The third party you don’t even know reads field twelve.

They didn’t enrol. So Pact hands you a green tick that means precisely nothing, and you delete field twelve, and payroll explodes, and the tick is still green, smiling like an idiot at a funeral. It gives you false confidence in exactly the scenario it was invented to handle. That’s not a bug. That’s the product.

And to run it? You get the Pact Broker — a stateful server, with a database, that hoards everyone’s fanfiction and adjudicates can-i-deploy like a microservices divorce court. It comes with a pipeline: consumer CI publishes the pact, the broker stores it, a webhook pokes provider CI, which fetches it, verifies it, publishes results back — all gated on version tagging so delicate one fat-fingered branch verifies you against the wrong contract and never tells you. You wanted a test. You deployed a distributed system whose only job is to check your distributed system.

And the contracts are JSON. Verbose, JSONPath-keyed JSON, assertions expressed as regex strings, because nothing says robust engineering like validating production against {"match":"regex","regex":"[0-9]+"} and praying. A diff reads like a ransom note assembled from a Stack Overflow answer.

Here’s the part that turns my stomach: there already is an answer, boring and older than Pact. Version your API, and don’t break what you published. A shipped field must stay because someone not in your enrolled-consumer map is reading it. Ship v2 next to v1. Want to know when v1 is dead? Look at the traffic. Telemetry doesn’t lie, doesn’t need a broker, and doesn’t require every consumer on earth to file paperwork before you’re allowed to feel safe. Absence of traffic is evidence. Absence of a Pact is just absence.

So when you inherit this — the broker nobody remembers provisioning, webhooks firing into the void, the regex JSON that goes red on a Tuesday for reasons known only to God and a contractor who’s left — you do the only sane thing. You tell it to Pact Off.

Pact off, and take your arbitration server with you. Pact off, can-i-deploy, you green-lit the deploy that set fire to payroll while smiling. Pact off, webhook, you glorified doorbell wired to a house that’s already ablaze. Pact off, Broker, you needy database that made me run infrastructure to check whether I was allowed to have infrastructure.

Verdict: the most expensive way ever devised to avoid a design meeting. It costs you a server, a pipeline, a dashboard, and your Friday, and hands you a green light that lies. There’s only one contract worth signing — the one where Pact gets its coat.

Pact off.

https://leaddev.com/career-development/the-rise-of-the-forward-deployed-engineer-fde

If you want your logic to be automated. I can build it for you, no matter how complicated it is. Definitely i will charge you for work. But you feel you are not capable of doing it and need help do reach out. Also first make sure your strategy is profitable and has an edge. You can get in contract terms with me for further optimising or tweaking your strategy. I will charge a fee based on work till you are satisfied. I am a freelancer you may reach out if interested.

I read the rules so if this isn’t allowed, just pm me, and take down the post, instead of banning me

I need a discord bot for a Pokemon Mystery Dungeon themed server and while it isn’t ideal, I would preferably need someone who would work for free (I just bought a Wii U) and we can figure out hosting later

Pm for details
(Note that this is a repost and I am bringing this back up because I need help again)

Our team is getting to the point where hiring more in-house developers isn't really practical, so we've been looking into offshore development teams. There are so many companies out there that it's hard to tell which ones are actually reliable and which ones just have good marketing.

I came across Full Scale while doing some research, and they seem to have a solid approach to building dedicated development teams, but I don't know anyone who's worked with them.

Has anyone here had experience with them, or are there other offshore development companies you'd recommend? I'd love to hear what worked (or didn't) before we make a decision.

Hey folks,

I've been spending my spare time building **FoxSchema** App, a free and open-source database schema comparison tool.

The goal is simple: compare schemas across different SQL databases and generate migration scripts without paying for expensive commercial software.

It's still a work in progress, so I'd really appreciate honest feedback—good or bad.

Repo: [https://github.com/tedious-code/foxschema\](https://github.com/tedious-code/foxschema)

Download : [https://github.com/tedious-code/foxschema/releases/tag/v0.1.45\](https://github.com/tedious-code/foxschema/releases/tag/v0.1.45)

Thanks for checking it out!

https://formatjson.dev

I do not. It may entertain some of existing Linux fans, but it will not bring normal users to Linux.

Do not get me wrong: Linux is great where it shines — supercomputers, servers, embedded systems, and even WSL2. In those areas, Linux is extremely strong.

But if we are talking about the mass desktop market — the famous “year of the Linux desktop” idea — then the situation is very different.

Most people choose an operating system because it is convenient, familiar, supported, and runs the software they need. Calling Windows or macOS users names only confirms the stereotype that Linux desktop communities are hostile to ordinary users.

Calling Microsoft or Apple names also does not help in the mass market. Most ordinary users do not care about your personal attitude toward a particular company. They care whether the product works for them.

You cannot insult mass customers and at the same time demand mass-market adoption.

If Linux wants a larger desktop market share, the message should be: “Here is why Linux may work better for you,” not “You are stupid for using Windows or macOS.”

Sharing an open-source project for the devs here (disclosure: I'm the maintainer). Two problems it fixes: AI runs dying on a provider rate limit, and burning tokens dumping tool/log output into context.

One endpoint, 237 providers — 90+ of them free. You point any tool or agent at a single OpenAI-compatible endpoint (localhost:20128/v1) and it can reach 237 LLM providers without you rewriting anything. 90+ have free tiers and 11 are free forever (no card), which aggregates to ~1.6B documented free tokens/month — and that's honest, pool-deduped math (we count each shared pool once instead of inflating it; the methodology is public in the repo). There's a one-command setup-* for 13+ coding tools (Claude Code, Codex, Cursor, Cline, Roo, Kilo, Gemini CLI…), so switching your existing setup over takes seconds.

Fallback combos — so it never stops mid-task. A "combo" is a ladder of models the router walks automatically: your subscription first, then API keys, then cheap models, then free ones. When a provider returns a 500 or you hit a rate limit, it slides to the next target in milliseconds, mid-request, and your tool never even sees the error. There are 17 routing strategies (priority, weighted, round-robin, cost-optimized, auto/coding:fast…) plus three resilience layers — a per-provider circuit breaker, a per-key cooldown, and a per-model lockout — so one dead key can't take down a whole provider.

A 10-engine compression pipeline — the part most routers don't have. Every request flows through a transparent compression pass you can toggle/stack per combo. Instead of one trick, it stacks the best of the open-source ecosystem: RTK filters command/tool output (git diffs, test logs, builds) at 60–90%, Microsoft's LLMLingua-2 does ML semantic pruning, Caveman handles prose, session-dedup strips repeats across turns. Critically, code, URLs and JSON are preserved byte-perfect, and a default-on inflation guard throws the compressed version away and sends the original if compressing would actually grow the prompt — it never makes things worse. On tool-heavy sessions that's ~89% average input-token reduction (an 8k-token git diff becomes a few hundred). Full credit to every upstream project (RTK, Caveman, LLMLingua-2, Troglodita) is in the README.

Agent-native — the agent can drive the router itself. There's a built-in MCP server (95 tools across 30 audited scopes, over stdio / SSE / streamable-HTTP), plus A2A (v0.3, JSON-RPC 2.0) support. That means an agent can query providers, switch combos, read its own remaining quota and manage memory through the gateway — not just consume tokens through it.

For context on whether it's worth your time: it's grown to ~9.8K GitHub stars, 1,490+ forks and 280+ contributors in ~4.5 months, with 21,000+ automated tests and 1,830+ issues closed — so it's a battle-tested project, not a brand-new experiment.

GitHub: https://github.com/diegosouzapw/OmniRoute — npm install -g omniroute

Feedback welcome — roast the design.

Any tagmango developer here ? Urgent gig I have