When one of my sisters got her first paycheck from her first real job, she didn't knew much about banking, and thought that the overdraft limit on the ATM was her actual salary, so she just withdrew the whole thing. I think it took over a year, maybe two, to pay it all back.
As a consultant data engineer (ish), I think it has potential. You're right that any company doing data analytics is gonna be prioritizing a single source of truth and a unified platform, but each one will choose a different set of tools, which I'll have to learn, install, and even teach, for each new client. If I can use this to both explore AND implement stuff for clients regardless of their underlying database, that would be a pretty significant win.
> We're rewiring internal processes with AI agents, automating the reviews, approvals, and handoffs to speed us up, and plan to right-size roles across the company to follow suit.
Ah, yes, finally gitlab will have the same uptime leves as GitHub.
I would usually side with Wikipedia, but the article says the registration process the government is asking for is free, and a from a quick google, not really invasive. It does seem to require a tax number of some sort, which could be a problem, but still, is not exactly a super unreasonable ask. The government reaction is kinda unreasonable, specially towards fucking Wikipedia of all sites, but, alas.
Side note, Jesus Christ on a bicycle, this site has a ridiculous amount of ads. Literally could not read the article at the first try, had to reload and enable reader mode before the 1937391 popups started jumping on my face.
That was an informative post but Jesus Christ on a bicycle, reign in the LLM a bit. The whole thing was borderline painful to read, with so many "GPTisms" I almost bailed out a couple of times. If you're gonna use this stuff to write for you, at least *try* to make it match a style of your own.
As an interesting linguistic coincidence (or not), FDP is a commonly used acronym in Portuguese, standing for "filho da puta", literally, "son of a whore", but semantically it's approximately "asshole/jerk/dickhead".
That's a banger article, I don't even like low level stuff and yet read the whole thing. Hopefully I will have opportunity to use some of it if I ever get around to switch my personal notebook back to linux
Gotta say, did not know direct energy weapons were actually leaving science fiction and entering the real world yet, but it seems they're. It's obviously not star trek level, but it's way more advanced than I expected
News just in, too much of a good thing sometimes is bad. After the break, new study reveals: the sky is (sometimes) blue and the grass is (sometimes) green.
I hate hello-how-are-you-then-wait-before-asking messages as much as the next autistic programmer, but both examples in the "more examples" section still kinda read like an asshole, because they present as fact things that often either aren't, or you couldn't be absolutely sure of it.
For instance:
> "The caching layer is causing a 400ms overhead on cold requests. Here's the trace."
Cool, but how do you know that? Are you sure you're interpreting the trace correctly? How many measurements have you done? Sure that there isn't a historic reason why the caching layer behaves in this way, or a conflicting requirement that lead to choosing this latency over some other, worse consequence?
In the same way:
> "The current error handling swallows exceptions silently, which is making debugging hell. We should propagate errors to the caller"
Agree in principle, but did you check git blame to see if there was a rationale? Or asked someone else? How much change would this require? Could it break consumers of our code?
Granted, the "polite" messages didn't care any of this information either, but at least they didn't almost preemptively shut down the conversation by laying down what is at best an well informed guess and at worse purely personal opinion as if it's irrefutable truth.
Perhaps instead of debating whether to be (too?) polite or direct, it's better to focus on providing as much information as you can, anticipate follow up questions, and close with clear actionable next steps, something which is also missing from both versions of the messages.
"Well, those are hypothetical examples" cool, another evidence that we're all talking out of our asses about the sex of the angels, here. Maybe if the author didn't try so much to characterize themselves as perfectly infallible information delivery machine, then I wouldn't have nit-picked so much their half-assed hypotheticals.
Thank god I found this page: https://causality.blog/series/, now I can relax knowing that at least there's a plan for a conclusion. Looking forward to the next posts
That's cool and all, but can we pass a law that this can ONLY be used for games? Because I remember the web when flash was everywhere. The games might have been fun, but everything else sucked humongous balls. Let's not get back to that.
Congrats on making it work pretty much flawlessly on mobile, it's kinda rare for terminal-themed sites. It was pretty fun to navigate around, too =)
One (I think?) bug report and one suggestion:
- bug: can't get past the 5th project on mobile, whole screen just go black and I have to reload the page.
- suggestion: maybe make cd ~ or something like that bring the user back to the actual initial state, with the login banner and stuff. Just running clear results in an empty shell, and the user has to remember to run help again.
P.S.: I ran the secret command. You son of a gun XD
P.P.S.: Two suggestions, actually: display your CV with pdfjs or something, or make an HTML version. It's annoying to have to download files.
Man, I feel bad for Docker, the company. Created the open source project that almost single-handely revolutionized deployments, development environments, and cloud computing, but sorta never managed to stick a product.
I can't tell if I find it funny or sad how obvious it is that Roy needs to be on several psychiatric medications that he isn't on, and that he's on a fair amount of cocaine (or insert whatever uppers the kids are into nowadays) that he shouldn't be on.
I'm not sure I can trust the author's characterization of Roy, though. I got the impression that they don't like any of the people they interviewed (which, you know, fair), but that doesn't get even close to the depths of hatred towards Roy that they sub-textually exude throughout the article.
If their portrayal is even half accurate, though, that's a perfectly reasonable amount of hate.
Come on, two levels ain't enough for anything serious. Also, the notes feature is not rendering any differently.