skysight-inc/HackerNews huggingface dataset:
> I'm going to find whatever port your running ssh on if your running it.

I still think it's a good idea. With SSH on port 22, ten thousand bots plus an attacker try to hammer it (so says fail2ban). With SSH on port 9278, zero bots plus an attacker try to hammer it. By throwing away the 99.99% of the chaff, you can see the remaining wheat you care about.

Changing SSH ports isn't about saying "yep, we fixed it!" and calling it a day. It's about decreasing the amount of stuff you have to deal with, which is quite useful. It's something you can do in addition to everything else that gives a decent bang for its buck. No, it doesn't keep you out, but it does keep out those thousands of bots crawling around looking for an open 22 to pester.
That's right, I would run into even bigger performance issues if I used Integer/Long/Double/etc everywhere instead of the primitive types. The problem is not that primitive types are not object, but rather, that generic code will only accept objects and not primitive types.
No need for (much) CSS, browsers already support vector graphics: SVG!

In Pandoc, what you would do is you would use a general Latex plugin, and then TikZ supports PNG or SVG output by 'standalone' (https://tex.stackexchange.com/questions/51757/how-can-i-use-...), and you can either save that to a file & use as an image or you can inline them.

This uses Latex at compile-time, but considering the extent to which TikZ is a graphics DSL, I wonder how hard it would be to implement a TikZ->SVG compiler as a standalone tool in a different language? (Or make it available in a variant like Mathjax? Like https://github.com/kisonecat/tikzjax except without running an entire TeX engine in the user's browser.)
> managers have power

Respect, too. I've lost count of how many times I've been stuck waiting for somebody in the network group to grant me access to some resource I need to do my job until somebody that they actually respect (that is, a manager) tells them that they have to.
Most comments seem to be encouraging to stick with programming, which on one hand is great.

But you asked a more general "what to do" I think/interpret; can you edit your post as to what other skills or interest or career background or experience you may have?

If you are a generalist techie with surface understanding of large number of technologies, and willing to explore that more / dig into things, there are "architect"-type roles you'd potentially be good at (and an even larger you'd be terrible at of course; the title covers a huge breadth of scope).

Are you good with people, communication, customers? Do you understand business needs? A manager who at least understands technical aspects can be invaluable. Yes, management is a tricky word in the world of technology and on HN, but I still believe that experience with dozens of bad managers is all the more reason to try to be a good one :)

Sales, advanced support, etc are all also options.

System administration of some kind may also be for you; fwiw I've been a "PeopleSoft Administrator" (PeopleSoft being an ERP like SAP, JD Edwards, Oracle eBusiness, etc) for 15 years (not one anymore but I'm still in similar space), and my breadth of skills was an advantage - a bit of DBA, a bit of sysadmin, a bit of middleware, a bit of scripting and programming, a bit of architecture, a bit of business and functional understanding, a bit of operational awareness, and tremendous curiosity and willingness to research and "figure it out" - that cross-section of curious understanding made me well respected and sought after in that particular niche, and there are hundreds out there like it.

I think important question that only you can answer but you haven't given one in your question is: do you want to stay a developer, or are you willing to explore other options close to or further away from that?
Back in the day we had engineers writing documents from markup. We called them typesetters. It was a qualified job, you don't expect the task to be something Joe Random could to with 6 weeks of training.
I've always wondered is the iPhone X built Sept. 12th 2017 the exact same hardware as one built on iPhone X 2018? Is the one built in 2018 better, do they fix hardware issues on later builds?
From the wikipedia page: In the field of psychology, the Dunning–Kruger effect is a cognitive bias in which people with low ability at a task overestimate their ability. It is related to the cognitive bias of illusory superiority and comes from the inability of people to recognize their lack of ability. Without the self-awareness of metacognition, people cannot objectively evaluate their competence or incompetence.
It is a meme that is largely self-fulfilling under the wrong organizational incentives: as managers control how and what information flows in an organization, managers in many organizations claim a lions share of credit for successes and delegate failures.
What is more likely: that Musk is a genius electric car engineer, rocket engineer, battery engineer, tunnel boring machine engineer, ... ? Or that he takes credit from those people in his various teams?
Don't get me wrong, there is certainly value from assembling the right team.
I've literally been on a date where I told a woman I was thinking of getting a cat and her exact response, in a public restaurant, was "that's gaaaaaay"; she was a data scientist.
We're not talking about the difficulty of writing a document using LaTeX, which I think we can agree is more or less proportional to the degree of control one has over the finished product.

What's at stake here is the difficulty of editing the source code of LaTeX, which would be necessary in order to make the resulting pdf files more compatible with screen readers for the visually impaired.
1. I'm not sure. It's only my assumption, but it should definitely be verified. Obviously if the assumption is bad then my conclusion is no good.

2. Several broad categories of solutions spring to mind with their own tradeoffs:

2.1 Invest in rehabilitation. Difficulties are cost and probably political problems due to ignorance (or maybe I'm ignorant for my faith in rehabilitation?).

2.2 Longer sentencing (or rather require prisoners to serve more of their sentence more frequently, as opposed to early probation, etc). Downside is cost, ethics, and politics (a lot of well-meaning, typically upper- and upper-middle-class folks believe that longer sentences harms communities of color more than violent re-offenders, or rather they don't consider the costs of the latter).

2.3 Death penalty. Downside is ethics.
What Is AI and How Does AI Research Work?
You have one great advantage. You can self-teach. Don't try harder just focus on things you don't know.

I'm self-taught as well and my degree didn't do a great job of introducing concepts that are common place in CS degrees (and hence job interview hazing rituals). It took a long time of me feeling bad about what I didn't know to actually go out and learn about these things. Turns out most aren't nearly as scary or complex as you'd think. As with a lot of academic topics simple concepts are dressed up in domain specific terminology.

Also don't knock breadth of knowledge, lots of very useful prods to problems come from having a wide set of things to draw on. Sure it might be finished by a specialist but they didn't make that leap.

And if none of that is true for you, you are good enough to be here as evidenced by being here. Enjoy it for what it is.
Makers, start with a non-scalable product
Performance is irrelevant to the principle involved.
I like to think of this in military terms.

"Don't be where the enemy expects to find you."

As TFA and several others have pointed out:

(1) Don't use this as your only method of defense. The further from your LOCK the better the key needs to be.
(2) Use your security in the layers that offer the most benefit.
(3) Be proactive in your defense.

-Changing your SSH port will stop that largest number of attempts on your service.
-A non-default port PLUS port-knocking PLUS key-only PLUS whitelisted IPs PLUS whitelisted login names. Is better then only one of those.
-Apply very liberal firewall rules to prevent any unauthorized from IP's that should have access to your service. Country-code level blocklists are a thing.

Being obscure is about NOT being where your opponent expects to find you.
>ssh non-standard port is actually a good thing given the massive amounts of bots around

Except that if you use a port above 1024 (like the author does) you no longer have assurances that it is a privileged user that launched the process. Any non-privileged user on a Linux system can bind to a port higher than 1024, so all it takes is sshd restarting after an update if it's directly listening on a high number port, or iptables rules getting reloaded if they're being used to forward traffic from a high port to 1024 and an attacker can have their own credential collecting service running where you think sshd is, and all it takes is someone ignoring the host key mismatch error to give up your good creds to an attacker, and now they have more access into your infrastructure.
I'll give it a shot. When you entangle two particles, it's kind of like they're connected to the same random number generator. So if you measure one particle it'll collapse to a certain value (at random), and you know that the other one will also collapse to the same value (or some other such correlation, depending on how you set up the entanglement). You also definitely absolutely cannot use entanglement to communicate information.
I wish more examples of serializers would show the resulting Hash or JSON, rather than just the DSL syntax.
In many cases it is much better to fake (or spoof) information, rather than try to hide it. Browsers come into mind. Instead of trying to hide information about yourself, which would make you unique, just give them false information that is common, and that way you blend in with the rest of the people, everyone is content, and nothing true has been revealed of you.
> project manager

In every organization I've ever worked in, project management was very different than management management: project managers never ended up actually "managing" people as in hiring, firing, budgeting, setting direction for, etc.
An imposter is: "a person who pretends to be someone else in order to deceive others, especially for fraudulent gain."

So if you're honestly questioning whether you are capable or not, then by definition you're not an imposter. Some people are actually imposters but they are not the ones openly asking for advice about it and asserting that they don't belong.
How to Change Your Mind over a Glass of Wine
> As long as the package manager can turn the registry namespaces into something usable from Rust,

All I am trying to say is that this is a technical problem, in addition to the larger problems, which you correctly identified are social.
There's a bunch of counter-argument here from working practising blind mathematicians who read and write raw TeX every day, so there's at least a non-zero audience.

https://www.nfb.org/latex-what-it-and-why-do-we-need-it-0
Believe it or not, HTML, CSS, and MathML are still going pretty strong in the educational publishing industry.

MathType supports TeX input. MathJax accepts TeX input. The technology is already there, there's just very little mindshare because no one cares about accessibility.
>>"All of this and more, for £200,000 a year."

Unless the British Government is giving out some windfall of equity this is the compensation package of a mid level software engineer at FAANG. For anyone remotely qualified for this kind of job it is an absurd pay cut. Given this budget I would suspect that the department will also be asked to hire staff at salaries that are well below market rates. In other words the position is set up to fail and a simple google search could have shown as much.
Stargate Project
You are absolutely right that these things are the true solution to not have depression. However, they don't really work when you are already in it though. It's like telling a drowning man to start practicing his strokes or someone falling out of a plane to invent a parachute.

Depression is a self sustaining problem. The depression prevents you from seeking social activities, taking care of your body and mind and being creative, This obviously makes the depression worse. Paradoxically, forcing yourself to do any of these activities makes the depression worse as well due to the internal resistance to get better.

We definitely do need innovation. We need something that works, is scalable, doesn't cost $1k per month in therapy fees and doesn't have any adverse side effects.

My current best guess about the future in this space is a combination of microdosing and supportive apps like mine.
A few of the best of HN links are pointing to the wrong posts
As others have mentioned you may not be as bad as you think, especially if you enjoy coding as a hobby. But if you really are bad, then consider what related skills you may possess: Do you have strong opinions about what functionalities a program ought to have and how they should work? Are you good at project management? If so look for Program Manager jobs. This is not a people manager position, although it does require strong people skills. It is about defining what a product should be, working with designers and developers to get it implemented and talking to customers and collecting their feedback.
> Using a non-standard SSH port is a bad example because nmap can see through that deception in a few seconds.

Compared to milliseconds. Do yourself the favor and open one sshd on port 22 vs one on a port >10000, then compare logs after a month. The 22 one will have thousands of attempts; the other one hardly tens if even any.

The 99% level we're defending against here is root:123456 or pi:raspberry on port 22. Which is dead easy to scan the whole IPv4 space for. 65K ports per host though? That's taking time and, given the obvious success rate of the former, is not worth it.

Therefore I'd say it's the perfect example: It's hardly any effort, for neither attacker nor defender, and yet works perfectly fine for nearly all cases you'll ever encounter.

EDIT: Note that it comes with other trade-offs, though, as pointed out here: https://news.ycombinator.com/item?id=24445678
Think as in a passing thought of "fuck all of this why bother" , or Think think? The former I'd estimate 90% of people have from time to time.
But if it's Think think you need to let some people close to you about this and look for some professional help, no point in suffering like this.
This is a $150 textbook ($75 used $25 Kindle): have you read it and actually gotten value out of it? https://www.amazon.com/Building-Successful-Online-Communitie...
How I Lost All My Money in the Stock Market and What I Learned
Links in the Hacker News part point to wrong URLs.
The first question to ask yourself is if you have the desire to be good. If not, find something else.

The second question is more of an assessment of yourself. Do you possess any of (there’s a lot of overlap here) tenacity, persistence, gumption, chutzpah, drive? If so, is it enough to keep you engaged in solving a problem until you succeed? If not, find something else.

If you can clear those obstacles, then you need only choose something to focus on and run it down to the end. Then you have that in your tool belt. You might have to start with running down how to triage the best thing to learn next. But if you stay engaged in the process and never give up (seeking recreation or sleeping on it isn’t giving up) you will become great.

Anyway, I acknowledge it is easy for me to be cut and dry in how I see your challenges. I just never gave up. Here’s an example, it took me like 3 weeks in high school to understand what an array is and how it works. We were given one week and my fellow students cleared it on time. Very frustrating, but I persevered.
The bad rep is probably due to too many people having used Obscurity as an excuse to hide the fact the actual security was, at best, an after though for their product.
I can see the issue as a circular trust one given precedent's magnified power in government that it multimillion dollar salaries would wind up proliferating and abused for ones who don't remotely have talent and any metric to try to limit it would get specification gamed to hell and back.

It seems to be a Morton's fork of expertise and stakeholding separation. If they are of the bueracracy they may be tempted to use it to exfiltrate wealth to cronies. If done by a ballot initiative they by definition wouldn't be informed at large about specialist topics (if they were it would fail to be specialist) and would be outside the context.

Being willing to pay a million for proper results would be a good deal but the devil is in the details for how to do it right systemically which is hard even before dealing with people in the system.
I would call that system secure. It does not just rely on an obscure password but is actually restricted by a list of whitelisted networks.

The failure in that case is only that the admin didn't consider that normal work might be done from home at some point or that the middle or upper manager thinks that he should be able to freely administrate his critical infrastructure from anywhere...
Sure does, I have the same day as you. But wasn’t it pg’s blog and not Reddit that sent the initial users? Starting to get hazy on the details.
I've worked in hardware development for a long time, though not for Apple.

The answer can't really be reduced to a single number. At this scale, products might released to manufacturing somewhere around 3 months prior to the launch date to allow time for ramp-up. This means the design must be finalized and tested several months before release to manufacturing.

The majority of hardware and software development doesn't require a complete prototype that matches that final iPhone form factor. Early internal development would be performed on large development boards. The original iPhone prototype board was easily 10x the size of the final iPhone. Photos available here: https://www.theverge.com/2019/3/19/18263844/apple-iphone-pro...

Apple quotes the original iPhone development time as 2.5 years. Later models are built as an evolution of previous models, so start to finish development times are likely shorter for newer models. Development likely operates on a rolling schedule, where each team moves on to their next generation iPhone work as soon as they finish up most of their work on the upcoming model.

New features like face unlock or thumbprint fingerprint readers are likely prototyped separately and will only be included in the upcoming iPhone model if they're sufficiently far along when the design is locked down. If a new feature is too risky or isn't mature enough, it can be pushed to a future model, at least until the design is locked. This means that some features could be in development for many years, across several iPhone generations.
To be clear, you can always depend on a package from your own host, or from a git URL, today.
I agree. If I run my SSH and my VPN on non-standard ports, the number of probes I get a day goes from hundreds to one or two.

If I change the admin page of a Wordpress corporate site URL to something other than the standard wp-login.php the number of scripts that try to crack it each day goes from a thousand to zero.

It's _very_ effective, along with other precautions for locking these things down.
Probably, some of my offers were well north of that as a swe with only 3 years of experience out of college.

The role they are asking for sounds like it requires a deep understanding of software development, people management, and the UK government to be effective, for a entry-level compensation .
I laughed, this is very true.
Did you miss https://news.ycombinator.com/item?id=24439378?

We don't want to have to ban you. Help us out and please stop and don't do this again.

Also, your recent comments have clearly been using HN primarily for political and ideological battle. That is also against HN's rules: https://news.ycombinator.com/newsguidelines.html. Please don't do that.
I am well aware that there are many other uses. That is the problem. Uses that are beneficial are the rare exception.
> Most has to do with automation.

This.

Don't ever put anything into production that's not automated. Ever. "Oh it's a simple HTTP server that's going to be used by 5 people". Cool. Automate it. "Oh but it's going to take time!". I thought you said it was simple...

When things are not automated, we treat them differently. If a server is not automated, now it becomes time-consuming to setup another, which means it's now a pet, not cattle. But if it is automated and is misbehaving, we can easily replace it (and save the current for troubleshooting later if necessary). Or we can spin up 100 of them.

Same goes for development. If builds are not automated, they become more difficult to do, more error prone, which means people will avoid making contributions unless they are forced to do so (by some ticket). When contributing to a code base that has no guardrails becomes a lose/neutral proposition, people won't want to.

And now it's been 5 years and it's difficult to automate things because there's a 100 different workflows that people use and you are going to break them.
> A perfect example is a missing element in a remote system. An old api would throw some sort of a Element Not Found Exception.

Wait, if the example involves a remote system how can the Exception be the bottleneck? Even generating the completely optional stacktrace shouldn't take that much time.
Also look into SEO. Its technical and marketing.
Indeed, the "real-world" examples suffer from two problems:

1) The former is not security by obscurity, the car the president is in is a secret. Any attack on the president is rendered much harder because of the process even if you know what the process is. Just like regular cryptography.

2) This isn't security through obscurity because the attacker learning your system wouldn't help them. Because the attacker is, literally, a bird-brain.
In the USA, we live in a system where power is held accountable. Every single thing you mentioned was a atrocity and we are able to speak about it, learn about it debate it and replace our leadership to stop it from happening again. Your argument is pure whataboutism, a term coined to describe Soviet propaganda in the 60's. The reason it's still legitimate to bring up Tiananmen Square is because it is still denied, censored and unaddressed. The Nazis killed the gays right along with the Jews and I would face the death penalty in many countries today. I think I have a realistic take on what's at stake personally if we lose our free and open society. My gauge for evil is what the powerful are willing to do to the weak to increase their own power. By your argument, we can never call out evil when we see it. Instead of silence in the face of the evil we personally recognize, let us all speak!