jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
It's interesting how one of the first things they mention is that you won't be expected to code. That may be true in some orgs but not others.

In my org team leads are the managers as well as the technical leads and wear the Scrum Master hat too.

Most of the other advice is still sane if you ask me but personally I do like oue mix of coding and other challenges. Keeps things interesting and you don't get too bored of one side of things. Also, it's much easier to see if one of your 'stars' is actually one or is just the loudest. If you don't really know the code base yourself that can be a little harder to figure out and message. And you don't have to work on the large, important critical path user stories either. Just fixing bugs from time to time is enough to learn their tools, their conventions, keep current, be seen as competent by them (helps tremendously with being listened to in my experience) and still have time to actually do your other jobs properly, because coding comes last but not least.
Sure, definitely. I have sold wine in my early adulthood and clients really cared about such things and it is good to have some vocabulary to describe and distinguish different wines.

Just what I think this study shows is that you may get stuck in this learned framework and try to apply it based on the appearance of the wine (red|white) and you will bias your judgement based on this.

This study setup is clearly adversarial but then again it pointed out a clear weakness in current state of oenology - to understand the wine better, you must eliminate biases.
Out here in the Midwest, my quarter acre plot didn't cost a whole lot - but the house itself cost a fortune in materials and labor. Maybe I wouldn't have needed a 30 year mortgage if the place could have been 3D printed with novel materials.

I'd still need a job to pay my property taxes, but wouldn't have to bust my ass as much.
I don't deny your right to challenge, but tight now I can't give an example. I've just gone through months of my posts looking for one particular post that might clarify but I can't find it. Not being able to search your own comments is frustrating. I'll have a muse overnight.

sorry!

Found it (thanks google): https://news.ycombinator.com/item?id=20591621 Simplicity was staring me in the face, it took weeks to find it.
I stand corrected. Thanks for the info. I came to know about the site after that app rejection. Thought the site came into light after that issue. My bad.
Anyone know how to get rid of the background image without having to sign in?
I doubt Mozilla will want to review all add-ons. And if review isn't required for a signature, Microsoft can just get theirs signed. Moreover, why wouldn't the MS add-on pass review? If it didn't, would that make Firefox the new iPhone?
I'm always happy to get free performance improvements, so it looks like a job well done. However, they note that "It’s not very useful to benchmark Phusion Passenger performance using a Rails application because most of the time is spent in Rails and the application itself." - which I would take to mean that in real world usage, this improvement really isn't going to buy me much. Still, nice work, and thank you!
You left out the ending to that episode.

Soon after Moe's becomes popular because of the 'Flaming Homer' drink, Homer tells everyone about the drink's secret ingredient (cough syrup.) Nearly all restaurants in Springfield start serving 'Flaming Homers' and Moe's suddenly isn't the hot spot anymore.

Here's hoping all the "Homers" out there leaving the App Store take their knowledge elsewhere and bring some openness to mobile development.
Any update on a 1.9.x version of passenger?
And having too many options is what is killing these companies compared to Apple. Quite frankly people don't care that you have XYZ mobo processor or graphics card inside. They just want the dam thing to work.

"Tyranny of Choice" at its best.
I think Feynman gave him HIGHLY ACCURATE advice, but you have to dig deeper to understand.

Although Wolfram has done quite well for himself, this is beside the point.

You might want to read both sides of the conversation:

http://elzr.com/posts/wolfram-feynman

and then read this article:

http://www.wired.com/wired/archive/10.06/wolfram_pr.html

in particular, starting here:

"in the spring of 1992, he became, in his own words, a "recluse."

So, he figured out a way to get away from the administration and concentrate on the science.

I suspect that Feynman's advice probably helped Wolfram steer a clear course through all this.
"you will have to decide between using Flash with a 99.6% market penetration or HTML5 with roughly less then 40% of users browsers"

Adobe keep rolling out the '99 percent' argument, and it is false. This argument is essentially 'hey look, everybody is already running our proprietary virtual machine so there is no need for a standards based solution!'. If we all thought like that, there would never be any progress.

HTML5 is not a flash replacement, but HTML5 + CSS3 + Canvas + Javascript + SVG + new DOM etc. sure is

When most articles refer to HTML5, they are often refering to the combination of new technologies, rather than the markup standard itself (ie. what was initially 'Web Applications 1.0' from WHATWG).
My father is deafly afraid of computers. However he is completely obsessed with baseball stats. In his office there are 6 book shelves as tall as the room. Each shelf is filled with books with thousands of pages containing baseball stats. a few of them are literally from the 1800's (apparently they're worth a lot, his will currently has them being donated to some historical baseball society) he's been a member of SABR for as long as I can remember.

Its rather funny though, he spends hours every day sitting at a desk with paper and a pen calculating matrices of stats. I imagine what has taken him years to write could have probably been completed by a computer in minutes.
This was really funny, thanks! As I finished reading, I realized how ridiculously much I've had to learn over the past ~15 years as a web dev.

Things have changed so much on so many levels. For example, just over the past week, I've had to set up a server, a CI tool, install and configure some databases, built an app using a bunch of different languages, frameworks and whatnot, learn a new language, etc.

The reason I'm saying this is because the number of skills I've acquired so far would have seemed absolutely daunting years ago. A lot of these skills are of course perishable, but the sheer number of concepts you have to keep in mind at any one time when working in web dev is ridiculous (though interesting for the most part).[1]

Over the years I've spoken to a lot of kids who wanted to learn web development, and I'm never quite sure what to say. On one hand I really want them to see how cool it can be, on the other hand I'm always concerned I might scare them when I explain how you achieve cool things.

I love what I do, but if you want to properly understand the tools you're using, web dev isn't for the faint of heart these days.

[1] I'm not saying this doesn't apply to other fields, web dev just happens to be the one I know the best.
Nope, a network engineer is way different.

Much closer would be writing boot loaders and compilers.
As a senior at Yale right now, and seeing what most of my fellow students are going into next year, the Ivy League is great at pumping out over paid worker bees. See here http://yaledailynews.com/blog/2012/02/13/finance-continues-t... for the numbers going into finance (~20%) and just anecdotally I would guess there are only slightly less going into consulting. Finally, there are a not insignificant number (maybe 10%) doing some sort of engineering.
ATS had macros: http://ats-lang.sourceforge.net/htdocs-old/TUTORIAL/contents...

I'm not sure if these made it into ATS2 though.
> The US has an extremely inefficient government fiscally.

I saw this old blog post recently, supporting your assertion: https://pedestrianobservations.wordpress.com/2011/05/16/us-r...

Basically, underground rail construction in US costs much more per kilometer than in other countries, and people in the comment section claim that the same holds true for other types of infrastructure construction, like bridges and highways.
1. No. Businesses (by federal law), aren't even required to accept dollars now.

2. Yes, but would you use Honest Achmed's Used Cars and Dollars?

3. (Private) Ratings Agencies would rate currencies and maybe each other. The market picks the winner based on trust, convenience, or whatever else it cares about.

In practice, I'd expect an 80/20 rule. Two currencies would make up 80% of all transactions in a given region, with a rather large tail (gold/silver/basket of commodities backing, fixed exchange rates, etc). Multiple currencies is nearly unworkable with paper money, but quite trivial with digital paper money.
I did "Agile" for 1.5yrs and it was the least agile team I've been on so far. We never had a product owner (we were all expected to understand the user's needs enough to serve as "product owners"). We had devs and a manager, and a "scrum master"/team lead, who was one of the devs and reported directly to the manager. Our scrums were 30m+ long because the manager wanted to know every little detail, and there would be a lot of back-and-forth, most of which would be irrelevant to any given team member. Complexity poker involved guessing what number the manager wanted you to pick, and sprint reviews were two-day experiences in self-flagellation.

Not that all of this would have magically gone away if we weren't an "Agile" team but it did contribute to the problem. "Proper" Agile just doesn't fit well with the way most companies want to run their teams. So managers take Agile and make their own personal tweaks to it. Since their brand of Agile has 80% the same rules to what they read in the book, they expect to get 80-100% of the benefits of Agile. Any questioning of the actual results of this system is heresy, since Agile is a well-established management method used by many successful companies.

If that manager had picked up a management system that worked within the company's framework without making so many changes, or if there wasn't so much Agile-worship in the industry that an "Agile" setup was politically unquestionable, the situation would have been a lot easier to fix. As it is, it wasn't until our team completely collapsed that the company reassigned half of that manager's responsibilities to a new department, and the manager decided to retweak their personal brand of "Agile". Even that is probably too little too late; more and more projects are being moved from that dep't into others, to the point where I'm wondering what the devs there will actually have left to do.

So yeah. I'm very skeptical of anything calling itself "Agile", because it's such a nightmare when done wrong, and I'd bet dollars to donuts there are more places doing it wrong than right.
This is so true.

I remember learning Java from a book, and many of my lightbulb moments about programming came from reading code, not writing it.
Is it not? https://en.wikipedia.org/wiki/Curry_tree
If I remember correctly (grew up in Connecticut, drove through MA a lot), I-90 does not go directly through Springfield, but, rather, passes by a couple miles to the north.
Hehe. Subtle.
Conversely, most every multi-party hangout I have had has gone perfectly. And I have them multiple times every day.
Many companies standardize on a couple languages. For companies like that, Go and Rust might occupy the same sphere of influence.
What part of it didn't you agree with and why?
The unfortunate issue with components is that they're kind of like wysiwygs or bootstraps. They save a small amount of trouble in the beginning, but always bite you in the end.

That being said, if it's all in a single file, you can copy and paste that file into your project and then modify the thing, unless the single file is itself a bundle.

At my last company we tried to make a button component. But then we wanted to be able to change url with it. But then if you ctrl-click, it should open in a new tab. And then there were certain styles of button, with mixed and matched shapes.

Nowadays, I see components as single use, or specific to a project. And for anything that's more about a visual than a function (ie buttons), just use css classes and implement the underlying Elements from scratch.

Point being, everyone wishes they could model the perfect abstraction of a component, but then you start adding config to make it do everything until it's basically its own miniature programming language (with worse docs).
I thought that article last week was much more interesting.

/Techsupport side note. I have a Windows laptop, and for the life of it the client will not connect to the service. How do I troubleshoot this thing? Its almost too simple. Are there logs? https://i.imgur.com/QRLkQl1.png

/And is there any way to get to test the magic dns? Will there be better ways to set up relay nodes, and then SEE the design of the network? Can I set up a relay node on Windows, and only for specific IP addresses instead of entire subnets?

/On the topic of "security within the lan is just a nuisance" I do appreciate this being more of a unix philosophy like single tool than kitchen sink. I do think there would be a market for a companion piece of cloud software that acts as a firewall orchestrator between devices, surfaces logs, allows you to block or allow specific connections between specific devices, and to visualize the activity of the mesh. It would be beneficial to be able to super quickly design a "all the field ipads can get to the server, but not each other" type network, while at the same time giving pcs more LAN like access, or being able to designate "edge/guests/clients" that can only connect to "servers." The two types of networks shouldnt need to be mutually exclusive.

/On the topic of other markets and use cases, and maybe this isnt what Tailscale ever wants to be, I think there is a huge opportunity for a pure software client Wireguard SD-WAN a la Velocloud. If I have two ISPs plugged into my network, let me define BOTH gateways as acceptable places for traffic outflow, and build simultaneous tunnels out both. Maybe load balance traffic between them, watch for packet loss, congestion, jitter, and correct accordingly. That extra redundancy of being able to lose a link and keep the path would be extraordinary.
Here's an example of single-file Web Component. Markup (JSX syntax with embedded JS expressions), CSS and JS are in one file:

https://github.com/wisercoder/uibuilder/blob/master/WebCompo...

All you need is this tiny 250-line lib:
https://github.com/wisercoder/uibuilder
Maybe, but with all the people stuck at home, it really should be on everyone's Netflix to-watch list. Fantastic movie.

Some other good picks relevant for these times:
The Andromeda Strain (1971)
Outbreak (1995)
Contagion (2011)
Invasion of the Body Snatchers (1956 and 1978 versions)
28 Days Later (2002)
We will pull together against CoVID, and anyone who takes this chance for criminal gains. For the readers who work in IT and cybersecurity, your actions
now will save many lives. Keep calm and carry on.
The URL of this submission is the same as the one of the submission you linked; it's strange that my submission made it through the dupe filter.

Thanks for the link, crocowhile; pg's comment there is really that more interesting to read
I think you've misunderstood. This does not take away any of those issues. With this setup, you can write (+ 1 2 3) or +(1 2 3) or (1 + 2 + 3) and they would all translate into (+ 1 2 3). You can treat any of them as a list. You can still parse, transform, do anything with it. There is no loss of functionality here. Think of it as a macro that aliases "plus" to +. There is no difference between (plus 1 2 3) and (+ 1 2 3) in a macro defined in this way. They are S-expressions under an invisibility cloak. But they're still S-expressions within.
This would vary from site to site, and if the HTML of one changes, the "collector" will need to be updated too.

It's a ton of work even for a few site, making it generic: yeah, you could do that, but then you'd have to provide unorganised data as a result, which wouldn't be useful at all.
It's painless and fast so why shouldn't it be awesome?
The #appengine channel on Freenode is a pretty good place to ask. There are oftentimes people from Google who are working on GAE and can help you out.

Worked for me several times.
Digest & ligate isn't even the worst problem. Back in the day (2006) the quality control and standardization of bricks was dreadful, I haven't seen evidence that it's improved substantially since then. Polymerases per second (POPs), the measure of brick efficiency, seems like a bit of a pipe dream -- I'm yet to be convinced that it can survive brick composition.

Did you do iGEM? Back in the day I started the iGEM team at Brown. We couldn't scum a PCR machine off anyone so we spent the summer doing minipreps. A few weeks before the jamboree, we refined our models a bit and showed that the parameter space in which our project would function was so narrow that it would probably never work. Oops!
Have a thought out product and a way to sell/distribute that product. Pre-sell your product, possibly with wireframes, hundreds of interviews with potential customers/users - prove that there is a market, you understand the market, have the knowledge to design the product, and that you can bring the product to market.

If you can't do that, you add no value. If you can, you should have no trouble finding engineers.

More:
This is actually a bone of contention for a lot of engineers. The attitude of many "business founders" is that they have great business sense, some "rolodex," "innovative ideas," maybe even an MBA. Their approach is that they bring these skills, while a technical cofounder brings the "other half" - technical skills. The flaw in this logic is that engineers are really smart - they also have almost everything you have - and can quickly learn what they don't know. That is - unless your execution capabilities are deep and proven.
Chrome explicitly stopped supporting void syntax on the script tag to encourage people to use </script> so IE wouldn't die when it saw a <script />.
Not sure I agree on Pl/1 I found it easy to work with.

I used to work with a a DBA whose first boss was Dijkstra
I hope you've written this up somewhere for publication. You've solved the "junk DNA" issue with computer science.

Best post on HN ever.
Google has a weird state between logged in and logged out. I believe it happens when your session has expired, but the cookies are still being sent. You're constantly asked to login again to access completely open pages.
GPS and transport data.
*TheyTube

Grammar.
Corporations are not good or evil. They're amoral.

Google only appears to be acting in bad faith because they follow the (IMO dangerous) ideology that because humans don't scale everything needs to be automated. They are essentially doing the epitome of "one size fits all", especially in how they deal with customers / business partners.

Yes, it's tone deaf, but it has nothing to do with being evil. The only reason this is at all a problem is that they're successful enough that it works.
The reverse is true, too: Want better performance than people of the same age? Have had more training than them.

I suspect this applies especially to language or logic related tasks.

We will likely never find out, variance seems to be extremely high, while the actual differences are very low.
Day job: Web site user sessions and offline retail sales data.

Side project: Poll responses on http://www.correlated.org
In search engine companies, we sort out cookies every day.
But when you try to imagine how it could be split up there are all kinds of problems. e.g., obviously CA + NY makes sense plus some large cities(e.g., Chicago). It all seems untenable w/o excessive relocation a la Stalin.

Truly splitting up the USA would require a war and that's more trouble than its worth in most peoples' opinions: I've kinda grown fond of letting my neighbor's kid cut the lawn for $25, even though he is a Democrat.

Now, OTOH, spinning off a state or two is within reach: e.g., giving CA and NY their independence would be fine with me. But then that's just me!8-))
A lot of us have no choice when at work.
Anyone else struck by what a bad speaker he is?
90% of the code you write at a startup is exploratory. It's written to learn something about your customers. If you break it, you typically don't incur a much of a penalty in terms of cost / time.

Testing every bit of code does cause overhead. I find it takes more than twice as long to write code when you test it. This overheard puts a big drag on the speed at which you can move, which can kill a startup.

For these reasons, I only test code that's proven its long term value.
The great point made in the README is that we can't generate feature expressions. With feature macros we can have macros that generate cross-platform code. That's big in my mind.

That hasn't been a problem with reader macros in the past since you don't need to generate `#(...)` if you have `(fn [] ...)`.
I've read fairly convincing arguments that we don't know how to land on Mars, either. Problems of thin atmosphere, difficulties in aereobraking, etc. http://www.universetoday.com/25438/why-cant-we-land-on-mars/

Currently the method that's worked best is to bounce down a sturdy probe on giant balloons, and now NASA is trying a quite rube-goldberg lander that hangs below its retrorockets. Still very much in the experimenting phase.
I like this. "The only weapons we have are simplicity and convention." Well said. I think we need to espouse a new software paradigm: DFS-oriented programming. (Dead F*ing Simple-oriented programming.)
Following are the counterpoints to their argument:

1. decreasing ROI on a college degree:
They are confusing between supply and demand.
While it is possible in future that a college degree will no longer provide an edge over High-School diploma, yet this might lead to even more intense competition for top schools. They cite Law schools as an example, however there isn't a uniform decrease in enrollment. In fact a bad job market means that you need to go to even better/reputed university than before. Also it does not means that alternate signaling mechanism is going to alleviate this problem.

The issue is the demand, assuming that in future the number of jobs available for college graduates decrease. This wont help alternative credential providing mechanisms. The reason people are hiring via git hub and stack overflow, is because there is an excess demand and low supply. If anything a bad job market will only lead to more competition for top universities.

2. MIT open course ware/ ITunes University etc. : While these websites make it easier for you to get access to the knowledge, yet they dont provide you other things which are needed, such as access to labs, examination etc.

3. Github / Stackoverflow :

Systems such as Github and Stackoverflow tend to have Pareto distribution i.e. top 20% have 80% contribution/reputation. Even if you are building a credentialing system, it needs to have a distribution similar to the grade curve used in colleges. Also at the same time, you must make sure that there is "some" protection of academic integrity.
Would be nice if they gave actual percentages in place of the "x% more likely". Not particularly useful if I don't know the baseline.
This is Dave from Bump. This was a bug that has now been fixed in version 2.0.1.
In the article I improperly used "availability zones" to mean spanning both the AWS AZ construct and the AWS region construct. My point was specifically that by building your app to either function in US East, CA, Ireland, Singapore, and Tokyo or to fail over to one of those locations, you can avoid a situation where you've put all your eggs in one basket.