5,591 karma · joined February 24, 2020
We all walked into the walled gardens and went "ooh, looks mighty nice in here!"
- Hard shift: quit their job, went to grad school, and started over.
- Soft shift: got an adjacent job w/ a company w/ many roles (consulting, big tech, etc.), slowly got good at the adjacent role, and then title change.
I don't know what's best for you. Option 2 is safer. Could look like:
- Get a job doing UX in/around tech services/consulting/cybersecurity (eg IBM, Palo Alto Networks).
- Get on a team with cybersecurity engineers (eg, GTM for a "new cyber offering")
- Slowly build up your PM or technical skills (eg, start by learning SQL & doing reporting)
- When you're actually useful in the new area, ask about a role change
Keep in mind this is a lot of work.
- You're gonna need to go from No knowledge -> Junior -> Mid-Level -> Senior.
- Your opportunity cost is 1-3 promos in your current track, which would probably radically change your day-to-day anyway.
Good luck!
Tech vs consulting/finance for MBAs, tech vs. HFT for SWEs, tech vs. advertising for creatives, etc etc
We're all just fancy monkeys with lightning rocks, it's fine dude
- DON'T is very clear and specific. Don't say "Stat-Sig", don't conclude causal effect, don't conclude anything based on p>0.05.
- DO is very vague and unclear. Do be thoughtful, do accept uncertainty, do consider all relevant information.
Obviously, thoughtful consideration of all available information is ideal. But until I get another heuristic for "should I dig into this more?" - I'm just gonna live with my 5-10% FPR, thank you very much.
If the FPR is comparable to asking a human "are these the same image?", then it would seem to be equivalent to a visual search. I wonder if (or why) human verification is actually necessary here.
I generally assume someone has 0 users unless they express otherwise.
https://www.wired.com/story/iran-apt42-trump-biden-harris-ph...
"Google says Iran-backed hacking group APT42 has targeted the Trump and Biden campaigns, as well as Israeli military, government, and diplomatic organizations"
I'm curious how folks who happily live in the city with kids approach it
Young adults love it bc they have the time to go to bars/restaurants/clubs
Middle aged folks hate it because they're so busy - they can't take advantage, and other people get in their way
(some) Older folks like it again bc they have the time to go to restaurants/theater
What's the process for determining the methodology? Would another process have been better? Does the plaintiff's proposed approach for methodological determination also conform to this law?
In this case, "how to go about determining methodology" is left ambiguous, and is now the province of the courts, not the EPA.
I.e., anything Congress does not explicitly state in a law is now determined by federal judges. At the extreme, this is aggrandizing a very wide scope of power to low-level federal judges to essentially ignore congressional intent.
This is kind of true, but also belies the depth of the Chevron change. In this example, plaintiffs can now, for example, challenge how the "X%" calculation is done. What's an appropriate methodology?
In the past, courts deferred to the agency: as long as it's scientifically valid + consistent, it's up to the regulator, not a judge. Now, it's up to a judge.
So if I sue and say "you should use a 0.01 alpha for calculations, not 0.05" for your X% calculation, then a judge makes the methodological decision, not the statistician.
IMO, it's not really reasonable for congress to design statistical methodologies as part of the text of a bill.
Good SQL is becoming more specialized for dev. No longer are the DBAs tutoring the devs to avoid inefficiencies. Now, the DEs handle really complex pipelining, and get really good.
But SQL isn't just used to "build" - it's also used to "access." And that's less specialized. The PM, BA, etc can all use ChatGPT/Stack Overflow and get things done quickly. And it's a virtuous cycle: the more people access data, the more the DEs are asked to clean things up, the easier it gets to query, and the more people try/succeed.
So SQL-for-development is increasingly niche, while SQL-for-access is increasingly common.
I've used a number of tricks to circumvent paywalls over the years, and they all get shut down after a year or two.
Looks like they're just trying to catch up. Bad timing.
But still - a lot easier than semiconductors