skysight-inc/HackerNews huggingface dataset:
I have worked with some incredible engineers in my life in 5 different companies and several divisions within those companies. I have met but a handful of senior devs who had what, when I was greener, an innate or better yet sixth sense as to what/how things should be done. The rest are intermediate developers. While I would love to believe a 3yr. engineer could be "senior" I've never met one who has the indepth knowledge to play the role.

Also, many companies have created multi-tier systems: Jr. Eng, Software Engineer, Sr. Engineer, Lead Engineer, Principal Eng, and so on
Well, on a second look: cefpython currently requires the user to pass in a UI window. That's apparently quite easy
to do on windows using pywin32, but nevertheless -- It's maybe quite hefty -- one might as well use QT, then.
This was also pimped a couple of weeks ago — by the very same person ⌘ https://news.ycombinator.com/item?id=9710357

https://news.ycombinator.com/submitted?id=timeup
...for having from boyhood been accustomed to no employment, or discipline, they do nothing at all contrary to their inclination...

Now we see why the state had to subjugate them! b^)
OK, I appreciate your feedback.
Summarizing some of Michael O. Church's screeds on the topic (https://michaelochurch.wordpress.com), I would say that the value of fresh graduate developers comes mostly in how much they undervalue themselves, and therefore how much excess generated value can be "skimmed off" by the company.

A software consulting firm, after all, is usually a bunch of fresh grads headed by one "architect" with experience. Most of the work is done by, and most of the decisions are made by, the fresh grads, but the work is being billed at a rate that assumes the senior "figurehead" developer, and others like him, are doing the work. (This is also true in law, finance, advertising...)

Or, in other words: http://marginalrevolution.com/marginalrevolution/2012/02/rob...
The last I had heard he bought a house outside of Medford OR and was living, in his terms, "simply". My assumption was that he had walked away with enough money to buy a house outright where the taxes weren't outrageous and is just living on the residuals at a much more down to earth level.
experience is misspelled :)
Eric Foner on the past and present of white supremacy
Static Web Publishing for Front-End Developers
Increasing Variety on Pluto's Close Approach Hemisphere and a Dark Pole on Charon
See Motivated Stopping: http://lesswrong.com/lw/km/motivated_stopping_and_motivated_...
By the way, congratulations on the first HN Singapore thread that does not mention chewing gum!

This is why we can't have nice things.
Kleinigkeiten:

- your url-structure is confusing (www.timeup.io vs start and landing)

- write "use timeup.io now" instead of "try"; add try once money is involved

- add small titles to the 4 bullets-list on event entry; right now they are very confusing; there is also too much white-space on desktop browsers; perhaps left-align the event-entry form on larger screens

- Slot Length should have an effect on Timeframe so one can start at 8:30 for example

- Text liest sich oftmals zu Deutsch (zBsp: "timeup.io focuses on the finding of the best fitting...") oder ist Englisch inkorrekt (zBsp: "Shoot a message!" müsste "Shoot us a message!" sein)

Grüße nach München!
That's part of it, but I also find recent grads tend to be useless on the hard/fun parts of development, but great for the tedious crap. Sure, with a lot of supervision interns can fill the same tasks, but recent grads tend to stick around for much longer.

There is also a huge nebulous gap after that where cost and talent is not that closely connected. You can have two people with similar resumes where one is worth 200+$/hour and the other is barely better than an intern. Worse this can get very project specific. People that do great things for one project can bomb another that's superficially similar.

Recent grads may be of near universally low quality, but it's predictably bad.
As a shorter than average man often disillusioned reading hundreds of honest female online personals, what about sexual selection and cultural expectations of women in choosing a mate?
My thought exactly.

Sometimes it is just about pay grade and rewarding people with a title. I am not saying you should not speak your true mind to a SVP or ESVP, but you should expect that people with more prominent title have more authority and more say, because ultimately someone has to make a decision on yay or nay.

I feel finding a place where you can truly have impact even as a junior is incredibly important, if not, more than a title. People respect those who work hard, capable and honest, but title still matter.
I appreciate the correction. Edited the comment to reflect that. Weird how the field is fragmented enough that I can go through hundreds of INFOSEC papers (ACM, IEEE, conferences) without seeing hardly anything on honeynets then you see a flood of them in the sources you read. I expect a certain amount of this due to specialization but I think INFOSEC innovation is way too scattered compared to some fields. People end up missing key findings.

It's why I keep toying with the idea of a unified resource for INFOSEC professionals of all these fields. Collection of papers by category, tools, wikis, forum, and so on. Free or cheap to avoid exclusion the way ACM/IEEE/Springer end up causing. The wisdom of our field would be passed down more easily, all stuff in one category would be there with authors maybe discussing it, and different types of researchers would have higher chance of bumping into each other for cross-disciplinary advances. Pretty idealist, I know, but would be great if pulled off.

Epstein at NSF liked the idea but thought you'd need a ton of buy-in from Universities & private parties ahead of time. Haven't solved that one yet...
Winner is Go by a large margin. 6.5X more demand

http://jobdensity.com/QueryGrid.aspx?q=906&t=node.js&qt=6/27...

http://www.jobdensity.com/QueryGrid.aspx?q=907&t=go&qt=6/27/...
No problem, that for your kind comment. And feel free to update your post :)
The article lost me on paragraph 1: "...There is a much higher need for developers than can be satisfied by new developers coming into the field. This is a problem that has existed for years, and it is getting worse as time goes on...
We have a serious shortage of talent to meet the demand..."

Basic economics dictates that there is only a shortage if prices are increasing, and they are not, certainly not relative to overall price increases.

Secondly, there are plenty of developers -- but like me they go into other job roles. The reality is that a developer salary does not support a family in developer-job-rich areas. You might find junior developers because they are willing to share apartments or live in shacks, but once you start speaking about senior developers you are often also talking about someone married, possibly with children.

The problem is certainly not a lack of developers but a lack of hiring managers paying a living wage for that stage of someone's life.

Cant find senior developers? Quick trick -- raise the salary and see them pour in for interviews!
My former employer's titles went Engineer, Senior Engineer, Principal Engineer, Senior Principal Engineer, Fellow, Senior Fellow, Principal Fellow. Each "Engineer" title had two levels, and one needed to be in each level at least two years in order to advance, so a "Senior" needed a minimum of four years. In practice, you needed more unless you had an advanced degree.
Mixing Ansible Roles and Tasks
Good luck guys :)
No, I was talking about general schemes. All of the stupid assumptions are yours.
Wow, this could get sketchy like those mail-order brides from Asia or Eastern Europe if people were to abuse this
I would, but edits are time-limited on HN.
Science is not engineering. In engineering, we understand the problem domain enough to make everything reproducible, the governing principles are well enough understood that reasoning from first principles can usually come up with answers.

In contrast, in science, we are trying to discover those first principles. So if something doesn't replicate in another lab, we have a responsibility to check it out, but that doesn't mean that the scientist has to discover all the first principles before making a publication! The non-replication could be due to new, solid, first principles, and the assumption that it should be "reproducible" exactly from the English words on a sheet of paper are a faulty assumption.

If you want to be able to pick up the scientific literature and read it like a science text book, you're doing it wrong. That is not the purpose of publishing papers.
How does it work, really? Do you provide a plausible-looking virtualized fake enterprise network that will look like a real thing to outsiders? Or do you put honeypot servers alongside other production servers, running whatever applications are really being used by the company? Do you intend to protect against inside threats as well?
Hmm, but the Flynn effect is endogenous, meaning that while IQs may be higher, IQ scores don't rise throughout the persons's life to suggest exogenous factors, only over many generations of testing. So the quote about the physicist is true, but in future generations, assuming the Flynn Effect holds, we may have more people with the cognitive capacity to become physicists.
I actually thought a bit about that after posting. I would be more inclined to use a web based admin interface today, than just a few years ago; the TLS stack is not as bad as it was; we've come further wrt ciphers - and the web servers themselves have seen (more) hardening.

The thing is; I already use ssh. Adding another network service doubles the attack surface.

Then there's the ux problem for browsers and certs. Using certs with ssh is complicated enough (it's still on my todo-list, I use/require keys - but key management is not trivial for more than a handful of servers).

Ssh also finally have easy/proper 2fa support now: setting up totp+keys is quite trivial. Add password+totp for sudo locally and you have half-decent ux and security.

And while ssh has had some security issues, it's been a while since the last big one. In contrast with all the things that go wrong with web apps (xss, session-hijack etc).

All that aside, certs+2fa (and the ability to disable pw auth) goes a long way.
Hello Dan,
thank you for your answer! You're right there is still a need in optimizing the landing page. In fact the whole page was developed for a customer development course at university. So I really appreciate feedback on the psychological parts of increasing the "customer" base!
Beste Grüße aus München :)
> A senior developer will understand that this job is to provide solutions to problems, not write code. Because of that, a senior developer will always think of what they are doing in terms of how much value it brings to their organization and their clients vs how much effort they are putting in.

Nicely put. Good read.
I think main advantage here is not the speed but power consumption and ease of deployment (small form factor etc.). Also as mentioned in the article, they can do a lot of customization there. Such as custom design floating point units, lookup tables for sigmoid calculations etc.
Probably need to discuss how to isolate the component's Javascript.

Web component's JavaScript exists in the global scope so it can overwrite and be overwritten by scripts external to the component.

This is actually a major issue in my opinion. You can isolate your code to some extent using an IIFE but if you want to include 3rd party libraries that quickly becomes very hard to do. 3rd party libraries will also often directly modify the window object making any isolation attempts ineffective.
> If an engineer builds the worlds greatest new engine

There is more to science than advanced product development. Conflating the two is wrong-headed.

> but says "unfortunately it'll only run in my lab, no one else is competent enough to run it or build a copy" then what good is it to society?

It's fantastically good to society. A company interested in monetizing the research could provide that researcher with a multi-year sabbatical to come to their company and turn is Research into a Product.

Incidentally, that happens. It's also not unheard of for phd students to carry an adviser's idea forward toward application in the context of a permanent position at a relevant company.

> almost nobody else can duplicate

There's a difference between not being able to duplicate, and duplication being expensive.

> and it is therefore impossible to determine the veracity of their claims

Again, reproducibility should focus on the veracity of the claims, not the economics of reproducing them. Nothing is wrong with calling for better reproducibility. The problem is in expecting to get it for free, and assuming that it's always appropriate at every stage of research.

Investment in reproducibility should be in proportion to the degree of trust the scientific community puts in the claim, and it is absolutely reasonable for that investment to grow over time. But, don't kid yourself, it's an investment. And society would have to be stupid to invest enormous amounts of money into ensuring every single scientific paper ever published is held to an extremely strong standard for reproducibility.

> Isn't the onus on the researchers to focus experiments that are also reproducible by non-supergeniuses?

If by "super genius" you mean "someone else who does research in the same or a closely related field", then Hell. No. The onus on the scientists is to focus on experiments that push science forward in service of mankind.

Sometimes this means helping mega-corps figure out how to reliably reproduce your research without expert help and thereby increase profit by decreasing required investment. Sometimes this means focusing on discovery.
Ask HN: Participating in Tech conferences in Bay Area
Hi
I am a developer and really want to attend tech conference in Bay Area. Is there any funded scholarships which let developers attend events.

If you have attend any conference like Google I/O, Apple event do share you experience.

Thanks
https://translate.google.com/translate?hl=&sl=nl&tl=en&u=htt... (Google hasn't figured out yet when to translate an idiomatic term literally yet. That makes for a funny translation. See for example the subscript of the first photo)
Plod – A simple distributed web crawler in Go
Interesting...but could it be that Go is a super generic term? It's surprising that Go has more jobs than Python, for example:

http://www.jobdensity.com/QueryGrid.aspx?q=912&t=Python&qt=6...
Ahh, good point, no problem. <3
Linux has lots of merged patches though. That they don't have merged prs isn't surprising as they handle patches via email.
For me it's not the best approach with server/html.

By design too many points of failure for desktop app, too many wrappers.
The gist is clear: it works, it's easier and faster to do, but ...
agree, I had some doubts but is crystal clear now...
It’s going to keep changing, again
That's pretty badass. It would be a pain to try to work with now given much of it is strange to a modern user or admin. Cool that they built it. My takeaway from Burrough's is to do much interface protection at compile time, pointers + code protection in memory during runtime, bounds-checking on arrays, simplified assembler, dedicated I/O processor/programs, and good recovery of failed components. That plus what we know from other systems would make for quite a resilient system combined with a RISC processor such as Gaisler's Leon SPARC I.P. or the Rocket RISC-V CPU.
This post seems imbued with the philosophy that programming is fundamentally a trade skill, with a skills development path that is roughly equivalent to becoming a master carpenter or mechanic (which are significant accomplishments, but that's a separate topic).

One cannot become a cardiothoracic surgeon simply by being a doctor for 10+ years, or even by taking part in thousands of open heart procedures as an anesthesiologist.

Unfortunately for our profession, looking for a 'solid CS background' or an active github repo haven't proven universally effective as methods for identifying self-sufficient people capable of building reliable systems that solve complex problems. Those people are more easily distinguished by being in exceedingly comfortable positions already, or enjoying early retirement.
noob/off-topic: I've seen people use the word DOM multiple times and I don't have an idea of what they mean.

- I know from past that DOM vs SAX were two ways to read/write XML. Not sure if that is related.

- Recently I came across a reading that said a website is four things (or a web is made of four key technologies, or something like that): HTML, CSS, JS, and DOM. I know the first three are frontend but what does it mean to put DOM at the same level as the others?

- Does DOM in this context have anything to do with, so to speak, schema or format of interchange between webservices?

- It might make things more confusing to consider that browsers like Firefox are built using web-technologies, instead of native UI frameworks/libraries.

Care to comment anyone?

EDIT 1: found the HTML/CSS/JS/DOM reference: "HTML is Done" https://www.tbray.org/ongoing/When/201x/2015/06/05/End-of-HT... (HN discussion: https://news.ycombinator.com/item?id=9672520)
A senior developer is such when they know not just how and why (through experience), but can teach and explain to someone else, and have them understand to a reasonable degree.
I can recall in my early days, a more experienced developer who was paired up with me and another junior colleague, that her job was not necessarily to try and teach us about all possible experience and gained knowledge - we would both have to gain our own badges and scars, and learn from the experiences. She would be there to direct generally, help us back onto the main path if we wandered too far, help with some of the larger leaps and jumps when we were ready, and to of course point out obvious pitfalls and perhaps some less obvious ones too.
It's something that I noticed too. I had what I think was a pretty unique opportunity to be involved in project(s) from the very beginning to the 'end' (i.e. support phase) from my early working days - since my very first year. That allowed me to fully experience writing really underengineered code, then subsequently vastly overengineered, then a chance to clean it up - all while having no one else to blame but myself for any shortcomings. I'd like to think it taught me a lot and of all the rules-of-the-thumb and catchy acronyms, it seems like KISS and YAGNI sank in the most.

Also, a lot of the points the article makes about the senior engineer seem to be about a 'business sense' - what the actual business problems you're solving are and how your solutions influence the business itself. I really like to know all that - in fact, those are my starter questions as a candidate in any job interview - but I don't know if it's just an innate trait that some people have, if it's something you pick up, or maybe both to a degree...?

And I don't consider myself a senior engineer, not by a long shot...
Traits on Generics
"The sad fact is that the vast majority of not only senior developers, but team leaders are in fact, intermediate devs. Most do not realize this, and have the best intentions, but have simply never worked with anyone who is at a higher level."

This terrifies me every day. Any ideas how to solve this problem?
yea, thought of that. so now Go by 2.4X

http://www.jobdensity.com/QueryGrid.aspx?q=913&t=node.js%20p...

http://www.jobdensity.com/QueryGrid.aspx?q=914&t=go%20progra...
Why We Need WebAssembly: An Interview with Brendan Eich
The "seniority" titles don't really measure anything useful; that's why they don't really transfer between companies. A "senior engineer" might become a "lead engineer" or just an "engineer" at a different company—which means there's no objective measurement going on there.

I much prefer a guild-like system for measuring actual aptitude:

• apprentices know one thing well enough to do it (the average "Java developer");

• journeymen have a good picture of the field, know what "the best tool for the job" is in most cases (even if they don't know that tool), and have the meta-skill required to efficiently pick up a new language/framework/paradigm/whatever else in order to solve a problem that requires it;

• masters have enough experience to flinch away from bad design/architecture. They've been burned by every category of problem it's been possible to be burned by, such that they have a complete high-level picture of all the moment-to-moment considerations involved in "the art." They know what questions to ask about a proposed pull request to determine its quality. To get here, they've likely completed a major "masterpiece" work on their own, and maintained it under heavy use by others.

These aren't categories that match social standing, or seniority, or experience, per se. In fact, they don't even form a tight match to the kind of "skill" people look for in job ads; you can become a "master" at 15 if you accidentally build something really popular, even though you still need a cheat sheet to remind you what's in your language's stdlib.

But these categories are able to be objectively fit to people (it's pretty clear in which one a particular person sits); they can be carried between organizations with no loss of meaning; each category is a strict superset of the skills of the former; and they tell you something that's very useful to know.

Interestingly, it would be fully possible to set up an educational curriculum that could make every graduate a "master" by the criteria above. Right now, though, colleges only make apprentices. Companies sort of make journeymen, though rarely. And no part of "the system" has any chance of making someone into a master; they have to pursue such a trial on their own.
So two questions, really. First, given We generate one because our decoys are real machines and nothing should run on them except for what we put on them., won't that machine look a little different from the outside, that is, the next machine over in the horizontal network than all the other machines? And thus the attacker would be suspicious?

Secondly, who is to say that the attacking army doesn't have a lab simulating an enterprise environment with one or two of your installs there, learning how to detect/avoid/silently compromise them?
It'll be interesting to c how the radically overhauled module management in Perl 6 pans out.

(They're making sure that installation is practical. For example, NativeCall, for calling C libs, does not require a C compiler.)

> Also devs are used to having named arguments for their functions. Not supporting that is just silly.

The latest Perl 5s have this ("signatures").

Signatures are a central element of Perl 6. (They are way more powerful than in Perl 5, even the latest.)

> it's difficult to google things like $/, $", $% and $_ when you're confused.

Yes.

Fwiw Perl 6 only keeps three of these oddly named variables (removing dozens of others) and they are simple in practice:

name concept formally means the current/latest

$_ it topic (Nil or any value/object)
$! oh noes! error (Nil or unthrown exception)
$/ /regex/ match (Nil or parse tree)
I experimented with this by using python-shell [1], but it in the end it just felt too hacky, and it decided it was best to embrace js instead.

[1] https://github.com/extrabacon/python-shell
As cool as this is, it's actually been posted a few times, including this post (https://news.ycombinator.com/item?id=9762054) four days ago.
I'm simultaneously honored to have been flamed by the lead of a project I'm interested in, and saddened to learn that the best source of attacks against us will be words our project leaders used first.

At the same time, if we're the ones generating our own bad press, we at least control the overall narrative. I guess that's a net win.
Man, I like Tkinter. (And you can make it not-ugly with just a little bit of work these days.) ;-)