Hacker Newsnew | past | comments | ask | show | jobs | submit | azthecx's commentslogin

Not all companies operate like this, but many large ones do. Smaller chops can have exactly the kind of culture that you describe, but they're also quite often hard to find as they tend to have some stable business and long employee retention, it's unlikely you will find them at the same time you're looking for a job.


Yeah I am lucky enough to be in a company with a solid culture now.

I definitely think you need to avoid companies with 1) large turnover, 2) investor-driven growth metrics, and 3) a hostile or passive approach to company self-criticism.

Like the guy in the article, I have found that companies which hand-wave away legitimately good ideas or criticism in favor of some vague “strategy” reason tend to be untrustworthy. Well-run companies want to improve themselves, even if they don’t have the resources to make that improvement quickly.


I currently use Headscale, can you give some more details on how you use this to the same effect as Tailscale / Headscale?


Yggdrasil is a more generic overlay. It can run over unconfigured Ethernet links, auto-discover other nodes on your local network, or punch through firewalls if you configure any public peers. You can setup a private network by only declaring your private peers. I think each device gets an entire subnet, so you might be able to expose multiple services on multiple IPs, though I'm not sure about that.

My use-case was sharing things like game servers and websites with friends—which we previously did by sharing each other's machines/servers via Tailscale—and accessing my homelab remotely. For the first case, the public Yggdrasil network was much better than a mesh VPN like Tailscale: I don't have to manage invites or accounts—everyone who knows the address can just connect.

For the second case, assuming addresses are discoverable (since 128 bits would make them quite hard to enumerate), I think a firewall gating by incoming IP will take care of that (since your IP is just a hash of your public key), though for now I've kept most sensitive ports unbound from it. I hadn't yet tried anything like Tailscale bridging (exposing a LAN address without configuring the client on the endpoint), but I'll try once I have a bit more free time.

Tailscale is a nice abstraction on Wireguard, but Yggdrasil feels less like a solution to your specific infra problems and more like a coherent vision of how the internet ought to be. You can just rely on IPs as identities, link-layer encryption with Noise Protocol, and out-of-box hole punching, with relatively low latency (though I haven't tested the speed). It's the same feeling of awe as when I first saw how easy it is to host Onion Services, only not hampered by the abysmal speeds.


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.


You clearly are delusional if you believe that the people drowning in credit card debt are in ever in this position.


Please don't put words into other people's mouths, I've never made that claim nor do I agree with it.

    Margin stock accounts also exist, although I don't know enough to know what situations it makes sense to use them in.
I was obviously replying to this part of the parents comment.


Interesting slides, it's always nice to see different ways to set up these kinds of systems and with a practical git repo to boot!


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.


If you're looking at the CLI there are specific man pages for it.

You can find creation here https://github.com/git-bug/git-bug/blob/master/doc%2Fmd%2Fgi...

And status update here https://github.com/git-bug/git-bug/blob/master/doc%2Fmd%2Fgi...


Yeah it was right in front of me and I missed it. Thanks a bunch!


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.


Odd. How can one get the vibes without looking at the code? Like gleaming diamond vibes versus confused spaghetti vibes.


I think the vibes refer to the running software, not to the code itself. I hate the whole concept deeply.


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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: