skysight-inc/HackerNews huggingface dataset:
Technical Cofounder

Sharebird | San Francisco, CA | Onsite | Full Time

I'm looking for a technical cofounder with SaaS experience and strong user experience chops.

I started Sharebird a few months ago, and have a full product built on rails. I ran a closed beta and now have paying customers.

Sharebird shows marketing teams what content to create to help their sales teams close deals. We have a large market, and one in which I have domain expertise. Also, I used to be the VP of Product at a ~$10M SaaS company before I left to start this product.

Our five cultural values are:
- Humility
- Hacker
- Growth
- Community
- Transparency

Email me at alex@sharebird.com if you want to know more.
More info can be found at https://jobs.braveclojure.com/jobs/17592186045748/clojure-en...
I think it is hyperbole given the surrounding context of this article/thread is mostly speaking to squashing commits after a review has happened in a PR. I say that not as a judgment, I like hyperbole and admit my top-most comment was intentionally hyberbolic too. Hyberbole is a good conversation to have sometimes.

A commit to git is a named snapshot of a file tree. That's it. All the other "worthiness" we ascribe to a commit is communal. A person's unhygienic work-in-progress can give you insight into their thought process or their work ethic. Why did this person give me this particular named snapshot of their file tree? I expect they are tell me (or future them) something and I can respect that artifact and preserve it, just as easily as you might angrily suffer from it and destroy it.

CI or "git bisect" "worthy" are orthogonal considerations and also vary between communities and needs.

If there is something we can agree on here: yes, all commits are not created equal. Even all commits aren't worth preserving equally. That said, I think there are tooling solutions here far beyond "destroy that what you dislike".
Thanks Kamil. For other people reading and interested in computing platforms that we support also see https://gitlab.com/gitlab-org/gitlab-ce/issues/14812
Optionals can't be expressed safely in Go. They have a type of `Option<T>` or `Maybe<T>`. Swift just has this notion built as an operator.

Traditional enums aren't particularly interesting. What languages like Rust and Swift have are tagged unions. They let you associate data with each variant.

Moreover, pattern matching is needed to use tagged unions effectively.

Constants are not "basically" tagged unions or even enums. They are not grouped into a parent type. For example, if you have a `Foo` enum with `A` and `B` variants; while matching or accepting this, you can accept a `Foo` which is guaranteed to be either `A` or `B`.

How would Go typed constants achieve this?
I've been reading Design for Real Life (https://abookapart.com/products/design-for-real-life), and its introduction is a fairly similar mirror of this kind of snafu -- using Facebook's "Your Year in Moments" feature as a stand-in.

When Facebook first launched it, they positioned it as a "look at all the awesome things that happened this year!" sort of feature, with lots of smiling faces and positive, upbeat language. However, the reality often didn't match up -- Facebook would add sad or otherwise unideal photos/statuses to the collage, such as houses burning down, depictions of illness, etc. etc. Lots of users complained, and as a result they shifted the tone of the feature to be more neutral. ("We thought you might like to take a look back at the past year")

Put another way: edge cases (or as the book refers to them, stress cases) exist not just in code paths but in your user's expectations and emotions. Just as a good architecture can handle these appropriately, a good design and UX accounts for the entire spectrum of users.
One of the author's here — you're nailing the exact point that we were trying to emphasize. In real cases, we often have incomplete or obscuring documentation, and draw conclusions from that. The addition of another perspective can radically change our perception of an encounter. Granted, it's artificial to the point of absurdity in this case, but the point is made.
For what it's worth, I pretty much exclusively use git through Eclipse's EGit UI. I do a lot of rebasing, as we use Atlassian's "centralized" workflow. [0] It's interactive rebase interface is pretty good. If you haven't used it, maybe try loading a repo into it and see how you do.

[0] https://www.atlassian.com/git/tutorials/comparing-workflows/...
Hack the Pentagon to win $150,000 bounty
New Release: Neo 4 Java
I see your point that there are more avenues available than before but more avenues != easier to get your product noticed. I think that's where others and me disagree with your premise. I employed all those avenues to promote my 2 products. Anecdotal evidence from end is that a post on HN by someone with high karma still got me all of 200 visits to the website. Getting on the Featured List on PH got 2 signups and 50 upvotes and a total of 156 visits to the website. Facebook, Twitter, LinkedIn, Google+ combined totaled 300+ visits to the website.
I agree with you. In fact I think the reason we have to do squashes and lose fidelity is because the git model is broken.

There is not technical reason a source control tool could not offer multiple 'views' into the commit history. A high level linear view which you can zoom into to see the underlying commits and merges. Why do I have to lose the latter to see the former?
Pyze | Senior Backend Developers | Redwood City, CA | Full-Time | Onsite, VISA considered

We are a growing and fully funded company that just launched out of Beta this week and seek to hire our seventh employee. We're looking for someone who cares about making a huge impact in making mobile app publishers create and grow successful and thriving mobile app businesses. We've built a business intelligence platform for mobile apps that automates and personalizes user engagement to drive stickiness and usage.

We work with Java, Scala, Kafka, Storm, Spark, Cassandra, Redis and much more. Experience in these areas is a big plus.

We are looking for backend engineers with big data and scaling experience, with some familiarity with our toolset. Nice to have experience working with one or more of the following: R, Java-ML, etc.

You can check out our jobs page http://pyze.com/jobs-at-pyze.html or reach out to me directly muntek+hn @ pyze.com
Some jokes are not scalable. Funny cats on youtube are scalable.
Aren't you working for Hacker News for free right now? If nobody posted comments here, nobody would know what Y Combinator is. And high-profile HN contributors aren't getting a share of profits YC makes from their startups :)
Privacy oriented niche, but yeah.
On the contrary, I think using a single tool (i.e. email) for every type of communication is the anti-pattern. The fact of the matter is that real-time chat is much better suited for most types of conversations that happen in a typical workplace.

My policy is that if the email is going to be less than two paragraphs, it's better to send it as a Slack message (or IRC or whatever your team uses). But if you need to elaborate on an idea, or bring someone up to speed on something, then write an email, and make sure it's exhaustive.
Auto Langzeitmiete sogehtauto
I bought a Lytro Illum to play with 3D pictures, which id did quite well on smaller scale objects. I have beautiful roses to show for it on my 3d Samsung TV.

Unexpectedly to me, it turned out to be very useful for a different purpose.

With a regular camera you have plenty of megapixels, so in post-production you can crop left and right. This allows you to learn how to frame your shots well via rapid iteration. Had you not had the megapixel surplus, you would have to make new shots to iterate on your framing technique, and that would take a lot longer.

While Lytro is lacking in megapixels, it can serve the same purpose with respect to depth of field. You can take hundreds of photos with a regular camera honing your DOF skills, or you can just play with it in post-production and very quickly see how it changes the overall picture.

Had they shipped their third-generation camera, it would allow to do both, making it an indispensable photography training tool.

It's sad that they had to wrap it up, but I wish them the best of luck with that VR thing.
Hey this is Nathan, co-founder of Baqqer. Just to echo what Dan just said, we built baqqer with the idea that individual creators/makers/developers/designers should be able to test out their ideas with minimum effort to see if they have legs. Unlike Kickstarter where users need to have their product costs down to the penny, we let users build community and long-term funding around their ideas(side-projects) until they prove the model. This allows for pivoting, product recognition, and idea validation. We see ourselves as a pre-kickstarter platform.
Maybe they don't need to apologize to the users tweeting at them. But maybe you heard about people who, for instance, got fired because they hit this accidentally?
It's an effective way of putting power in the hands of people impacted, for better or for worse. I've certainly reopened "by design" bugs in areas I don't own because I think the design it wrong. Done with tact (and usually a note explaining/alerting the person) it generally goes over well.
Get yourself a WIP branch, do whatever you want on it, extract clean commits from it, kill it with fire when finished.
Do you bother to reply to submissions these days? Or still ignoring them?
There was a patch submitted in 2011[1] to do roughly that, but it got diverted into a different purpose and then seems to have disappeared. It certainly seems like it must be possible to have a git-bisect that can deal with branches.

[1] http://git.661346.n2.nabble.com/RFC-Add-bad-branch-first-opt...
The ‘Hello World’ Fallacy – our bias towards easily demo-able tech stacks
Bending Spoons | Software Engineer | Milan (Italy) | Full time, Visa, Onsite

Bending Spoons is a fast-growing tech company focused on building and marketing mobile applications. We think, create, and market our own apps. We're young (2 years of activity, average age 27 years old), but we've achieved explosive growth: the apps that we've invented, developed, and published have been downloaded more than 35 million times, and millions of people use them every week. We are currently looking for an exceptional Software Engineer to join our team of backend and iOS engineers. Our backend stack consists for the most part of Python, node.js, MongoDB, and Redis. Our iOS work is every bit as extensive and challenging as the backend one, if not more. Among the perks we offer: free lunch five days a week, a cool office, top equipment, and the opportunity to join an incredibly skilled team.

More information and application form at http://bendingspoons.com/en/careers.html (Please mention that you found out about us on HN in your cover letter.)
Skyscanner | London, Barcelona, Edinburgh, Budapest, Sofia | ONSITE, VISA | full-time

We're one of the biggest travel metasearch products in the world by traffic... and we want to x10 that :)

Hiring experienced people in lots of key disciplines: backend with distributed systems, full stack and frontend, designers, product, iOS & Android. We are hiring to all our European offices - London and Barcelona being the 2 newest offices we're scaling. In short, if you're good, and looking for something challenging, we're interested.

We're one of the very few unicorn companies HQ'd in Europe who are profitable - and have been so for the past 7 years. Recently we've had the director of Amazon S3, Bryan Dove join us as our VP engineering - in London you would be working closely with him alongside some very experienced industry figures.

We're looking for people interested in working on large scale challenges and building new products. We have an incredible amount of historical data and a unique position in the market. What does the future look like? How do we change the game? How do we best use our data, our scale and new technologies to our advantage as we grow? We're particularly interested in travel personalization and recommendation, as well as developer enablement and tooling.

We've recently opened a Barcelona and London office and there is incredible energy across the company. We are set out to be the #1 flight search engine in the world: from the UK through US, all the way to Asia.

You can apply at http://www.skyscanner.net/jobs/ - or ping me an email at alex (.) treppass [at] skyscanner.net for a referral. Happy to answer questions or pass you to someone who can.

On a personal note, I see a lot of freedom, responsibility, accountability. Engineers have a LOT of room to make decisions and move fast, and the encouragement to make things better. It's an exciting place to be.
I have a foot in both communities.

Around 10 years ago, developing Java enterprise desktop applications was a mix of pure Swing, SWT, Eclipse RCP and Netbeans Platform.

Nowadays, just speaking from our customer projects, it is .NET for Windows only applications and Web for everything else.

The only place where Java based UIs still matters are on Android.

And on mobile OS, thanks to Oracle not caring about iOS and Windows Phone, C++ and C# are the languages to go for portable native apps. With Xamarin being made available for free, this will increase C# (including F#) usage for such applications.

Currently .NET Core lacks a story for portable UI framework, but if it gets one, it might win some adoption outside Windows for desktop apps, at least more than Java, as JavaFX doesn't seem to be wining much mind-share.

Another advantage of .NET Core is that Microsoft is having AOT compilation for free, while on Java world the best AOT compilers are commercial.

However for server side UNIX applications, mainframes and embedded devices, there Java might still rule, specially thanks to the existing developer base.

Also pure speculation from my part.
There's also Nim, which AFAIK started out by targeting C, but apparently now also support c++, objective-c and javascript backends: http://nim-lang.org/docs/backends.html#backends

For more on Nim, see nim-lang.org and/or https://howistart.org/posts/nim/1
Learned english decades ago but I still confuse though, thought, through and thorough when I write.
I can relate to that. I don't like those WIP commits on a feature branch (when the program is crippled or even doesn't compile or doesn't pass the tests, when the code is filled with temporary "printf" debug messages, etc.) to be in the history of the master branch.

Ideally, every commit that I'm making should be preferably not big, but logically complete and working. The problem is that sometimes I want to work on another branch and I have to commit in the middle of the work so I can checkout into the other branch in which case (without a squashing merge) the "offending" WIP commit would end up in the master branch's history.
http://www.wsj.com/articles/theranos-has-struggled-with-bloo...
What's your timeline for being as open as the Tor folk about abuse of your network and start taking responsibility for all sort of internet scum being protected by your network and allowing them use of your infrastructure?

You seem keen on making locking out malicious use of Tor, when can we expect you to lock out malicious use of CloudFlare?
>>The problem isn't that it's a joke. The problem is that Google didn't do any kind of UX thinking behind the change.

Actually no, the problem is that the joke they came up with is the type that requires UX testing in the first place, i.e. it changes the behavior of a product in a very noticeable and non-reversible (by the user) way. As opposed to something harmless, like a joke announcement or something.

Several years ago Blizzard announced the "Archivist" class for their popular game, Diablo 3. They put a good amount of effort into the joke, with a short gameplay video and everything. But it was a joke, and the class didn't actually make it into the game, and everyone had fun.
Do applicants need security clearance? (i.e. could a Canadian citizen apply?)
A joke should be simple, globally understandable – and if it isn’t understandable, shouldn’t be too annoying – and it should never be destructive.

Changing GMail to render (but not send!) all emails in Comic Sans would be such a change. (With a notification at top to turn it off)

Offering "Clippy" now also in Hotmail would be such a change. (with the ability to hide it)

Adding a "Send (and attach a gif that makes me seem like an idiot, and nuke the conversation)" button where a normal send button used to be is not.

A good joke is hard, and we all have made jokes that backfired before. But for a corporation, such as Google, in a huge project of theirs, they should try to double and triple check each joke for damage it might do.
I guess what you're trying to say is that BayesDB and BQL are leaky abstractions?
I'm posting a comment to make sure I come back to this, silly HN mobile apps make it difficult at times...
Yeah, it goes to show that you really want a mid-level language-specific IR (which is what the Plan 9-based compilers have) if your language is at all high level.

I think the ideal for best performance of generated code is 3 IRs: a mid-level language-specific IR for high-level optimizations (especially around memory management and devirtualization), a low-level IR for lower-level optimizations (e.g. algebraic simplifications), and a codegen IR (for instruction selection and scheduling). This is what Swift is doing, as far as I can tell.
Just started looking into Cydia, cycript and static analysis on an older model iPhone for application development debugging. If you're a dilettante, enjoyed this article and want to get some productive use from your older model iPhones it's a lot of fun. http://www.cycript.org/
> But I have literally no idea why in 2016 anyone would want to subject themselves to irc (plus whatever other crap you have to install/configure to make it bearable).

Although I'm not trying to discount what you want for chat...
Everything you just desribed is super easy for me to do with IRC. I can customize it to look however I want, and just connect with the protocol. That's why I "subject myself to irc". All the commands you have trouble remembering, are customizeable, and muscle-memory for me.

> Now I can use a browser.

hmmm... that sounds like the opposite of what I want. To each their own I guess.

> Not that i'm trying to sell slack

Not at all. I asked for a comparison, and that's what you provided. I guess I just don't have any personal interest in it over IRC. Cheers!
Depends on two things IMHO:

(A) how important the commit is and (B) how many lines of code are changed.

Squash makes sense usually when you have have a branch with multiple small commits that affect the same thing. Doesn't make sense to squash 2 commits affecting large parts of the application just because your commit has to be squashed before merging.
Snoopa Vision YouTube
Wasn't it already? :-)
Kind of a tangent but...

Anyone know of a nerdy source for stretching exercises? I'd love to know exactly how often, and how far to stretch to maximise progress rather than just guess but I've not really found anything that seems to have rigorous justification for their numbers.
Kentik | San Francisco | ONSITE / REMOTE

Want to architect, build, and maintain the interface for our industry-leading big data platform for network data? Then come on down. Kentik is looking for a full stack JS engineer to help translate the trillions of data points we record daily into actionable insights.

https://www.kentik.com/careers/?gh_jid=147806

If interested, email me directly: pye+hn at kentik dot com.
Also second market lets employees cash in their options instead so there isn't internal demand for a liquidity event.
So that's essentially what mercurial's evolve extension does. Which is pretty useful in some circumstances, e.g. if you have a review tool where you want to support rewriting history in a nice way (the typical approach to this in git tools is either a) don't meaningful support history rewriting, b) require manual ceremony for each history rewrite, or c) add unique ids to each immutable-across-rewrites commit).

Whilst it's clear that retaining the pushed history can be useful in some cases, I don't understand the notion that disallowing history rewrites helps retain useful data in general. Developers can make commits for all kinds of arbitary reasons e.g. they reached the end of the day, or had to switch branches to work on a different patch. That doesn't seem like a particularly useful thing to record. To take it to an extreme, I wonder if any of the people who think that the precise commit history gives useful information about how a feature was developed have configured their editor to commit on keystroke, since that seems like the logical conclusion of that position (and indeed is effectively what tools like etherpad do). I suspect not because, actually, being selective about the information that you keep is rather helpful. During rebase we see the developer as curator, selecting the most useful representation of a set of changes for the benefit of future readers. or, to use your analogy, if someone suggested removing meaningless data from a report to focus attention on the most important points, then they would certainly not be laughed at, but praised.

Of course GitHub's implementation is too blunt a tool to be really useful, but hopefully we will eventually get something better.
When that stopped working is when I went with DDG full time for my searching needs at home and at work. And I don't yet regret it either.
'The Coding Man' to Open on Broadway with Bill Gates in Title Role
Ravel Law https://www.ravellaw.com | San Francisco, CA | Full-time

At Ravel, we develop the legal profession’s most innovative products for data analysis, visualization, and research - uncovering insights about judges’ rulings, revealing critical cases, enabling lawyers to make data-driven decisions, and more.

Ravel was launched from Stanford University’s Law School, Computer Science Department, and d.school, with the support of CodeX (Stanford's Center for Legal Informatics). We have been featured in Wired, The New York Times, the American Bar Association Journal, and our founder is a Forbes 30 under 30 for 2015.

We are a rapidly growing Series A startup funded by top tier investors like NEA. We offer competitive compensation, equity, and health care. Our culture is extremely dog- and human-friendly. Our office headquarters are in San Francisco, South of Market - conveniently located between BART and CalTrain.

We're looking for Front-End Engineers (jQuery, Ember, D3), Full-Stack Engineers (Scala, JS, Mongo), and Data Scientists (Spark, H20, Stanford NLP).

Check out the full descriptions and apply at https://jobs.lever.co/ravel.
It does tell me a great deal about your development habits, yes.

Maybe not information that I care to do much more than skim, of course, unless I'm your manager looking for reasons why you might be working from home too much. :) (That said, there's probably some cool deep learning applications here...)

Some of the information, for instance, is that maybe you are working on pieces too large at a time and should find more ways to break them into smaller units of work that you can more easily commit in logical piece at a time rather than "snapshot dumps" between computers.

Like I said, from a hyberbolic standpoint, how the sausage is made isn't pretty and is full of garbage sometimes, but it is informative.
iOS 9.3.1 jailbrak with 3k jailbreak download
Apple Inc | San Francisco, CA | Competitive Salary

Apple's CloudKit (part of iCloud) is hiring backend developers who have Linux expertise and who are excited about Swift. Job is full time in San Francisco.

More info at
https://jobs.apple.com/us/search?#&ss=47424189&t=0&so=&lo=0*...

Email jaybuff@apple.com with [HackerNews Job] in the subject line.
Big changes in Google Local search today. Here's the fix