In today's PEBKAC, i forgot to set "enable [fucking] Go modules integration" in IntelliJ when setting this goddamn laptop up, and SON OF A BITCH turning that on fixed every goddamn dependency issue I've had for the last fucking week on this imported project.
Ok, I think it's cancer causing liquid poison o'clock.
=> More informations about this toot | View the thread
So, Gorillapod and iPhone with magnifier app on, and using the built in flashlight, with a pair of multi-tool pliers, the most basic of repairs was done.
That magnifier is really good, by the way.
=> More informations about this toot | View the thread
Earlier this month, my scheduled backup to S3 started failing. No real reason, just "oh, yeah, nah" and the utter lack of logs.
So, I finally dig through system logs on the NAS, and for whatever reason, a recent change to HyperBackup caused a region conflict error (I push to a different region than the default, because I have over a decade experience in running production workloads on AWS). Nothing changed with the configuration, but the failure was consistent otherwise with a region conflict. So, now I'm testing re-linking the backup target to a fresh task.
As it's a configuration backup, and not a "oh shit, my data!" backup, I'm fine with this test. But, goddamn was this frustrating to diagnose, and worse trying to pick apart.
With that, I think it's time to migrate to something else.
=> More informations about this toot | View the thread
But, motherfucker, come in to my goddamn drop then get grumpy I'm not playing your way, or doing what you expect, while I'm trying out a new thing or three.
I intentionally didn't put up an SOS, bucko.
Anyway, this is my stupid rant.
Also, I just discovered you can blow open the doors of various shipping containers for fun and profit.
=> More informations about this toot | View the thread
Which means you're in a weird position if you favor the long reach over close in. Do you sacrifice your support weapon options to the railgun, which is good anti-armor, but sucks at range and cycling, or the Anti-Material rifle, which is good at range and rather powerful, cycles fast, but weak against strong armor?
Anyway, running solo against lower ranked challenges is doable. At least against Automatons, and it's a good way to test out a new Strategem to figure out how to mix it in your game.
=> More informations about this toot | View the thread
So, the "grind" in Helldivers 2 is enjoyable, if you're using it to test different combinations out, and not relying or trying to play with a team.
I tend to prefer PvE games in general, but I really want to choose the style of play for myself, vs supporting a team.
Solo, I tend to favor stealth and rapid recycle of support weaponry. Yes, the precision strike to take out Automaton outposts works well, but it also works because it's a rapid attack.
The sniper rifle kind of sucks, because the charge/fire cycle is slooooower than the other options.
And it can't oneshot some medium enemies.
=> More informations about this toot | View the thread
Y'know, having to implement the shitty ass version of an old API that's stuck around well past its prime, makes you really appreciate REST and JSON objects.
But, making a GET API works, and implementing the REST version of it is on my own roadmap. The good is these things can be combined to a single endpoint with different service paths.
But, man, I hate this shit.
=> More informations about this toot | View the thread
Authentication is hard, and I don’t wanna deal with it. Why can’t I just store plaintext paaaaasswoords. /whine
=> More informations about this toot | View the thread
A thing which annoys me in writing “correct code for applications” (y’know, functional programming) is that the tests and mocks sometimes represents 60% of the total lines written.
Like, I just want the damned thing to do the thing!
Anyway, I now have to write the thing to hash the private thing for storage and I don’t wanna.
=> More informations about this toot | View the thread
Over on LinkedIn, I write stupid professional things to let folks know I "know my shit." I've been doing this ops thing for so long, you'd expect me to have long since left it.
Mostly it's writing practice. I know it doesn't do much other than feed the vomit of their LLM projects, which in turn churns out the vapid "write with AI" bullshit for post responses, and quite a few posts.
It's good practice, I stand by what I write, and the topics I post (briefly) about. But I've 0 expectation of real engagement.
=> More informations about this toot | View the thread
Anyway, this is just a subtext to say "fucking querying your goddamn logs to make a fucking dashboard with SQL sucks".
Thanks Google for encouraging people to use your GCP Logging module. It's both a delight and a goddamn pain in the ass.
=> More informations about this toot | View the thread
You know what always needs improvement? Logging.
Why?
Because everyone logs all the things, but doesn't think they need to break up the logs to differentiate functionality.
So, you get 58k log lines for "Info", without a single differentiation for what those lines mean, which means you now reference the source code to find the goddamn line and compare outputs to the string being formatted.
Devs, stop trying to be clever here. Fucking be clear, concise, and make the line simple.
=> More informations about this toot | View the thread
I shouldn’t take it as telling there’s a talk on DNS basics at #38C3.
I should be happy the topic is getting attention at all.
=> More informations about this toot | View the thread
So, popping the traditional Origami Water bomb/balloon on an LED Christmas light is pretty pleasant.
https://origami.guide/easy-origami/origami-water-bomb-balloon/
=> More informations about this toot | View the thread
One thing I've learned over and over again in working with startups: no matter how bad you think things are based on what you're told by other team members, the reality is no less than 10 times worse.
There's a series of problems, most of which will need a series of efforts and project plans to address. More than half of it is architectural, the rest is fundamentally incorrect assumptions and scale issues.
This is going to be an interesting project.
=> More informations about this toot | View the thread
Honestly, if nothing else comes of this break from work, I'm enjoying messing with paper folding again.
=> More informations about this toot | View the thread
Which is not to say there's no learning opportunity there, but it's not the easy way or the best route.
=> More informations about this toot | View the thread
The wrong way to figure out someone's API is to analyze their iPhone app in Ghidra.
=> More informations about this toot | View the thread
Make it a point to add the location, the office, to the graph as well, and link who's based out of that office to the graph. Michael is not based there, but someone(s) who report to him are, and they're likely the HM.
Time to dig further at Lucifer's Berlin office, and possibly open conversations with people who know the landscape around Gabriel, the parent company.
=> More informations about this toot | View the thread
Now, that's having the HM.
What about the "job post to HM"?
I recently had a recruiter reach out for a FAANG level job as a Staff Engineer with their DevOps org. The list of technologies was pretty typical (Kubernetes, EKS, AWS, Python, Go, Rust, etc).
But, the job's in Berlin, and pretty unremarkable. Despite the employer, it's tempting just due to the fact it's challenging.
So, to start with, the company itself should be researched. With the recruiter stating which group in the company (think Facebook, "Platform Engineering", and "Palo Alto"), there's enough to seed additional information to the graph.
So, new graph, for a different position. I'll code name them here.
Start adding the company names as a Company entity. Fill in notes as needed.
Company: Gabriel
Company: Lucifer
Company: Lucifuge
Link those in their order of priority: Gabriel -> Lucifer -> Lucifuge. Lucifuse, as the BU in Lucifer, is the focus.
For shits and giggles, add the recruiter to the board by name, and add their LinkedIn profile. This is mostly so, if they're internal, you track the outreach, and if external, they'll show up more than once.
Starting with a basic search, look up the company and BU together: Lucifer Lucifuge in this case. This should dig out press releases, details on the company, and what the strategic goals are (why they reached out via an internal recruiter), and details on what the funding looks like.
In this case, the search reveals an SVP who manages the BU. Challenge is that he's based in California, the job's in Berlin. So, he's not the hiring manager, but, good to know.
Person: Michael, SVP Lucifuge.
Search gets extended based on Michael, which gets his job history, LinkedIn profile, and some additional blog posts. All good.
So, leveraging Michael's LinkedIn profile, let's dig at his social graph and add additional information to our plot.
Michael's job with Lucifer Lucifuge, provides links to a bunch of other employees, none seem likely to be the right hit, but a few are adjacent, so let's add Henry, a Staff Network Engineer, and Holly, a Staff Software Engineer. Both are Lucifer, not focused on Lucifuge, but are based in the same office in Berlin.
=> More informations about this toot | View the thread
=> This profile with reblog | Go to jb@hackers.town account This content has been proxied by September (ba2dc).Proxy Information
text/gemini