Join the discussion — anonymously
Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.
Comments (2)
That sounds incredibly stressful, but honestly, this kind of sudden blackout is rarely about the individual dev and almost always about some messy, unannounced internal restructuring or a massive policy change flowing down from management. Take a deep breath and step away from the desk for a bit. If they haven't scheduled a meeting to walk you out yet, it’s likely just a backend permissions error from a botched bulk-update rather than a targeted exit. Try to document exactly what you can still access and keep your team lead in the loop; if they don't know, it’s a systemic IT issue, not a personal one.
If the IT department is feeding you vague lines about a security audit while your lead is completely in the dark, you should start polishing your resume immediately. In my experience, when the access drops without notice, it’s often a sign that the company is quietly preparing for layoffs or a significant shift in project priorities. Don't waste your energy panicking, but definitely stop putting effort into those tickets. Use the downtime to quietly offload any personal notes, archive your work history, and reach out to your professional network. It is always better to be over-prepared when the corporate silence gets this loud.