<sarcastic, joke, maybe..>
JOB OPENING
NOBODY EXPECTS THE JOB OPENING.
Role: Take some of my building and maintaining work, because if you ain't first, you're last, and I'm tired of being both.
Looking for: Me. Also acceptable: a shrubbery, a man with a duck on his head, or anyone willing to look me dead in the eye and say "shake and bake" without breaking character. Also, Me, but younger, hungrier, and contractually obligated to laugh at my jokes. Cloning is on the table if anyone has a friend in biotech.
Pay: With all due respect, almost none now, maybe when this blows up?. I pay in exposure, experience, and the warm feeling you get when the build finally goes green. If you require currency, we have a coconut you can bang together.
Benefits:
Learn things. Real things. The kind of things that make you go "well, that's not supposed to do that, is it."
Hands on tech. You will touch the server. The server will touch you back. This is the circle of life. the GPUs prefer cool temps so dont touch them.
Shape the future. The future is mostly on fire right now, so honestly any shape would be an improvement.
Unlimited Monsters and bourbon, because I wanna go fast and I cannot do that sober and hydrated.
Free access to an existential crisis, brought on weekly by the standup we don't have.
Location: HackHaus. In person. No remote. Remote is a myth, like the Knights Who Say Ni, or a 40 hour week.
Open desk: The Fantail Patio. The cigar patio. The bourbon lounge. The place where, at approximately 11pm last Tuesday, someone said "help me Jesus, help me Tom Cruise" out loud during a code review and we all just nodded. (we meaning me, myself and I)
Humor: Dry. Sarcastic. Pythonesque. If I tell you production is down and you respond with "tis but a scratch," you are halfway through the interview. If you can deliver "this parrot is no more, it has ceased to be, it is an ex parrot" while pointing at a crashed Kubernetes pod, you are hired and also, frankly, a little scary.
Disqualifiers:
You think you're first.
You don't know what to do with your hands.
You enjoy meetings.
You were expecting a Spanish Inquisition joke earlier and are now disappointed it was the opening line. Our chief weapon is surprise. Surprise and disappointment. Our two chief weapons are surprise, disappointment, and a ruthless commitment to the bit.
How to apply: Pigeon, since the parrot is now an ex parrot?
@leothrix The issue I run into is the repeatable shipping of $something to the runtime environment. Containers are currently the least painful way, but I’m always interested in better methods.
@leothrix Same exact thing today only my response was “the outside is their home, I’m cool with them out there”
Then he stuttered and complimented my (vintage 😫) linkin park shirt
🚀 OhMyPCAP 4.0.0 is HERE!
The ultimate FOSS PCAP analyzer just got a massive upgrade for deeper file intelligence.
New in v4.0:
• Upgraded to YARA Forge Full ruleset — more comprehensive malware & threat detection
• Exiftool + rich file metadata analysis — get more file information even if there are no YARA matches
All the power you love is still here:
Suricata alerts, file alerts, Sankey diagrams, full-text search, ASCII transcripts, hexdumps, stream carving + single Docker/Podman container (perfect for air-gapped or quick spins).
Ideal for malware analysis, incident response, threat hunting, forensics & teaching.
Who’s pulling this version right now? Drop a ❤️+ reply with your main use case (malware samples? CTFs? real-world incidents? teaching?)
#PCAP #DFIR #Cybersecurity #Infosec #BlueTeam #ThreatHunting #Suricata #YARA #MalwareAnalysis
@Suricata_IDS@lennyzeltser@chrissanders88@sansforensics@TomLawrenceTech
I gotta say this is probably one of the worst possible takes I’ve seen in the subject. Imagine saying “poor people aren’t smart enough to cook” 😂
Nobody is forced to door dash, Taylor. It’s a convenience.
I grew up dirt poor and we went out to eat maybe once a month. 🤷♂️
This is bc they do not have the time or capacity to create home cooked meals. It’s an issue countless ppl have tried to raise w leftists but big leftists online continue to shame/abuse poor ppl for being forced to rely on these services for meals, which act as a tax on the poor
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
@mitchellh This was the SOP at @tsheets for the longest time when I worked there. Definitely a solidly good plan. @zehm had a pretty good handle on that area :)
Blog: why I built a new Terraform provider for UniFi Network. Goal:
Built on the UniFi OpenAPI snapshot, published on the Registry.
https://t.co/IYgR0ZyAdl
#unifi#terraform#blog#whydoesntanyonetaganymore
@leothrix I’ve done this a couple times and… look, if a token predictor can guide us to something edible from a random assortment of ingredients then.. ok.