unimpressive

Oh huh, I can totally see how that works but would not have predicted it/thought to check because it's not my blog. My apologies.

We bought that too, haven't set it up yet.

I think you may be a bit different than the modal person being targeted with this site.

That's much better phrasing, thank you. :)

You mean this blog with default CSS? And barely any site navigation?

https://slatestarcodex.com/2014/05/23/ssc-gives-a-graduation...

Obligatory Sci-Fi premise:

https://www.greaterwrong.com/posts/5wMcKNAwB6X4mp9og/that-al...

More in this vein: Your superior knowledge won't even give you an edge in technology investing/founding.

https://www.gwern.net/Timing

I definitely find the OP's perspective a little obnoxious. Being less-wrong is actually fairly easy (in the grand scheme of things), the problem is that nobody cares about being right.

Yeah, hearing TG's UI/UX described as not good made me do a double take. It's the best UI I've ever seen in a chat app, and I've probably used at least a dozen by now.

>The actors I've seen taking advantage of it are highly unlikely to front up with a credit card and provide what amounts to personally identifiable data (i.e. make a credit card payment) in order to mass enumerate the API.

Unless they just steal a credit card. Not unlikely, given who we're talking about here.

>as soon as legislation is introduced by governments to make the parties producing software or hardware responsible for the stuff they dump on the open market.

AKA the plausible end of open source. Once writing any program and sharing it can get you sued, people will stop doing that.

>I had a high school teacher who described what he called a failsafe study method:...

At this point you should just use spaced repetition. It's what I did, it has the same effects for a lot less work.

Reminds me of: http://messymatters.com/tagtime/

Which is a pretty well formed solution in this vein, unfortunately written in Perl.

I would honestly just copy it as an iso with something like dd.

>The only thing guaranteed about "open source" software is that you can read the source.

'Open Source' was/is a rebranding of the term 'Free Software' to make it easier to sell to suits. Eric Raymond has said as much about his invention of the phrase. The idea that it's just about "being able to read the source" is wrong. It's not vague at all, you just didn't do your research.

https://opensource.org/osd-annotated

> Looking at their previous partnership with ProtonVPN, ten dollars a month for a VPN seems a bit high. My self hosted Algo instance only run ~6 a month with tax.

You are not the target market for this product. "A few more dollars than my self hosted solution..." is a sentence that typically takes you way outside the target audience of most products in this vein.

Yes. Exactly like that.

It is generally adversarial to call people labels they wouldn't use themselves. Sometimes that adversarial tone is warranted. On Hacker News, in a top level comment that's starting off the conversation is probably not one of those places.

>Surely our concept of objects and OOD can't be that bad

How would you know if it were?

Sorry but, what does the GDPR have to do with this story about China? China doesn't care what laws Europe writes.

Location: Seattle Area

Remote: Yes

Willing to relocate: Yes

Technologies: Python, Django, Basic Machine Learning, Java, Rust, Lisp, Linux, HTML, CSS, GraphQL

(Note: Programming Languages presented in order of skill level/experience, other stuff presented in order of importance)

Resume/CV: http://www.jdpressman.com/jdp_resume.pdf

Email: jd@jdpressman.com

----

A few fun projects I did recently too small for my resume:

Rust-based substitution cipher solver: https://github.com/JD-P/ctool/blob/master/src/main.rs

Non-Rigorous K-Means Cluster Analysis of Effective Altruism cause area priorities, with spatial table: http://www.jdpressman.com/public/ea/ea_cluster_spatial_table...

Fresh out of college, so I'm especially interested in opportunities that will grow my skillset or present tough technical challenges.

At the top of the page, orange button. Took me a minute to spot it too.

Ted Nelson was banging this drum as far back as 1974 with the concept of Cybercrud as discussed in Computer Lib/Dream Machines: New Freedoms Through Computer Screens. If you go back and actually read that book, you'll realize that basically everything he says about computers then is applicable to computers now when it comes to lies told to users. As an example, he points out that 'computer people' will routinely tell users that something can't be done when the reality is it's entirely possible but the software won't do it.

That we don't seem to have made much progress in 50 years is pretty disappointing.

>And I mentioned personal sites disappearing, and I still stand by it - yes, of course there are blogs and what-not, but they're not the same. They're hosted, fast, efficient, and typically use approved themes. If you want to get down and dirty and actually make your own site, it'd be looked at as a gigantic waste of time. Technology has come too far for it to be practical to build a fancy site out of pure flat HTML files that looks like the worst 90s sites. Why do that, when you could just have an out-of-the-box Wordpress or Tumblr site?

I still write my website by hand. I use a static site generator to do things like make a blog index and stuff, but I don't use any templates. Everything you see is designed by me.

http://www.jdpressman.com/

"Let’s go all the way back to 1996 and talk about Section 230. I think historians are completely in agreement that this is the law that made the internet what it is today.

----

We thought it was going to be helpful. We never realized it was going to be the linchpin to generating investment in social media. We envisioned that the law would be both a sword and a shield. A shield so that you could have this opportunity, for particularly small and enterprising operations to secure capital, and then a sword [by allowing them to moderate without facing liability over the practice], which said you’ve got to police your platforms. And what was clear during the 2016 election and the succeeding events surrounding Facebook, is that technology companies used one part of what we envisioned, the shield, but really sat on their hands with respect to the sword, and wouldn’t police their platforms."

- Ron Wyden on Section 230

https://www.theverge.com/2018/7/24/17606974/oregon-senator-r...

I see a lot of people in this thread expressing the view that by moderating their content Facebook is becoming responsible for it. To the extent that's true under the law, it's not necessarily a great idea. Certainly the intent from a lawmaking perspective when some of the underlying framework was written is that this wouldn't be the case. You could moderate and remove bad actors from your platform without fearing legal persecution for it.

>The fact that college graduates get paid more seems adequately explained by the signalling model he presents. How else do you explain the big pay differences for college graduates vs people who dropped out early? They are bigger than you'd expect from just skill/knowledge gain.

Well, one thing to consider is that you can structure things so that you avoid all the hard classes until the end, and then leave without taking them. I found myself in this situation and had to 'boss rush' all the hard STEM classes at once, which wasn't fun and probably usually results in someone just dropping out.

Confirming this isn't what's happening might be one explanation for the sheepskin effect. (Of course, just because it might be doesn't mean it is, I think Occam's Razor favors Caplan here).

Your narrative is not actually evidence (even if I suspect you may in fact be right).

Yes but that's very obvious, the route just discussed is subtle and difficult to detect.

In that case it would make more sense to try and isolate the tasks comprising the last 20% and train on them separately, so that you get more practice.

People are exasperated with bad actors being allowed to set the common trust on fire with gasoline. For example, if this story were about a smaller dev they would probably be prosecuted for credit card fraud: https://news.ycombinator.com/item?id=18995823. Fines so far have not caused that to stop, so now the mob is asking for blood. Try to take it as an indicator of how desperate and frustrated people are, rather than a fetish.

>Perhaps it might be better if younger programmers learned the old stuff instead of just badly reinventing the wheel every few years.

I think if you pick a concrete example of this phenomena (say, Java applets vs. WebAssembly) and you ask "so why didn't someone take Java Applets and update them, why do we need WebAssembly?", the answers to why this happens start to become more apparent. It's not so much that Java applets were good and then we decided they were unfashionable, as that Java applets were always kind of ugly and we eventually stopped tolerating them.

For examples from before say, 2000, say Turbo Pascal a lot of the answer is because the thing in question was a proprietary product so once the financially backed dev team stopped working on it users were forced to move on to something else. Other times it's because the thing was written for an 80's computer platform that no longer exists outside of emulation and retrocomputing collections. Sometimes it's that the graphical standards the original used were for hardware with very different capabilities and making the thing usefully work on a newer system would almost require a total rewrite anyway.

Even beyond all that, there's another problem: Software is fairly hard to do literature review for. If I want to know if a particular research idea has been done before, I can hop on Google Scholar and figure it out with a few hours of carefully constructed search queries. Doing the same thing for software is very difficult, especially because most products for the majority of the fields history were proprietary. As a consequence, we don't have our history available to analyze in any easily accessed form. The Internet Archive has been doing what they can to rectify this situation. (See: https://archive.org/details/BeyondCyberpunkMacintosh) Nonetheless, there are still serious problems in this area.

I'm a younger person (23) who shares your frustrations, but I don't think that you can really wag your finger at people when there are real barriers to what you're proposing.