12,701 karma · joined August 13, 2009
It’s probably too early for you to decide that you are done forever, but you could be if you want to.
You could take a break of 1-2 years and see how that goes. Call it a sabbatical on your resume if you want to go back to work after.
But it's super common for a team to be asked to do something fundamentally outside their scope, and the asking client/boss not realizing that they are doin g it.
"Figure it out" as a useful strategy sort of assumes that both sides of the equation are clued in about this and roughly on the same page.
"I underwrote a great team, you should be able to figure this out (stop whining about it being hard)" is a fundamentally different statement than "Why can't you just do X, how hard can it be?"
It's also worth remembering that the plural of "resource" is not "team".
If the “why can’t we do X” is “because we’re a team of 4 and already overburdened” there may not be any practical solutions.
There isn't really a shortage of other options with that feature (though it's shrinking); granted they mostly don't have people waiting on you.
Personally I'm a fan of "I'm on vacation, my phone is at home" though I understand that doesn't work for everyone. If there is an actual emergency, there are people who know how/where to reach me.
Another factor is possibly pent up demand for mirrorless with all the bells and whistles.
To the contrary - that's a good reason to subsidize the construction of of infrastructure, but having some sort of incentive to use less damaging forms where possible makes all kind of sense. Part of the reason for the stupid-sizing of consumer vehicles in the US over the last decades is because the incentives are all messed up.
It just looks like "conf_paper1.tex" "conf_paper3.tex" "conf_paper_friday.tex" "conf_paper_20240907.tex" "conf_paper_last_version.tex" "conf_paper_final.tex"
...
"conf_paper_final2.tex"
Oh, and the figures reference files on local dir structure.
And the actual, eventually published version, only exists in email back and forth with publisher for style files etc.
I spent time getting some mathematicians working together via version control rather than email, it was a bit of a mixed bag even using something simpler (e.g. svn). Eventual we moved back to email, except the rule was email me your update as a reply to the version you edited, and I scripted something to put it all into a repo on my end to manage merges etc. Worked ok. Better than the version where we locked access for edit but people forgot to unlock and went off to a conference...
If I was doing the same now, I'd probably set up on github, give each person a branch off main, and give them scripts for "send my changes" and "update other changes" - then manage all the merges behind the scenes for anyone who didn't want to bother.
I think expecting everyone in a working group to acquire the skills to deal with merge issues properly etc. is too far if they don't do any significant software work already. In the latter case., teach them.
But any tech may be overkill. In a e.g. roommate situation, a paper record per month (plus receipts, if lower trust) works fine.
Then again I'd never trust rules to do everything right anyway, so I'm reviewing at least once to reconcile.
Problem is, the world consuming these things mostly seems to want those parts, and can't ignore those other parts. Which seems to explain relatively low uptake.
That doesn't really match my observations ,or NIH data https://www.niaaa.nih.gov/alcohols-effects-health/alcohol-to...
There the majority (18 and over, and slightly under 50% of 12 and over) report consumption in the last month.
Of those, a bit under 7% report "heavy usage". You can look up the definitions, but doesn't include e.g. "usually has a beer or two with dinner".
The category you describe definitely exists, but I don't think it's anywhere close to a majority, and there are also at least a couple reasonable categories between that problematic or abusive consumption.
In general, no.
It's worth remembering, though, many/most jobs don't come from this process. It's worth trawling jobs postings of course to see what's going on, but if that's all you are doing you'll probably have a hard time.
In tech circles, I see mostly two camps of process. One is big and/or established companies that have a bureaucratic evaluation process, the other being more "bespoke" hiring at e.g. young startups.
Navigating both processes is vastly easier if you have some sort of personal connection. It doesn't have to be a deep one, but it gets you out of the slush pile.
Any large company application with an attached internal recommendation will at least be read by someone. Any small company is more to reduce the crapshoot aspect of hiring by convincing themselves they know something more about this candidate because so-an-so's cousin's brother used to work with them.
My most effective advice to younger job seekers has been to get themselves out there in face to face settings (e.g. hardware/software meetups, conferences, etc.) and to directly contact (ideally through a colleague or common connection) companies they already know they'd like to work with... you have no idea what they are thinking internally but don't have posted on a job board.
Also, senior people in your life can often help you with contacts and recommendations, and often are more than happy to. Don't hesitate to ask if you have a good relationship.
For what it's worth, nearly all the jobs I've had in my career haven't been posted. The one that was, reached out to me with an internal recommendation. This only happens with some sort of networking, but that naturally comes with time. This post was by someone 5ish years in, if I recall correctly, and that's long enough to be effective relative to entry candidates.