I work at a company that is an extremely heavy user of Github copilot. All employees are mandated to use it daily, if you dont, you are put on a PIP. Theres a leaderboard for who is prompting the most without context, and every demo and presentation is offshore people trying to demonstrate LLM capability and failing. Horrific accuracy problems or latencies always surface and they pivot to a pre recorded video or say crap like “this is the worst it will ever be!”

Almost all my time is spent reviewing slop PRs from offshore that are 1000s of lines and filled with emojis, and management not so subtly tells me to stop being a blocker and approve the slop. But then when prod breaks im on the hook, not them.

Well as many of you know, a new change is being rolled out to Github copilot starting June1. Previously, we had unlimited access to some models, and a set allocation of tokens for “premium requests” on frontier models, all for a static price.

Now, every …

No tokens generated during the composition of this post

For those who have not seen the video, a former atlassian engineer recently posted a video going over his time at atlassian. The title is clickbait, this is basically a system design video about building a load balancer controller at scale:

https://www.youtube.com/watch?v=55pTFVoclvE

Now, few things to address because I’ve seen the other comments section of people who clearly didn’t watch the video.

Nothing he said in this video is likely to be proprietary. It’s high level system design. He probably doesn’t have to worried about getting sued, it all seems like fair use. But IANAL.

Here is what we can learn:

1. Talented engineers get laid off. I know most people should know this, a lot of time layoffs target experienced engineers as they have higher salaries. But this individual seems like he knows his craft and I don’t doubt he won’t have trouble finding work.

2. You need to be considering new …

I started a new job at a startup about four months ago where the whole process is now “ai-first” approach being pushed on us that we should just vibe-code all of the requirements and the apps. The startup is self-sustainable, it’s cash-flow positive and is looking to go get some funding in a few months for expansion but holy shit it’s bad.

The startup had two developer founders that left it; their code is a mess, and I mean a complete mess but I understand it from the point of view because they needed to get the customer and had to do shortcuts and just a typical startup fashion.

Then a CTO joined and he pushed for a complete rewrite which happened after about a year and now we are going for the third rewrite (hurray!) The principle engineer is coding, the CTO is coding…? seniors get to code but they don’t get to design anything and they must ask for implementation details from the CTO?

Anyways, the PR review is basically just LGTMing claude …

I spent 5 years at a large local telecom company after university. It was honestly a great place to start because I got strong mentorship, learned a lot, and built a solid technical foundation.
Eventually I felt like people still saw me as “the junior,” so I decided it was time to move on. I joined a sub company of a very well known enterprise software organization, something similar to an SAP style corporate environment. The interviews went great, but after joining, the reality has been pretty rough.
There’s almost no documentation, and the only “docs” we really have are Jira tasks. It’s hard to understand the full system or even trace how things are supposed to work. Tests are flaky, integration tests are run locally, there’s commented out code everywhere without explanation, and a lot of the system feels like workarounds built on top of older workarounds. Whenever these things come up, the answer is usually “we’ll fix it later,” but that never actually happens.
What frustrates me …

With fewer openings, more people entering tech, and continuous layoffs in many big companies, do you think this will become the new normal for the IT industry?

Feels like companies now have more bargaining power:

- Delayed promotions

- Smaller salary hikes

- Lower salaries for new job openings

- More competition for every role

Are others also seeing this trend in their companies and job searches?

No idea how it bypassed perimeter security. Not in my DHCP leases either.

Rack is semi-open so I assume it came in through an air gap.

Is this a known issue? First time dealing with a physical layer intrusion of this kind.

(WRITTEN BY A HUMAN THAT LIKES BULLET POINTS)

Most people here have probably heard about Plex hiking the lifetime pass to 750USD, effective July 1.

If you’re still on the subscription and considering buying the lifetime pass before the deadline, here are some reasons not to:

• Plex is the worst type of ‘self-hosting’ - Closed-source, auth is routed through their servers, you’re completely dependent on them.
• Plex explicitly sells your data. This excerpt is from their privacy policy:
  • “If you have set your account to public settings, then your watch history, reviews, or other data from the Services that you share publicly may be shared with both the public and third parties for marketing purposes. Learn more about your account settings here.”
  • If you haven’t yet, opt-out of tracking immediately.
• Self-hosters are not the main target market anymore.
  • Every single Lifetime subscription are a liability for Plex, since servers cost money. …