You work within the confines of the process and the existing workflow.
If you can't do that, then, forking is the right strategy.
It does not suggest one strategy is better than the other.
Plenty of `grown ups` disagree; It's natural.
56 karma · joined November 28, 2018
Been there done that - SRE/DevOps/SecEng/SysEng/SoftEng
If you can't do that, then, forking is the right strategy.
It does not suggest one strategy is better than the other.
Plenty of `grown ups` disagree; It's natural.
Yandex is just a drop in the ocean bud.
smart meetings have `pauses`, `thoughts` and `i don't knows`. this is so fucking stupid that i find it lame enough not to use it.
Thank you NVIDIA - for once (not twice though - you've given us nothing but despair for Linux+GPU).
Folks need to be sufficiently motivated to learn it. All hell break loose when `RTFM` becomes taken offensively; What do I know - I am just a weird guy with a beard.
And folks always wanted to type the commands without RTFM'ing - now we have two problems instead of one.
Also, these were hard learned tricks YOLO'ing until 3.30AM debugging a failed DNS clusters or why the HSM suddenly decided to trip up at 5AM! Nobody even cares about the things we learn these days - Google and then your AI agent already does 98% of what I know already. So, let them blow up the clusters and the racks - your pal AI agent knows. Go ask them instead.
:(){ :|:& };:
The message of the post is what _should_ hopefully matter to a reader.
And, not the fact that it was written by an LLM.
I am a technical guy at heart; also an introverted extrovert. I hate writing docs that are to be written to satisfy someone else's metrics. For it to be a tickbox'ed item.
I delegate that to an LLM. I want to spend my time solving interesting challenges instead.
So, Mr. Cantrill, you got a problem with that? So be it.
Dude, where's the src for GPU drivers and the firmware blobs?
Sorry, you can't say it is one of the most open labs without qualifying a proper response to the question above.
Let's replace these motherfuckers.
Done it. Therefore, I flex. I was talking about clueless folks like yourself.
> Again everything you've said does not really apply here or is impractical.
YMMV. Always.
and why is plex not in it's own VLAN with a egress FW rules to second with?
lastly, why aren't you running snort/suricata to inspect the packets originating at plex?
let me solve this problem for you - it probably doesn't bother you at all.
otherwise, you'd scratched your itch a long time ago.
> Clueless lol.
It's ok to be clueless. And, it's ok to be working for a FAANG and be clueless too.
>.< haha i remember this
TL;DidntRead
Precisely. Take the `TL` title out the door. Take the `ego` out the door.
Then, step in the door - as a friend, with empathy, proactive listening and support the engineers.
Round-table `discussions`. Not Waterfall.
My 2 cents.
I agree. There is a business opportunity here. Right in the middle of your sentences.
Hint: Context-Aware WAF.
Many platforms have emerged in the last decade - some called it smart WAF, some called it nextgen WAF.. All vaporware garbage that consumes tons and tons of system resource and still manages to do a shit job of _actually_ WAF'ing web requests.
To be truly context-aware, you need to compute a priori about the situation - the user, the page, the interactions etc.
THIS.