At my department we're all straight guys with a max 3 year differences. We're an oddly homogeneous group.
No, that was by design.
The luckiest greybeard in the whole world.
As mentioned elsewhere, this is appropriate for anyone doing database administration, because DB writes should always be a trans action.
I get that this is a joke, but....
... ackshually it should almost never be a transaction only when there's absolutely no other option, because transactions kill your performance.
Actually transactions can be a secomd-layer safety-net for single-responsibility writers to ensure rollback on eg restarts and consistency on loadbalancer redecisions without having much of an impact on performance, and data integrity is usually quite important.
As long as the database is acid restarts should not be a factor. Data integrity is not helped by transactions, you would need error correcting codes for that. Plus the effect on performance is quite notable on all dbs I've worked with.
Restarts in a server between dB updates that in a sane world would be txns I meant (e.g update A, crash so don't update B). Anyway, in postgres they're pretty cheap in the absence of actual conflict -- more expensive if you have actual cinflicts, obvs.
"Pretty cheap" is very subjective...
Well it depends how much data integrity is worth to you, and how your system works. Every write in postgres is already a transaction - when you can get away with simple crud stuff, often there's nothing to do, you have transactionality already. Transaction isolation levels are where db operation costs might change under concurrent conflicting writes but you can tune that by ensuring single-writer-per-partition or whatever in your server logic and it might add a ms or two. OTOH if you have heavy contestation it can be much more expensive. The performance implications are complicated but can certainly kept to a fraction of overall cost depending on your workload!
Again, not data integrity (Error correction) but consistency (aCid). Adding two milliseconds to a half a millisecond operation is by no means cheap...
But adding it to an 80ms operation is. If your operation is 0.5ms it's either a read on a small table, or maybe a single write -- transaction isolation wouldn't even be relevant there. You're right that I did mean consistency rather that integrity though, slip of the terminology, but not really worth quibbling over. The point I meant was that I like my data to make sense, a funny quirk of mine.
If your single operations take 80ms either it's a toy app or someone didn't do their job (unoptimized queries, wrong technology, wrong modeling, etc).
Lol what an absurd take. A transaction is a sequence of operations, not a single one, so even small tables can meet that threshold with enough query logic. I guess you're unfamiliar with medium to large datasets, but it's not uncommon to use the aggregate functions that SQL provides in real world situations, and on large tables that can easily reasonably exceed 1s. Toy my arse. Go play with yourself
Although this is no surprise tbh because apparently you don't understand why transactions are even necessary. Benchmarks shmenchmarks. Whether it works is more important.
I do not apologise for the downvote because this is smug shit only a junior would say
Exactly my point. Wrong technology. If your operation takes more than 1s and you just accept it, you are not very good at your job. No worries, more job security for me!
I would recommend reading a few books, but given that you couldn't even read my first post about when to use transactions, it's futile.
Unless you're using Firebird (3) in which not using transactions kills your performance
Greybeards are an increasingly rare commodity, it seems.
I've been in the industry for 13 years, a technologist using Linux for 19 years - I think I'd count as a greybeard if I hadn't lasered it off as part of my transition lmao
If you don’t mind me asking, how well does that work? I’m very interested in never having to shave again lmao
Effectiveness depends on your skin and hair color, paler skin and darker hair get better results. Results are permanent, a dead follicle stays dead for good, but you won't get 100% removal with a single pass because of how hair follicles cycle in and out of active duty. You'll need to do multiple treatments over the course of several weeks or months depending on how your hair grows.
As someone with dark hair and quite pale skin, I was basically a perfect case for it. At 7 sessions so far, the number of hairs that still grow on my face are countable - 43 of them by my count - I still do have to shave but it takes like 30 seconds because they're all focused on my upper lip and one particularly stubborn spot on my chin. The important part is that when I shave, I have no beard shadow at all now. I may not 100% pass yet without makeup but it makes makeup way easier to not have to also collor-correct for beard shadow.
Others have answered with more detail but yeah, it also does take testosterone suppression or you'll have to go back every so often to address any new/rejuvenated hairs. A cis guy friend of mine has to go just about every year.
Just for your information, it only works in combination with suppressing Testosterone. as long as testosterone is present in high levels it will come back
This is not true
It hurts and it takes a while (at least on my face), and it costs a fair bit depending on where you're at... but when it finally starts kicking in, I would STILL say it's worth it.
I had Lazer done on face, chest, arms, legs, and genitals. You need to do like 8-12 sessions but I haven't had to shave in years. Though there are like 5 clear hairs now that I pluck.
You can get rid of the clear hairs with electrolysis, they have to target each hair individually but if you've only got 5 it won't take very long
Yeah, I just keep forgetting to make an appointment.
Are the many sessions because you only do small areas per session, or because you need to do the whole area repeatedly?
Repeated, hair growth happens on different cycles and not all will be active at the same time. Need a short root for the Lazer energy to kill the root and sometimes one hit does not kill the base and needs to be hit again. https://milanlaser.com/inclusive-clientele/trans
https://www.reddit.com/r/MtF/comments/15zbz45/does_anyone_have_experience_with_milans_unlimited/
I feel like greybeards were always people who care little for the standards/expectations of society.
They probably have a lot in common with trans people, who unfortunately are forced to overcome very aggressive and hostile societal standards.
But Greybeards have a lot of luxury relative to trans people. They’ve always gotten to do what they want because of competency as a bargaining chip. Trans people as a group generally don’t have that.
Anyway, I’m rabbit holing. We treat trans people awful and they do nothing to deserve that.
Edit: I don’t mean to say trans people aren’t competent, just that greybeards privilege exists because they’ve passed through a specific niche filter that the general population has not
Indeed.
A Transition Plan suggestion (?):
Lifecycle of a rust programmer with C background.
Used to be the lifecycle of a ham radio nerd now those guys are all weirdo magats
So, instead of the length of their beard it's the length of their socks we should be considering?
Hi I'm trans Peter and came here to explain the joke
It's a pun, cis sounds like sys.
Cis(gender) is the antonym of transgender,
Sysadmin abreviates System Administrator.
Peter out.
The others are sis admins
Thanks, Dad.
That took way too long to click.
Maybe you should update to a faster system.
As a former sys admin, this clicked immediately for me.
Congrats on the transition
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
