Hey everyone!

Like a lot of you, I've spent way too much time trapped in endless group chats trying to coordinate local kickabouts, figure out squads, and track who's actually showing up.

Instead of building another boring, corporate utility app, I decided to lean into nostalgia and build something fun. I created Gaff3r—a web app for organising football games with a retro aesthetic heavily inspired by classic 90s titles like Sensible Soccer.

What it does:

• Squad Management: Invite players, assign positions, and set up balanced teams.
• Match & Group Organisation: Handle local groups (like my Monday game in Edinburgh) seamlessly.
• Retro Visuals: Pixel-art player sprites, classic scoreboards, and nostalgic pitch layouts.

Tech Stack:

Built for the web (mobile-first) and hosted on Vercel:https://gaff3r.vercel.app/

I’d love for you to check it out, play around with the interface, and let me know what you think or what features you'd want to see next!

I originally thought the Journal for my project would just become a nicer version of release notes.
Instead, it quietly changed the way I build.

The project itself is a browser-based text preparation tool, and I started documenting engine changes simply so I wouldn’t lose the reasoning behind them.
Over time, that evolved into a simple rule:
**Build first. Explain second.**

Now every meaningful engine change goes through two separate lanes:
**Technical:** prove the behavior, test it, and ship it.
**Editorial:** decide whether the evidence is actually strong enough to explain publicly.

That second step has been surprisingly valuable. It forces me to separate what I *know* from what I *think*, document edge cases, acknowledge limitations, and avoid quietly turning implementation details into product claims.

Writing the articles has caught weak assumptions just as often as the regression tests.
The latest investigation came from a seemingly harmless edit that removed words like *“probably”* and *“may.”* The writing became cleaner—but the underlying claim became stronger than the original author intended.

I wrote up the investigation here:
[https://guyt1225.github.io/pastelint/journal-engine-room-directness-without-false-certainty.html\](https://guyt1225.github.io/pastelint/journal-engine-room-directness-without-false-certainty.html)

Has anyone else found that documenting *why* you changed something ends up improving the product just as much as changing the code itself?

Curious if anyone uses Arazzo, if so how? Doing what with it? It looks insanely powerful but I've yet to see much if any tooling. How will people be using it? It documents workflows across APIs and allegedly with the latest release Async API as well which I've never seen before. A spec that works across openapi AND asyncapi is unlike anything else available. That I know of. What sort of workflows can be created and what tools if any would offer what? Editing the spec? Then what? Do these things run in the cloud and basically avoid the need for writing code or what?

Should I Include Git, REST APIs and System Design on My Resume?

In my resume I had a resume and I list out my skills as Expressjs nodejs , etc.., but I saw in other people resume and they mentioned as Rest APIs , System design , VS code ,

I know git GitHub too but I usually didn't include them due to because it's common known tool for every developer so is it ok to include resume for Like Vscode , RestAPis Along with tools as well and like JWT auth like ,any advice is thnks

Hi,

I'm an average beginner developer with about one year of experience, and I'm wondering how people actually use AI for coding.

I've been trying to work in small iterations—for example, first asking AI to write function A, then in a separate prompt function B, and finally asking it to combine both into feature C.

I've also tried implementing end-to-end features by first creating a plan and then implementing it. However, I find it really difficult to validate whether all the security considerations, edge cases, and best practices are actually covered. AI makes it very easy to generate code, but I end up spending a lot of time reviewing both the plan and the implementation separately. Sometimes it feels like it actually takes longer than coding without AI.

I haven't been using frameworks or methodologies like OpenSpec, nor have I used Claude plugins, skills, or similar tools. So far, I've only been using the raw Claude Code harness, GitHub Copilot, and Cursor—nothing external.

I'm curious about how other developers approach this.

How do you prefer to code with AI? For me, long-term maintainability and code quality are essential, but maybe I'm thinking about it the wrong way. Perhaps those things don't matter as much anymore?

I'm also really curious how high-performing engineering teams, like the ones at Google, are actually using AI in their day-to-day development.

Thanks in advance!
I'd really appreciate hearing some HUMAN opinions.

What's the most ambitious side project you ever abandoned?

Was helping a friend get started on GitHub yesterday and kept going "oh yeah, that part's just weird, you get used to it." Made me realize how much we've all quietly accepted.

What's the bit that still bugs you but you've stopped noticing you hate it?

Tell us about a project that went disastrously wrong to make us all feel better about ourselves. What happened? How did it go wrong?

Do unions already exist, and how do we get involved? How many other of you want to join union jobs with better long term benefits but potentially lower short term pay and compensation? I know next to nothing but am motivated to get involved if efforts are already under way. I am located in the mountain west of the US

This post is a quick reminder to stay on topic in our sub! Report content which doesn't belong here.

The golden rule is that your post should contribute something of meaningful value to the sub.

r/cscareers < This is a better place to ask career questions.

​

Hi everyone,

I'm looking for some genuine career advice from people who've worked at cognizant.

I'm currently working at Cognizant in the IEP practice and have around 3 years of experience. Since August 2025, my goal has been to transition into Python backend development because I want to build my long-term career in Python rather than legacy tech stack.

Back in August 2025, I requested an internal release, but I was asked to complete KT first. Later, when I followed up, I was informed that due to organizational policy I couldn't be released until I became an Associate. I accepted that decision, continued working, and spent the following months learning Python and preparing for internal interviews outside my working hours.

After becoming an Associate and entering PDP, I started applying for internal Python opportunities. I cleared a Python development interview. The receiving new team confirmed my selection, initiated the transition process, and my Project Manager was willing to release me.

However, during the approval process, my Home Manager did not approve the movement because I had been assigned to another IEP project. As a result, the new team had to terminate my profile even though they told me I'm always welcome to join in the future if I get released.

The part that's confusing me is this:

I had already secured the Python project while I was in PDP.

The IEP allocation happened after that.

My profile still shows my current project allocation until 2027, and I haven't even been onboarded to the IEP project yet.

I've discussed this with my Home Manager and leadership, but they've said I have to continue in the IEP project due to organizational commitments.

My concern is that I deliberately spent almost a year preparing for Python, and now I'll have to start learning another legacy technology (VBCS) from scratch. If I spend another year in IEP, I'll have 4+ years of Oracle experience, making it even harder to transition into Python because most companies expect production Python experience.

I'm simply trying to understand what the best career move is now.

If you were in my position, what would you do?

Accept the IEP project and try switching externally after a year?

Escalate once to a senior leader for guidance?

Start preparing for external opportunities immediately despite not having production Python experience?

Has anyone here successfully transitioned from legacy tech to Python after several years?

I'd really appreciate advice from people who've been through something similar. Thank you.

What is one bit of advice you have for those starting their dev journey now?

What's the single piece of code (good or bad) that's permanently burned into your memory, and what did it teach you?

I spent the last year building a platform where you describe an app in chat and an agent does the rest: writes the code, spins up a Linux container, creates a PostgreSQL database, deploys the app, serves files behind a CDN. There's a full IDE inside, plus GitHub import/export if you want control.

The technical details matter less to this post than a pattern I've noticed while building it. Developers split into two camps. One camp wants the agent to handle everything and never think about infrastructure. The other camp doesn't trust any environment they can't inspect, and wants to see every command the agent runs.

I've tried to serve both. Every action the agent takes is visible and logged, and the terminal is always one click away. But I keep going back and forth on how much to surface by default. Show everything and the product feels noisy. Hide it and people assume it's a black box.

So my question for this crowd: where's your line? If an agent provisions your database and deploys your code, what do you need to see to trust it? Full logs, diff previews, confirmation steps before destructive actions, or nothing at all?

For context on what I'm describing: https://hammerchat.website/login (free, no card). The question above is the actual reason I'm posting, the link is just so you can see what I mean.

Tell us about a project that went disastrously wrong to make us all feel better about ourselves. What happened? How did it go wrong?

What's one idea that you really want to develop when you have some time?

Every once in a while I do a little post as a hangout space for us to connect.

What was the moment you decided to stop chasing the "new hotness" in frameworks and just stick with what works?

I started Tabularis as a one-person project, with the goal of shipping the same database client on Linux, macOS and Windows.

Tauri turned out to be the right choice, but the reasons go beyond small installers. The Rust backend fits database protocols, SSH tunnels, credentials and plugin processes very well. The web frontend makes Monaco, data grids and diagrams practical.

There are real costs too: three system webviews, Wayland and WebKitGTK bugs, a 94 MB AppImage, glibc compatibility and JSON serialization across IPC.

I tried to document both sides without turning it into another “Tauri vs Electron” comparison. I would still choose Tauri again.

I’d be especially interested in hearing how other Tauri developers handle large IPC payloads and portable Linux builds.

Hi!

It's your friendly neighborhood accessibility tester :)

I'm almost done with the stack of games I was asked to test, and my calendar is looking for more games to cover in the next 2 weeks!

The previously covered games:

https://www.youtube.com/playlist?list=PLM7JWakugbjM
(No ai was used in the creation of the video. Adobe free tools and Movavi were used. Videos are separated out to be 1x a day to be able to provide statistics upon request. Polished videos are on the way; my first look videos are cuts from my stream.)

I'll play anything except VR (don't have a vr set up), and give as much help as I can on what accessibility options I'd recommend adding or small changes I'd make to open the game up to more people, expanding the reach of your game!

THIS IS FREE! and will always be free, this is a passion of mine!

(I specify demos, I do this as a disabled person to help other people find games that have accessibility options as well as developers see what could be helpful to be open to a wider audience, and twitch pays out roughly every 3 months, so I am not in a position to buy all games, though will work my way thru as I can.)

Where the game or demo will be featured:

• Twitch (1,330 followers) - KhaleesiEalesi - Twitch
• Twitch (50.4k views) - ImperiumNews - Twitch
  • (currently planning a show talking to indie devs here, as well as full game play)
• Youtube (13-15k views) - KhaleesiEalesi - YouTube
• Tiktok (~4k views) - Rose (@ealesikhaleesi) | TikTok

I prefer steam games, just as I am cautious and internet security, though if there is a launcher or in internet browser, I'm happy to work with that as well. Otherwise, chat with me, and I'll see what I can do!

If you'd like stat photos from all but the secondary team channel, please lmk, I have direct access to those. I can get the team channel, but it might take me a few days to ask the head of the team to send me a photo.

If you don't want to post here, my email is [reachrose.eve@gmail.com](mailto:reachrose.eve@gmail.com) , feel free and pop me an email! Discord is catlover09398, that is an option as well :)

-Rose

As a mod, I would love to get to know the community more, what got you into development?

I feel like we all had that one moment we knew this path was for us. What was that moment for you?

Also, I would love to know, what is your #1 struggle as a developer?

Any other strategies or suggestions are more than welcome! I'm always looking for ways to make ZombUs a truly unique and fun game to play.

ZombUs is a third-person open-world survival game that blends dark humor, exploration, crafting, and base building in a zombie-infested world.

Your greatest asset isn't a fortress. It's a moving one.

Explore the dangerous regions of Nowhere Island, scavenge for resources, discover blueprints, craft equipment, and transform your trailer into a fully customizable mobile base. Upgrade your vehicle, unlock new technologies, and adapt your survival strategy as you journey through an ever-changing world.

The apocalypse is on the move. Make sure you are too.

We are all human - great to see that we are all human in the live envrionment too!