Or just do not use a phone at all. I travel internationally without one a few times a year. Europe, mexico, canada, japan, no problems. Dirty looks, but no problems.
Not just to blame. They also sell credibility to a lot of managers and bosses.
I've experienced it often enough that upper management doesn't listen to their own employees.
Ultimately, a consultant comes in, talks to employees, suggests the exact same thing to the same people, and they love it.
Having that branding on the ppt slides sells ideas. If you're a project manager or department lead and need to push through an idea but your boss won't let you? Try hiring a consultant who will sell it to your boss.
Surrogacy is illegal in Spain, Germany, France, Italy, Switzerland, Austria, Norway, Finland, and Turkey. Also banned in China, some states in the US and Québec.
Thats a pretty hefty chunk of the worlds population.
A lot of other countries also have a limbo status where there is either no clear law making it illegal but put so many hurdles up that its impractical.
Some countries, like Italy, also make it illegal for Italian citizens to go abroad to a country where it is legal and then do it there.
Something that most sub 1000€ laptops could do over a decade ago, requires a macbook costing well above 2000€ in 2025.
I'm running multiple types of machines in my home for work and personal use but macs have been by far the worst offender for multiscreen support for a long time.
Vintage 2015? Yes. Any Dell Latitude (mid tier business line) would have supported 3 monitors and would have been in the ~$1000 range, especially picked up off of Dell Outlet. I have Dell Latitude Windows machines from 2011 that supported 3 monitors.
That wasn’t a capability of the laptop. The docking station had its own dedicated graphics hardware that drove the extra monitors. Of course the lowest end Macs can do that. When we talk about how many monitors a certain laptop can drive, we mean plugging them in directly to the laptop in some combination of HDMI ports and USB C/Thunderbolt ports.
This is embarrassing, just stop. You can go look up the specs of any chip and how many discrete displays the iGPU supported instead of bickering about what is or isn't a laptop feature. Citing sources isn't illegal or passe.
Exactly how did you attached three monitors to your laptop without a docking station? I bet you the docking station had displaylink based hardware/software like most of the Dell docking stations had
You didn’t give any citations on your specific model of laptop or docking station. You just admitted that you used an old school docking station - those came with GPUs.
And your citation said it wasn’t available in all configurations.
Riddled with bugs is frankly expected for Bethesda.
Starfield's main problem was the shallow content which is very unlike Bethesda. Skyrim, for all its faults and issues, had so much to discover. As did the previous entries in the series. As did Fallout.
I don’t know. I stopped playing Elder Scrolls games at Oblivion which was significantly more shallow than Morrowind, itself less ambitious than Daggerfall. On the Fallout side, NV was great but not made by Bethesda and 4 is pretty much just a bad FPS with boring paddings in between the shooting.
I think the constant content downgrade has been going on for a long time.
My view is likely very tinted. Skyrim was my first Bethesda game and while I did the play the Oblivian remaster, I never touched Daggerfall.
From my view, assuming the remaster isn't too massively different content wise, the change was more in certain mechanics from Oblivion to Skyrim. Lore and story wise both games have incredible depth.
While I did enjoy Starfield, if found it to be flat. They stretched the resources too thin. Much of the content was too repetitive. It felt like a kids game. Neon, the supposed crime den riddled with drugs and gangs, may as well have been a kids amusement park.
Ultimately, the fact that Starfield came out over a decade later but offered so much less was a let down. Never mind that the game didn't really improve on the underlying mechanics. Modders solved a lot of loading screens in Skyrim decades ago, but Starfield is full of them. It felt dated at release already.
> Lore and story wise [Oblivion and Skyrim] have incredible depth.
As you said, you never played Daggerfall or Morrowind. Just about all of the lore in Oblivion and Skyrim comes from Daggerfall, Redguard, and Morrowind.
As for the stories... sorry, but you're on your own there. Oblivion's was okay, but Skyrim's story was a trainwreck from beginning to end. Of all the parts of Bethesda games, it is the character + story writing that has suffered the most over the years.
> They use licensing as a weapon to restrict labor supply
In parts they do, but that doesn't mean that licensing doesn't have a point. They should not be able to limit the licenses but testing and training should absolutely happen. Especially for critical things like electricity.
> If I go to India I do not automatically die inside a house with a $9500 solar installation.
You don't but your chances are higher than a country with enforced minimum standards.
>1. “I’ll Just Fix It”. As a senior: it’s reckless.
For the sake of my own sanity and enjoyment of my work, I have realised that I sometimes have to do this. I'm not talking about massive 2 week tasks but rather something done in 30mins - 1h. I call them pallet cleansers and when there is a particularly hard task that has me stumped I'll do one of them to give my brain some time to passively process the more difficult one.
I have also told my manager point blank that they can get on board or start looking for a new engineer because I would leave otherwise. Thankfully, they're a good manager and are completely fine with it as long as my main work gets done on time and I somehow communicate it (standup, slack, jira, etc).
This one's just wrong, unless the author is using a novel definition of senior.
Senior engineers are exactly who I trust to "just fix it" when they notice a problem, even one outside their immediate domain. Sure the bar is higher, but that's still their job. If this was about staff or architects, then it would make sense.
If anyone is going to spot that the easy fix turns out to actually have more implications its the senior engineer. To some extent it comes with a battle hardened wince to "this is a 30 minute fix" knowing full well it sometimes isn't and to look for the foot guns.
This - and how to deploy that “easy fix” in a way that watches for unexpected consequences, and with a plan in hand to mitigate them or revert the change without undue disruption if necessary.
As I go through this thread, one word keeps coming to mind: discernment. The more senior you become as a SWE, the more you’re expected to know what to address, when, and how to address it. The actual addressing of the problem is table stakes, and as you move from senior to staff you’ll find yourself directing more and implementing less.
I think the author didn't account for different types of engineering orgs at different points in their lifecycle. "just fix it" at an enterprise massive company as a junior is fine but a senior would know "if you fix it, you own it" and it could cause downstream issues with what your team does or owns at the company. whereas at a startup, if you're relying on junior devs to "just fix it"... good luck with that
Even at an enterprise its absolutely possible. I work for one after all. My team owns the product anyway though and my "just fix it" tasks are 99% of the time annoyances that I encounter in my day-to-day work.
For example, we run a Jenkins instance for our platform that has bi-weekly production releases. We write announcements in slack when there was a release with a list of PRs and links to the tickets in Jira. That used to be manual work. At one point I was annoyed by it and took 30 minutes to write a 15 line script to automatically take the merged PRs, create a Jira link and announce it in our slack channel.
It’s funny that you get (or got) pushback for basically doing extra work. If you were to just take a break and do nothing at all, people would just assume you were hard at work on the main issue.
At a previous job my manager complained. They weren't mad about the extra work itself but rather that I didn't go through the entire change process. That meant writing a user story, creating a ticket, bringing it to refinement, agreeing with colleagues that it's something we should do, planning for it in a sprint, etc, etc. For large tickets/tasks/projects that makes sense.
However, I outright refuse to go through this process for a minor annoyance that needs 2-3 lines of code and 30 minutes until its in production.
Since then I steer clear of companies and teams that have an incredibly strict sprint schedule were no unplanned work, even if its tiny, is allowed. I hate that way of working and refuse to do it.
reply