skysight-inc/HackerNews huggingface dataset:
You write an acceptance procedure into your MSAs. Pro-tip from Thomas: write the MSA such that the client gets two weeks of business days from delivery to object in writing to the deliverables or "the deliverables shall be deemed accepted." You don't owe clients anything after the acceptance period.

Should it fit with your desires and your clients' needs, you can sell maintenance on a retainer arrangement, which is use-it-or-lose-it access to you at a defined price which is a modest discount to your prevailing rates. If clients do not have an active retainer agreement with you, maintenance projects are entirely new projects, with a new SoW, at your current rate, subject to your current availability.

How this looks in practice: if I'm selling projects at $20k per week, the initial SoW offers 2 weeks at $20k plus two days a month of availability at $7k per month, with those days covering bug fixes, incident response, and such minor tweaks or adjustments as the client may require. In the event the client doesn't purchase maintenance, and the app goes down, then I'll try to slot them in for another 2 weeks at $20k each, but I can't make any promises.

You know the Chris Rock monologue about steak? When you go to a restaraunt with money in your hand and ask for steak, you get steak. Then you go home... and the restaraunt does not owe you more steak. Past clients are wonderful people who you may choose to do business with again, but you are not a free source of steak for them.
Darpa Is Developing Human Bio-Factories to Brew Lifesaving Vaccines
They're medians specifically. The graph is a visual representation of this data: http://www.bls.gov/cps/cpsaat39.htm The raw data isn't made publicly available, so boxplots aren't possible, but that'd be really cool!
Is it sexism, or is it women not wanting to promote due to external factors? Is it women not asking for raises as often as men? There is a lot of missing data here.
There's a lot of work besides performance to get right in a transport protocol though. Just getting the retransmission working like you want is a small part of the job.

WebRTC went for UDP-encapsulated SCTP in order to get a transport without HOL blocking. I'd look into that or an existing UDP game net transport (like Enet) first.
> That still demonstrates there's a significant problem.

Of course, but it's a different problem with a different solution. Isn't that important to know?
As I understand azth's objection, it basically means "This data has been stripped of all context that could make it meaningful". Which is to say it's a shocking, but ultimately useless graph.

You can say there's no way to read it as indicating things should stay the way they are. I believe azth's point is that there's no way to read it as saying anything coherent at all.

(EDIT: Typo.)
I have only glossed over the paper (yet), but this raises some thoughts on C in general. Why/Where/How we use it. I could distinguish 5 distinct use cases for C:

1. Legacy code
2. Shared (closed) code
3. Zero runtime dependency code
4. Hardware control
5. Resource limitations

This could be a good thing for (1.) - rewriting a project (most) in a safe language is just infeasible, yet this offers some guarantees/protection basically for free. Even if a tool (any tool) catches fire all over the place on first run because of a bug (in app code) it's still a good thing.

Sometimes we want to share some functionality (library), yet stay closed source. Or have an ability to take a file, drop it on a remote machine and expect it to run. This is what native binaries with a stable API are for. Yet calling foreign function in VM'd languages is often so awkward that we just end up reimplementing a lot of software instead of calling foreign function possibly shipped/managed at an OS level.

By hardware control I mean something like writing to 0xABAD1DEA and having data fly out of serial port or NIC change modes or something along those lines. I guess this is doable in managed languages by some built-in magic proxy object, but I'm not entirely sure if this does not start with "write hardware definition file and rebuild the VM". Just a thought.

5. is the basic idea why I'm attempting to discuss this. Small MCUs are still general purpose computers, just very limited, and are rather good litmus tests - is it possible to cram a Hello World into ATtiny with 512 bytes of memory? Is it possible to run something on baremetal ARM Cortex M3/4 (no FPU, MPU/MMU)? No? Then it is by no means "general purpose" and we should thoroughly discuss limitations imposed by the technology.

Programming is a discipline just too diverse for a single individual to grasp and too rarely we step outside our boxen to see the whole world.
> risk averse during interviews which accumulates over the years

Careful now, that may be a commonly held belief but is also wrong. There are far more reasons why the pay gap exists and you can't simply clump it all together and blame it on the stereotypical view that women have an innate inability to negotiate as well as men.
An Unlikely Cure Signals New Hope for Cancer
I mostly trust the BLS, but I don't necessarily trust every statistical conclusion someone can draw from running a script on BLS data.

Just as an example of how the numbers might not mean what they appear to: "lawyers" is near the middle of the chart, at around the 82% mark, while "legal occupations" is way at the bottom, around 57%. Does "legal occupations" include lawyers, or is it everything else in the law field aside from lawyers? If lawyers are included, then there's an obvious explanation for the large gap in legal occupations as a whole (namely, more male lawyers, and lawyers being higher-paid than assistants etc., dragging up the median compensation of males in the legal field); if they're not included, then there's a huge and unexplained gender discrepancy in pay among legal assistants etc.

These numbers have a very different meaning if they don't account for seniority, hours worked, or level of responsibility than if they do.
That could easily reflect different specialties within medicine compensated differently. As I understand it, pediatrics is dominated by women and surgery by men, and they don't pay equally for a variety of reasons. So a chart like this strips away that sort of context and shows you a shocking number.
Resume generated using your GitHub profile
"...O'Neill finds that when these factors are accounted for, the gender wage gap falls to approximately 97 cents on the dollar..."

http://www.ncpa.org/sub/dpd/?Article_ID=22058
This is a csrf attack -- it allows a site B (malicious) to exploit the trust relationship that exists between site A (running some Lucerne index behind a web service -- perhaps elastic search?) and a user C's web browser. Suppose site A allows logged in users to search an index -- user C is logged into A and user C visits site B while logged into A. Site B sends down JavaScript telling C's browser to send requests to site A -- because the user is logged into A, A sends back responses containing sensitive data. The JavaScript from B has no access to the data that was sent from A due to the single origin policy however it does have the ability to time how long the response took -- hence the mechanics of this attack.

As mentioned in the article, A can protect against this by requiring a csrf token to be included in all the requests sent to it (this is on top of the authentication/session cookie which establishes the trust relationship between A and C's browser. A csrf token is a random unguessable token that the server sends to C's browser in a form that cannot be accessed by B -- the JavaScript from A is expected to retrieve this token and send it along with future requests to A. The server A then needs to validate that any request from browser C contains the csrf token -- this allows A to distinguish between requests from browser C which were generated on behalf of code from A (should be allowed) and requests which were generated by browser C on behalf of code from some other domain (potentially malicious)
Some people believe that the secret to closing the gap is to ban salary negotiations: https://www.washingtonpost.com/posteverything/wp/2015/05/21/...
Others of John Simkin's (the author) essays strike me as somewhat fantastical, distinctly fringey, and exceptionally poorly sourced, e.g.,

"The Death of John F. Kennedy"
http://spartacus-educational.com/spartacus-blogURL17.html

Nor does Simkin's biography impress me much.
The gap in medicine is a microcosm of the wider gap: female physicians are disproportionately likely to end up in lower-paying specialties like pediatrics and family medicine.
Thanks, I should put in another "from my experience of 20 years of IT recruiting and mentoring women" to make it clear I'm not generalizing and what I'm talking about.

As a sidenote your comment about the ability of women to negotiate was not what I've said. There is a distinction between risk aversity and negotiation ability.

[Edit: Science is murky here, some studies claim to have found evidence, others claim that women are better negotiators. One I found interesting, can't find it, said women are better negotiators but do not start negotiating when it is not clear that they can, but man do negotiate salaries there too.]
> I think the graph speaks for itself.

That's never the case with data visualization. Explanation helps remove ambiguity, and the lack of explanation behind the data source is why there is an excessive amount of criticism in the HN comments.

Regardless, the graph does not certainly speak for itself. There's no obvious correlation between which professions have a better gender pay split than others. If you're trying to make the point that most professions pay women less than men, then you need to justify that. (And provide evidence that the chart represents "most professions.")
I'm just glad that there are still people (prmiarily nemo/francisco ballesteros/9front team/cat-v) hacking away at Plan9/Inferno/[nix/octopus/planb]/etc. In a world where corporate OS research is all but dead, it's definitely nice to see.
Thousands of women and girls disappear in Mexico every year
Wow if this were true even normalized for years of experience, education, hours worked, specialty, etc... (which it is not) seems the market would make it incredibly difficult for men to find a job https://www.youtube.com/watch?v=BDj_bN0L8XM
I don't see how that really helps. That just pushes it to being willing/unwilling to walk or having other offers in hand.

Which is to say it removes overt bargaining in favor of making it all covert. Is that really an improvement? I have some doubts.
When you read the source text, you can see that they have been fairly selective in the criteria in which they dismiss size of the wage gap. I would argue that the text shows the study was produced with a political leaning.
http://www.ncpa.org/pub/ba766
Personally, I've found that any time someone declares that a given visualization "speaks for itself" what they mean is that they want you to not ask questions about it. Occasionally this is justified, but more often it's a stunt of some sort.
There absolutely are ways to read the graph in a positive light.

If pay is heavily influenced by seniority, and a profession used to be sexist in its hiring practices but no longer is, then it follows that there'll be a significant gender pay gap until the older - mostly male - members of a profession die out.

Of course, there are many ways to read it negatively too. It's so devoid of information that it's just meaningless.
Of course!

First of all, we still haven't settled on a set of common abstractions and tools for the industry--so much reinvention happens that most projects can almost be considered bespoke every time. There is no common and simple way of estimating development time. There is no common and effective way of accrediting engineers. There is no commonly-understood legal liability and responsibility for software engineers. Frankly, any schmuck who decides to smoosh jQuery libraries together can claim to be just as much of an engineer as a high-end PhD or person with decades of experience--and the nature of the work is such that, quite frankly, that schmuck may deliver more value than their more experienced counterparts.

That said, the technology on which we are deploying has changed a great deal in the last forty years. Orders of magnitude increase in both processing speed, secondary storage, and memory have made a lot of formerly unthinkable approaches commonplace. The problems we face in terms of networked systems and security concerns are far different and more ubiquitous than they've ever been.

If the fundamentals of software engineering haven't changed, we shouldn't take ourselves seriously at all.
I have a feeling this graph is going to be reposted across various social medias with less context and incite more people spreading misinformation.
The data sourced here are full-time only workers, not part-time.

Would love to take a look at the souce code of that analysis, but I can't find it. Happen to know where I can get it?
They specifically said "one of many reasons" - I'm unsure what you're disagreeing with?
PRs welcome! The source code is here: https://github.com/statwonk/paygap
The comment had been updated, as the author mentioned.
If you're good enough to do so I think it's more cost-effective to forgo co-op, stack on the debt, and graduate earlier so you can earn full-time salary and begin vesting stock.
Yes, marathon runners. You are exactly on point.
How about women are more likely to change professions/jobs, so they don't get to the same levels of seniority as men. That might indicate they have a more varied and interesting life. Maybe that suits women better than men. So yea the graph says nothing.
That most occupations pay women less than men is a fact, the graph is just a reformulation of this table: http://www.bls.gov/cps/cpsaat39.htm
How to buy Bitcoin in Singapore
Facts do not absolve a data visualization from being potentially misleading.
I read an article a couple years back that pointed out a sudden increase in the gender pay gap among medical professionals -- specifically, fresh graduates from medical school, going in to the same specialties. Men and women had basically been at parity within each specialty in the early 2000s, and then over the course of the last decade or so, a massive gap appeared.

I read a followup paper shortly after, where they had investigated the details and found that a significant percentage of recently-graduated women had asked for reduced hours and fewer overnight shifts in exchange for lower pay, while many men had volunteered for those sorts of conditions in exchange for higher pay. The gap had actually appeared in response to trends in the lifestyle decisions of employees, rather than discrimination on the part of employers.
I suspect that all state universities in locations that have cheaper cost of living that the national average (Texas, for instance) are hampered by viewing the data in the way it is being shown.
Australian rules football and Gaelic Football are not the same thing although there used to be an international rules series every year between Ireland and Australia.
> [...] what value does Twitter have, other than a more restricted set of content? What about App.net? Twitter is in an even worse position than MySpace to fight off a disruptive competitor.

Did this article imply that App.net was about to kill Twitter since App.net was open?

Heh.
Near-Perfect Computer Security May Be Surprisingly Close
At first glance, parameter tuple unpacking seems like a silly hack that was wisely removed, explained here http://legacy.python.org/dev/peps/pep-3113/

What are the cases where you use it / rely on it?
Oops thought it was. Thanks!
> I want to try to get into Software Consultancy.

> Most potential clients I've talked to want me to create a somewhat simple website for them in 2-3 weeks…

In my understanding, software consultancy is when you work with your client and their engineering team, but don’t actually build the product. You may help hire the team and you may indeed write actual code, but it’s the team that’s supposed to do the actual engineering and future support.

Deep understanding of client’s needs (a pre-requisite), steering them away from wasting resources on building the wrong or unmaintainable product, and helping them organize their processes efficiently are important parts of consultant’s job. With that in mind, building the whole thing from the ground up at the same time just doesn’t seem to be the best use of your consulting skills. The following maintenance—even less so.

Normally consulting activities seem to be billed by the time (hourly or daily). In my experience, if you do build the thing yourself, it can be difficult to ensure client’s understanding that you’re really acting as both a consultant and the engineering team, and structuring your pay adequately becomes somewhat harder.

If you build the thing, you should probably make it your responsibility to ensure that deliverables include all the information necessary for future maintenance. Then the client is free to use it with their engineering team or a freelancer, and even if later you’re willing to be hired back for maintenance yourself, you’ll appreciate the documentation you’ve left.
For legacy code a converter might be the better option. E.g.

http://www.tangiblesoftwaresolutions.com/Product_Details/CPl...

Yes, it's not perfect but at least debugger, instrumentation, ... will work against the module.
Maybe they like those jobs more despite having lesser pay? Or do we always have to assume they are victims?
Absolutely agreed. It's irresponsible to present incredibly nuanced data at such a shallow face value without making any attempt to show the full story, especially on such an incendiary and divisive topic. How is this helping clear up disinformation and progress gender wage gap dialogue?
I'm sorry you feel that way. I sincerely find it very informative. Before I got first glimpse of it, I thought there would be at least 10-15 professions where women edged out men.
I think the point is: If Twitter had remained open, it would have been easy for users to export their graph and take it to competitors with similar features. Twitter closed their friend finder APIs to prevent this.

I don't know if App.net could have ever killed Twitter, but Twitter closing made it harder for users to transition to App.net in the first place.
I appreciate the gesture. Unfortunately, statistics is not my strong suit and R is not a language I am familiar with.

That said, did you consider the social and media context into which your work is being injected before you did so?
Awesome idea!
This isn't just a feeling. The existence of phenomenon such as Simpson's Paradox mean that this is something that any data analysis must be very careful about. Presentations of aggregate data are particularly vulnerable.
"Here's some misinformation for everyone! Fix it for me or keep your comments to yourself."
CloudFlare's 45th data center
I'm reasonably certain that that is not what azth was attempting to communicate. Is there a particular reason you are commenting in this manner?
GSOC: Institute for Artificial Intelligence
I will try to compile this today - appreciate that thank you. I understand that Ubuntu is making Python 3 the default from 16.04 onwards so I need to get moving. Looks like the long dusk for 2.x is finally turning to night.
You can use a similar technique to clone a garage door remote control. You simply have to record the transmission using the techniques mentioned in this post, then rebroadcast it on the same frequency.

Broadcasting FM is as simple as loading a Raspberry Pi up with PiFM[0]. Or, if you don't have the original remote (but are a bit more technical), you can just brute force the combination; most remotes only use a 12-bit DIP switch (4096 combinations)[1].

[0] https://github.com/CodyJHeiser/PiStation
[1] http://samy.pl/opensesame/
This gets posted every two weeks here. It is the opinion if one programmer and respected but enforcing your view is not.
Show HN: Best Automotive News – Ultimate Sources of Car News (Get It for FREE )
>When the disruptive competitor comes along – when, not if – who are the developers going to side with?

There can't be more than 50,000 devs who used the Twitter API. I definitely don't think they're going to be the deciding factor.

That being said,I would never use the Twitter API based on the horror stories I've heard.
This is why you should provide a locale for most sting functions in C# for example. I think this article is mostly about bad unicode support in programming languages.
"O'Neill finds that single women without children, on average, make 8 percent more than their similarly situated male colleagues"

http://www.ncpa.org/sub/dpd/?Article_ID=22058#sthash.6sSZrCm...
Of course you should charge for maintenance. But this is "Contract Development", not Consulting, fwiw.
Exponential Economist Meets Finite Physicist
Amir Najam on authorSTREAM
> Twitter has an enormous advantage over Facebook in one key area: while people on Facebook tend to friend their friends, people on Twitter tend to follow their interests. The social graph that makes up Twitter is worth far more on a per-account basis because it is directly monetizable in a way that Facebook’s generally isn’t – you can show prophylactic advertisements to Twitter users based solely on the people they follow, and probably get a much higher rate of interest. Compared to other social display ads, Twitter ads, it is rumored, work extremely well.

So, clearly this is from 2012 and the thesis is 100% incorrect (in fact, pretty much inverted). The interesting thing is that this is pretty much how the general populous still thinks Facebook does it's ad targeting. The author massively overlooked machine learning. I don't have first hand evidence, but I can only guess that Facebook is crawling every piece of data possible (pictures, messages, etc) and then draws conclusions of my interests there. In addition to this, all FB user info is being hashed and compared against consumer spending data (e.g. DLX and Acxiom).

The level at which FB and Google can target us is staggering. There is a reason these companies make so much money.
2012 was before Twitter went thermonuclear with their API limitations. (back then, you could even access the Twitter API without authentication!)
Visualizations like these certainly have their place, and I actually appreciate that the OP didn't offer commentary in this case. This graph acts as a blank canvas onto which people project their conversational biases. Each person has their own idea of what the pay gap is.

For me, the pay gap encompasses all sociological factors that lead to women making less than men. When the numbers are squeezed to only compare men and women by exact position, the question "why aren't women holding high power positions?" is implicitly answered with "because women are incapable," and that's a gross untruth. (This is not to say that such research has no value — it is quite important in the context of coming up with solutions.)

If you're quick to wave around the 97% number, you may not be treating this problem with the humility that it deserves.
Pay-Per-Story Platform Blendle Goes Live in Germany
Instant Glue and my keyboard was no more since then
Kylin