1,353 karma · joined February 8, 2023
So if for some reason I can't use Zstd, I would still probably choose LZ4 instead of Lzip.
So then, if we can cook a chicken like this, we can also heat a whole house like this during winters, right? We just need a chicken-slapper that's even bigger and even faster, and slap the whole house to heat it up.
There's probably better analogies (because I know people will nitpick that we knew about fire way before kinetic energy), so maybe AI="flight by inventing machines with flapping wings" and AGI="space travel with machines that flap wings even faster". But the house-sized chicken-slapper illustrates how I view the current trend of trying to reach AGI by scaling up LLMs.
With PostgreSQL the materialized view won't be automatically updated though, you need to do `REFRESH MATERIALIZED VIEW` manually.
I didn't know this existed, so the first thing I did is check the caniuse website, and yeah not even they have info about the Web Share Target API[1][2]. As of writing this comment, they only have info about the Web Share API[3].
[1]: https://github.com/Fyrd/caniuse/issues/4670
What has been an issue for me, though, is working with private repositories outside GitHub (and I have to clarify that, because working with private repositories on GitHub is different, because Go has hardcoded settings specifically to make GitHub work).
I had hopes for the GOAUTH environment variable, but either (1) I'm more dumb and blind than I thought I already was, or (2) there's still no way to force Go to fetch a module using SSH without trying an HTTPS request first. And no, `GOPRIVATE="mymodule"` and `GOPROXY="direct"` don't do the trick, not even combined with Git's `insteadOf`.
Writing a library in TypeScript (with typechecks in CI/CD as devDependencies) and just importing it directly from Node.js...
If I use composite actions, the logs get associated with the wrong step[1]. It's just a visual thing (the steps themselves run fine), but having 90% of your action logs in the "Complete job" step is unpleasant.
For reusable workflows there's a few open issues as well, but what happens in my case is that jobs just don't start at all, they stay as "Waiting" forever.
These issues only matter if you write your own reusable actions with YAML (the actions written in JavaScript seem to work fine), but it's worth mentioning.
Other than these two issues, I'm very happy with Forgejo and would still recommend it if people ask for my opinion.
This. It's like if you want to collect biometric data about everyone's faces with different expressions, different angles, and how those faces change over time, you just make a mobile app where people voluntarily record themselves.
So, if the problems are:
>> It requires several electrodes to be implanted into the patient first. Then there's an adaptation phase in which the patient trains the system.
Then one possible way I can think of to make people do your work for you, is to release a nice VR videogame to the point it becomes popular, and have some features that make it nicer if you ("enhanced controls", or "your HUD shows exactly what you want just by thinking it like Ironman helmet", or whatever).
Taking an existing and popular videogame and making a mod like this would also work.
There's non-zero desire for full-dive MMORPGs, so marketing it like a step towards that would entice a non-zero amount of gamers.
Once it's normalized on niches like that you'll probably have a better time expanding outside that niche, because by then it would be "that videogame tech thingy that cool and rich streamers use" rather than "the sus mind reading stuff".
It doesn't need to be videogames, but the idea is the same, you make an "inoffensive" thing that people want to use, and then leech off the collected data.
Proprietary web browsers are in a really good position to do something like this, especially if they offer a free VPN. The browser would connect to the "VPN servers", but it would be just to signal that this browser instance has an internet connection, while the requests are just proxied through another browser user.
That way the company that owns this browser gets a free network of residential IP address ready to make requests (in background) using a real web browser instance. If one of those background requests requires a CAPTCHA, they can just show it to the real user, e.g. the real user visits a Google page and they see a Cloudflare CAPTCHA, but that CAPTCHA is actually from one of the background requests (while lying in its UI and still showing the user a Google URL in the address bar).
Literally a few moments ago I was playing a video from a Nitter instance (Twitter proxy), and wanted to save it with Firefox but nope. Firefox already has the video there, I can see in the developer tools that it's playing from a blob. Even if the blob is then modified on-the-fly, why can't I right-click it and save that blob that you already have? If it's a stream, why can't I dump it? You are already playing it, you already have the bytes, you can "cache" the whole playback into a local file and then let me Right Click -> Save that "cache" file. Had to use `yt-dlp`.
Similar with bookmarks. When I bookmark something, it would be nice if the current state of the page were saved as a fallback (or at least have a checkbox for this behavior). You already have the rendered page right there. I can literally do `Ctrl+S` and save this page as it is right now, even with this half-typed comment. The code for saving the current state of a page is already there. And you can already link binary data to a bookmark (favicon), and text data (description, tags, etc). I wouldn't even mind if I have to give up the description field in exchange for a base64-encoded version of the bookmarked page, I'd be willing to accept that additional storage requirement.[1]
Sites like YouTube that actively work to prevent easy downloads and archiving might still need extensions like the one linked in the submission, but browsers don't make it easy to save some data that they already have, and it's difficult enough to contribute to (or patch for yourself) those massive codebases unless you are already familiar with them.
I'm willing to patch things for myself and repackage them for myself, but unfortunately for these things it's easier and more reliable long-term to just do workarounds.
(Disclaimer: I'm using Firefox.)
[1] EDIT: Having history enabled doesn't seem to do save an offline version, either.
It's very tempting because (I'm guessing) you just want to get out of your current situation ASAP, and of course the final decision is still yours, but this is the advice I would give my past self:
- You might not be in the best state of mind right now to make a good decision. I agree with others saying you should take time off, the more the better. Definitely more than one week.
- Try going for 1-2 months of time off if possible, even if unpaid. If your country has something like "leave of absence" that allows you to take a long period off, like 6 months or more (usually unpaid), but still be able to come back to your company after that period (or at least get priority during hires for the similar position), then try to look into that first, and consider it a "trial period" of how well your job search will go.
- You might feel good about leaving your job for the first few months, but after that you're running on a time limit. This will be on the back of your mind, and you'll have to learn to live with this worry, and not let it affect your performance on interviews.
- You'll get rejected. You'll get ghosted. You might think it's you, and part of it will be because of you, but you don't know which rejections are legit and which ones were just farming your info. This will also take a toll on you, and you will have to learn to not let this affect your performance on interviews.
- The more time you've been unemployed, the larger the gap on your resume, the better you'll have to be at explaining that gap in a convincing way. And this is without letting the previous point affect your performance on interviews.
- Remember that when you apply for roles, when you reach the last stage (the vibe check), you'll be competing against people with no gap, who might be able to perform better than you if only because they have less worries (no ever-increasing gap, no ever-decreasing money, a rejection for them doesn't affect them too much because they still have a job).
- Even if you think you have a good network that could help you get a job quickly, consider their location. Assume you'll only be able to get some help from contacts in your current location (within commute time). Even if you're looking for remote jobs, assume your network will only be able to help, at most, with on-site jobs.
- Even if you do freelance work, consider those as part of your employment gap. You might get interviews for companies that don't mind it, but assume that most companies default to treating it as an employment gap.
- If you feel bad right now at work, assume that's similar to how bad you'll feel after being unable to get a job for 1 year, but with less money on top of that. And you'll have to learn to not let this affect your performance on interviews.
---
That's what I would have liked someone told me before I left my last full-time job. I'm aware I'm just some stranger on the internet exposing how much I suck at life because I wasn't able to just get a job quickly like others, and I underestimated a lot of shit.
So I think what I want to say is, "think carefully".
> But, its tip is very fragile
I came here to say this. I have a rotring 600 mechanical pencil with non-retractable tip, and it bends if you even look at it funny. It can be straightened again if you insert a sewing needle so it was not a big deal, but it was unexpected how easy it bends.
Heck, I have to treat it even more carefully than my smartphone. Not that I treat it rough or anything, but I have to be very conscious of where I leave it, lest it rolls off and falls off a height of a few centimeters.
Other than that I don't regret buying it, it's been a few years and it still feels nice to use.
https://github.com/grafana/tempo/discussions/5001#discussion...
(Yes, that's for Grafana tempo, but the issue in `grafana/grafana` was just marked as duplicate of this.)
The only inaccurate thing of that meme page is that you only need to uncheck 5 cookie "partners", when in reality there should be at least a few hundred.
Maybe they were thinking about something like the "clustered indexes" from SQL Server, and mistakenly thought PostgreSQL also worked like that:
> "When you create a PRIMARY KEY constraint, a unique clustered index on the column or columns is automatically created if a clustered index on the table doesn't already exist and you don't specify a unique nonclustered index." [1]
> "Clustered indexes sort and store the data rows in the table or view based on their key values." [2]
So I'm guessing you could squeeze some extra performance for certain access patterns, maybe? I have not worked at any place where I had needed to worry about low level details like this, though, so obligatory disclaimer to take this comment with a grain of salt due to my lack of first-hand experience.
[1]: https://learn.microsoft.com/en-us/sql/relational-databases/i...
[2]: https://learn.microsoft.com/en-us/sql/relational-databases/i...
I forgot to put it in the title and I can't edit anymore.
If anyone out there is already fully committed to using only Alpine Linux, I'd recommend trying creating native packages at least once.
If I had to rewrite my previous message in a less subtle way, it would be that companies are constantly contradicting themselves when giving any public "reason" for their actions, and I do not think employees' happiness (which fathomdeez focuses on) is anywhere close to their actual reason.
- Human contact is more important than efficiency gains, hence mandating return-to-office.
- At the same time, efficiency gains are more important than human contact, hence reducing human headcount in favor of increased AI use.
If you read between the lines, you can see how those two points are related: humans find difficult to feel connected when their communication partner is just pixels on a screen, so that's why remote workers are being replaced with AI.
Both ways. It can't be just one side always bending backwards while the other doesn't, without even any intention to meet in the middle.
> 34 seconds later, it was done. Not just a quick hack...proper production-ready code with error handling, logging, environment checks, documentation, the entire implementation. Working, tested, committed to git.
> This wasn't copy-paste from Stack Overflow. This was bespoke, production-ready code tailored to my specific Laravel app, following my existing patterns, with proper security considerations.
And with their proposed "AI-Optimized Process" conspicuously lacking code review, QA, manual approval. Just going straight from prompt to production, with no human supervision after the prompt is written. Otherwise those steps would have been mentioned in the list, the same way "Traditional API Integration Process" mentions them.
At that point might as well add a button to Jira that says "Implement this".
Seeing how everything seems to be broken everywhere, I'm very much looking forward to the post-mortem.
EDIT: Updated link to point to the specific incident.
"Tell me about a time when you tripped over while commuting."
"Tell me about a time when your feet touched each other during a walk."
"Tell me about a time when you were facing north-east and a bus passed in front of you." [follow-up question] "What type of bus was it? [suburban, long distance, etc] You say you saw it, so walk me by your visual experience."
If you have lived your life as a walking person, as you seem to imply by your comment, you surely have done these things multiple times, right? Failing to respond in a truthful and satisfactory manner will be counted heavily against you.