Pinned Tweet
Your PHP code works. But when did you last audit what's underneath?
That's the question behind GetObserver.
Built to help developers review PHP/Laravel code locally, without uploading source code.
Here's a 10-second look at it. 🎥
#PHP #Laravel #CodeSecurity #DevTools
🤖 Made with AI
2
1
77
An outdated architecture diagram can be worse than having none.
Developers trust it, make changes, and discover the actual dependencies only when something breaks.
Tech leads: how do you keep documentation aligned with the code?
#TechDebt #SoftwareEngineering
4
Hey @X, are developers, SaaS founders and tech leads already in weekend mode? 😅
Or is everyone still debugging that one issue that refuses to let Friday end?
It's unusually quiet here. Who's still building?
#BuildInPublic #DevLife
5
A payment webhook times out. The provider retries. Your backend processes it twice.
The code may be clean and the tests green, but is the operation idempotent?
How does your team test duplicate events before release?
#BackendDevelopment #CodeQuality
1
11
A codebase can pass security scans while its test fixtures contain real customer data.
Teams focus on production secrets but barely review sample databases, debug dumps or old backups.
Who checks those before a repo is shared?
#AppSec #DataPrivacy
6
A SaaS team can patch a vulnerability today and reintroduce it next month through a copied helper or old branch.
Do you track whether a security finding stays fixed across releases, or just close the ticket after one clean scan?
#AppSec #CodeQuality
1
85
An API can have solid authentication and still expose another customer's data.
The missing check is often ownership, not login.
When reviewing backend code, do you explicitly test whether User A can access User B's records?
#AppSec #BackendDevelopment
1
91
A security warning gets marked 'accepted risk' to meet a release deadline.
Six months later, the exception is still there. Nobody remembers who approved it or why.
Should every accepted security risk have an owner and expiry date?
#AppSec #CodeQuality
4
Before approving an AI-generated patch, I want to know one thing: can we safely roll it back?
Tests may pass, but database changes, background jobs and external API calls can leave damage behind.
What does your rollback checklist cover?
#CodeReview #DevOps
3
A developer leaves. Six months later, nobody wants to touch the module they built.
I've seen this become a bigger problem than the code itself. No ownership, no context,no confidence.
What should teams document before a critical developer leaves?
#TechDebt #SoftwareEngineering
1
10
Hey @X algorithm 👋
Looking to connect with indie hackers and SaaS founders who build and maintain their own products.
Especially those dealing with technical debt, code security or production issues.
What are you building?
#BuildInPublic #IndieHackers
9
9
360
A dependency update can pass every unit test and still break production.
Changed defaults, deprecated APIs and unexpected behavior don't always show up in CI.
How does your team review dependency upgrades beyond checking for known vulnerabilities?
#AppSec #CodeQuality
1
24
When a team inherits a SaaS codebase, what's the first thing you'd audit before shipping a new feature?
Authentication, database queries, dependencies, or error handling?
I'd start with the paths that could hurt customers most.
#CodeReview #SaaS
11
Who owns a bug introduced by AI-generated code?
The developer who accepted it, the reviewer who approved it, or the team that pushed for faster delivery?
We talk a lot about AI productivity. Not enough about accountability.
#CodeReview #SoftwareEngineering
15
Would you trust a codebase just because its security scanner reports zero critical issues?
A clean report doesn't mean the code is secure. It only means the scanner didn't flag anything critical.
How much confidence should automated audits really give us?
#AppSec #DevSecOps
12
Legacy code isn't automatically bad code.
I've seen teams rush into rewrites without understanding why the old system works.
Would you rather maintain a messy but stable codebase or rewrite it with modern tools and introduce new risks?
#TechDebt #SoftwareEngineering
35
Would you approve a code audit tool that requires uploading your private repository?
Some teams value cloud convenience. Others can't risk exposing client code.
Should local-first auditing be the default, or is that an overreaction?
#DevSecOps #CodeReview
19
A security scanner that reports 200 warnings but can't explain which ones matter isn't helping the team. It's creating another backlog.
Would you rather have 200 findings or 10 with clear evidence and fixes?
#AppSec #CodeQuality
13
Would you approve a code audit tool that requires uploading your private repository?
Some teams value cloud convenience. Others can't risk exposing client code.
Should local-first auditing be the default, or is that an overreaction?
#DevSecOps #CodeReview
8
