With this type of experience and knowledge requirements, even Cryptography, that pay range seems quite on the low side. Someone with those skills can get paid far more in the Netherlands
Did you really notice a significant drop off in connection attempts? I tried this some years ago and after a few hours on a random very high port number I was already seeing connections.
I use a non standard port and have not had an unknown IP hit it in over 25 years. It's not a security feature for me, I use that to avoid noise.
My public SFTP servers are still on port 22 and but block a lot of SSH bots by giving them a long "versionaddendum" /etc/ssh/sshd_config as most of them choke on it. Mine is 720 characters long. Older SSH clients also choke on this so test it first if going this route. Some botters will go out of their way to block me instead so their bots don't hang. One will still see the bots in their logs, but there will be far less messages and far fewer attempts to log in as they will be broken, sticky and confused. Be sure to add offensive words in versionaddendum for the sites that log SSH banners and display them on their web pages like shodan.io.
In my experience can cut out the vast majority of ssh connection attempts by just blocking a couple IPs. ... particularly if you've already disabled password auth because some of the smarter bots notice that and stop trying.
As a software developer do you genuinely believe that it is harder for indie game developers to build online infrastructure and pay for its hosting costs rather than build some LAN feature into the game, or to package local server binaries into the game as it was done just a few decades ago?
Most indie games I've play don't even run their own online infrastructure because of costs. Why bother, when you can just use a storefront's matchmaking for free? And storefronts provide it as a means of soft lock-in. For example one of my favorites, Deep Rock Galatic, doesn't have crossplay between the Steam PC version and the Xbox PC store version of the game.
And there's already software to emulate Steam's matchmaking because it's so common.
There are arguments to be made, especially if you're young and just starting out to take a reasonable amount of margin and kickstart your compounding growth.
Say you just started working, have no use for your money and are willing to bet 20k on index funds vs a 90% market drop, you should be able to take 2k in leverage and set up your position be auto closed.
But of course as you have more money this type of market exposure starts shifting as you have shorter timer horizons to rebuild and are instead going into more of a wealth conservation mode.
In general the public transit system in the US is so underfunded and badly executed when compared to road infrastructure that only disadvantaged people that can't afford car transportation will even consider using it.
Yes but that’s not by “design” like you alluded to. It’s because the advantaged people with cars don’t really care about funding the transit system. So if anything the “design” of transit, only taking the poor to where they want seems purposefully molded by the privileged.
No, with vibe coding you are not a reviewer an editor or an author, quoting from the source:
There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.
...
I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it.
No, they actually have the files pane on the left, live preview mid-top, terminal errors mid-bottom, and the agent on the right. no looking at code.
Cursor has a "yolo mode" where you don't have to click accept for tooling even for system commands and people whitelist commands like sudo, su, and rf :))) I wish I was kidding.
The vibes are coming from changing to actual product (design, UX, functionality) and not from the code. The code in fact doesn't matter at all. At this point that's only ok for throwaway prototypes (but for those it's quite wonderful), the more the application requires careful maintainable engineering, you need to read every line and leash the LLM. It's a bit of a continuum between the two edges in reality.
> No, with vibe coding you are not a reviewer an editor or an author, quoting from the source:
That was the joke, which Karpathy found "quite amusing" and "not too bad for throwaway weekend projects". In reality, you won't even get that far with vibe coding if you don't understand what's going on.
At first glance it's not immediately obvious to me, why would you pick Sentry or Bugsink over something included in the Grafana stack? What's the use use
I haven't used Sentry's obserability portions, but the error capture has very strong deduplication built into it, and can optionally integrate with your SCM, CI, and issue tracker, if one wishes. Thus, the flow can go like:
- error happens, can be attributed to release 1.2.3
- every subsequent time that error happens to a different user, it can track who was affected by it, without opening a new error report
- your project can opt-in to accepting end-user feedback on error: "please tell us what you were doing when this exploded, or feel free to rant and rave, we read them all"
- it knows from the stack trace that the error is in src/kaboom/onoz.py line 55
- onoz.py:55 was last changed by claude@example.com last week, in PR #666
- sentry can comment upon said PR to advise the reviewers of the bad outcome
- sentry can create a Jira with the relevant details
- claude.manager@example.com can mark the bug as "fixed in the next release", which will cause sentry to suppress chirping about it until it sees a release 1.2.4
- if it happens again it will re-open the prior error report, marking it as a regression
Unless you know something I don't, Grafana does *ABSOLUTELY NONE* of that
