Find what's wrong in production — in one offline command. Code + deps + runtime + logs → one report. Free & open source. 👇
Joined June 2026
- Tweets422
- Following542
- Followers87
- Likes107
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
34
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
4
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
4
If your AI coding assistant can generate a feature in 10 minutes, but your team needs 2 days to review it safely, did you really save time?
Where should the productivity gain be measured: code written or code trusted?
#CodeReview #AI
10
What is more difficult to get?
Your very first customer or your second customer after your very first customer pretty quick after lunch of your product or service.
Personally for me it gonna be second customer forever ✌
Share your experience 🤔
#developer #Founders #SaaS
6
1
49
How did you guys got your second customers? Share your experience and efforts @franagl @byrehan @StackOutreach
1
13
AI isn't creating better developers. It's creating developers who ship code they don't fully understand.
Passing tests doesn't automatically make that code secure or maintainable.
Are we improving productivity or accumulating technical debt?
#AI #CodeQuality
15
Would you let an AI code-review tool send your private repository to a third-party server?
For some teams that's fine. For others, client contracts make local-first analysis essential.
Where does your team draw the line?
#DevSecOps #CodeReview
5
One lesson from maintaining older backends: a 'small' change is only small when you understand its side effects.
Before touching a legacy module, I trace callers and failure paths. What is your first move when the documentation is missing?
#BackendDev #TechDebt
4
A green CI pipeline isn't the same as production readiness.
I've seen changes pass tests but fail under real traffic because nobody checked query load, timeouts or rollback paths.
What's the one pre-release check your team refuses to skip?
#DevOps #CodeQuality
4
The hardest bugs I've chased weren't syntax errors. They were assumptions nobody documented.
Before refactoring a service, I ask: what behavior are other parts of the system quietly relying on?
How does your team uncover those hidden contracts?
#CodeQuality #TechDebt
5
A codebase can pass tests and still be painful to maintain.
Tiny changes can turn into hours of debugging when nobody knows which modules depend on what.
When inheriting a project, do you map dependencies first or inspect the riskiest code paths?
#CodeReview #TechDebt
7
AI-generated code can look clean in a PR and still hide a costly database query or a missing authorization check.
I have learned to review the behavior, not just the diff. What do you always verify manually before merging AI-assisted changes?
#CodeReview #AppSec
2
14
A security scan can catch vulnerabilities, but there's another question worth asking: where does your source code go during the scan?
For private repositories, do you prefer local checks or cloud scanners? What drives that decision?
#AppSec #DevSecOps
10
A feature passes all tests, works in staging and gets approved for release.
But nobody checked rate limiting, error handling or what happens under unexpected input.
Would you call that production-ready?
Curious what your team's minimum release checklist looks like.
#BackendDev
10
🪔 Happy Dhanteras from GetObserver!
May your wealth grow, your code stay clean, and your vulnerabilities stay low. 🔐
Here's to secure, maintainable PHP & Laravel projects—audited offline, without uploading your code.
github.com/sanks205/getobser…
#Dhanteras #PHP #Laravel
1
23
A question for teams handling private repositories:
Would you rather run code security checks entirely inside your own CI environment, or use a hosted scanner with richer dashboards?
Where do you draw the line between convenience and source-code privacy?
#AppSec #DevSecOps
7
One thing that makes technical debt worse isn't always bad code. It's code nobody feels responsible for anymore.
I've seen teams hesitate to touch a working module because the original developer left years ago.
How do you handle ownership of legacy code?
#TechDebt #BackendDev
10
A Laravel API can look perfectly clean in code review and still struggle under real traffic.
I've seen database queries become the bottleneck long before the PHP code itself.
Do you review query performance during PRs, or only when production slows down?
#Laravel #BackendDev
1
2
40
Security scanners can flag hundreds of issues, but not every warning carries the same risk.
For a small backend team, what matters more: catching every possible issue or keeping false positives low enough that developers actually act on findings?
#AppSec #CodeQuality
1
13