skysight-inc/HackerNews huggingface dataset:
Data Science Retreat | Director | Berlin or Montreal | Onsite | Fulltime | Visa | Remote possible for exceptional candidate

Data Science Retreat (DSR) is the market leader in EU for machine learning training. We are expanding to North America, we started in SF but are moving to Montreal. DSR helps coders or people with significant quantitative training (e.g. science, engineering, or math graduates) ramp-up rapidly for a data science career - arguably the fastest-growing, highest-demand profession. Our participants have an average of 5 years of industry experience.

We are launching a new product that is a big departure from our 3-month in-person training:

- For a monthly fee (3 different price points), our customers receive a topic that our teachers prepare in depth. For example, an exciting new technique that just came out in a paper and that is really applicable in the industry today

- There's code that implements the technique, but the most important part is that we provide a detailed explanation and references to every bit of knowledge you need to understand the topic. With exercises that are self-correcting (you write code, press a button, get red/green)

- This business model works well B2C, but it's something easy to consume for big corporates that want to train their people on-the-job (the current 3-month retreat doesn't address this need well). It's all very 'hands on' and more advanced than the usual MOOCs. We suspect MOOCs are not creating data scientists, at least not when done on-the-job. If we can demonstrate results, this should be an easy sell.

As Director of this product, these could be your day to day activities:

- Think up methods to increase our pipeline, together with marketing
- Pay attention to KPIs for recurrent business, for example, churn
- Decide which proportion of revenue goes to service the base, and which to invest in R&D
- Look at customer lifetime value (you don't need to calculate it, we have a resident expert on the team)
- Experiment with variations of product and pricing
- Do outbound sales to convince companies to try our service
I always find it amazing how many ‘technical’ people have a warped view of reality and it’s physical limitations.

I guess the take away here is that for the X13, they should just clock it way down from the start and just maximise battery life. Which is not a bad idea.
Which doesn't cost them as much and are part of the services agreement?

Just in case you did't know.
It would be interesting to know the regional distribution of those vehicles. Southern Norway has excess of energy and short distances and generative braking is particularly suitable to southern Norway... But Northern Norway does not have free energy sources (that is why they destroyed Alta river) and distances are long and winding but mostly flat.
I think the key legal point was that they changed how the phone worked after that sold it. (I anal)
> we have a Monorepo for each app platform

Do you mean two separate mono-repos, one for Android, one for iOS? To me that's not a monorepo. Is there little shared code between the two platforms, or is there a third repo that is depended on?
That could be both true and irrelevant when the other health related factors, plus the quality of life (social experience, etc) alcohol in moderation can enable is taken into account. Almost everything is a carcinogen.

So we need to consider Amdahl's law and profile. He die from so many things that we do wrong (e.g. sedentary lifestyle, stress, lack of proper healthcare) that alcohol/coffee could be a very premature optimization.

People in some of the so-called "blue zones", the places where people live most than everybody else statistically, drink a few glasses of wine a day.
I don't care much if the waste is in energy or hardware or in any other resource. And the level of waste depends only on the block reward and the price of ETH, not the algorithm used, because as long as it is profitable people will burn resources to get the rewards. In free competition people will do that until it gets unprofitable and it gets unprofitable when they burn as much value as they get from the reward. This is MC=MR argument - first presented in: http://www.truthcoin.info/blog/pow-cheapest/ . I believe it is possible that PoS is still more efficient than PoW - by being more secure with the same block reward: https://medium.com/@zby/proof-of-stake-can-be-cheaper-than-p... , but still the main point holds: the waste depends on the reward not the algo.
UI Dashboard Design
PII is a concept is US law. The GDPR uses personal data, defined as:

"any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person"

Pseudonymization (separating unique identifiers from the rest of the datapoints) can and should be used as a safeguard, but doesn't remove the need to protect the data, particularly if you keep a link between the two.
https://en.wikipedia.org/wiki/Jacobin - the second paragraph talks about the guillotining of 17,000 political opponents. I apologize if my comment seemed too ideological, but I think it's fair to assert that they're a provocative thing to name your magazine after, and the piece mentions Jacobin's featuring the guillotine as well.
Fair point, but ETH is not just Mr. Buterin and some close friends deciding to postpone mining winter at will. There are currently 8 groups building ETH implementations (https://www.coindesk.com/next-gen-buidlers-the-8-teams-worki...), so you have /some/ level of decentralization since they all have some weight in decisions.

Ultimately, the consensus in any classical blockchain HAS to be uniform, and that introduces an element of centralization (via the consensus algorithm used). That has always been true, and the contentious forks of BTC (and lately BCH) with their fights about the ticker symbol, name, and who has the "true vision" have made this pretty clear. Differing minority opinions have to go the hard fork way and hope to build something better.
Where in Asia? I imagine the culture is pretty different depending on the country.
Server-side analytics is not a silver bullet, but it's great for the quoted use case. While it has the mentioned disadvantages, so do client-side solutions. Many people run adblockers and it's easy - sometimes even a default - to simply block Google Analytics & co. So yes, if you really need exact statistics, you should probably run both client-side and server-side analytics. But for a rough "what's popular?" estimate, there's no need to impose (one more) JS file on your users. I've switched from GA to GoAccess a few years ago (running both for a few months), and while the absolute numbers were off by ~10%, the ratio was almost the same. But then again, I'm just running a blog and not a business.
When I got my iMac in 1998, it came with a crappy mouse and no ADB ports to plug my old mouse into, it only had those new fangled USB ports. Apple didn't make dongles and it was something like three months before a third party dongle was available, which cost more than a new USB mouse. For about two years, I had to run my Zip drive and printer on the dodgiest series of parallel-to-USB converters ever made. My point is that it has been ever thus. This is not new. I like that Apple push standards. USB-C is clearly the right direction to go. I’m just bitter they’re not available on iPhones. Yet.

As for headphone jacks. I haven’t used wired headphones with my iPhone for over 5 years. Dropping the jack has literally had no impact on me whatsoever. In fact it’s one less hole to fill with pocket lint. Before you go on a tirade of audiophile nonsense, I’ll remind you that most people listen to audio and video that is streamed over cellular data in a lossy format. All arguments are rendered moot. I am a content iPhone X user, so now you know of at least one.
Nice link!

FWIW, You also see <- within Haskell's do notation. Apparently F# and OCaml use it in places, too: https://en.wikipedia.org/wiki/Assignment_(computer_science)#...
The far side of the moon isn't dark. It has the same day/night cycle that causes the phases of the moon visible from Earth.

On the other hand, it is shielded from radio emissions from Earth and might be a good place for a radio-telescope.
To me, the key point is this: Splitting your code into multiple repos draws a permanent architectural boundary, and it's done at the start of a project (when you know the least about the right solution).

The upsides and downsides of this are an interesting debate, but there is a cost to polyrepos if you want to change the system architecture. There is a cost to monorepos too as argued by this post, and its up to the tech leads as to which cost is greater.
What are you talking about! In my perfect micro services world I just have these enforced bounded contexts that are so perfectly designed they never need to change. Consequently all parts of the system are perfectly independent snowflakes that can be deployed without thinking about any other parts of the system. It’s beautiful really when you think about the mess that things were before we could do this!
I'm not an expert, but I looked at both BQ and ELK and went with BQ just for ease of ops and the fact we can use SQL, which makes it more accessible to other team members who know SQL.

We're a small startup though, so last thing I wanted was even the slightest ops load from a new system.
They’re crazy if it’s not open source.
It's entirely possible, and repositories like https://github.com/facebook/fbthrift/ are an example of an open source project that is synced commit for commit with a private monorepo.

It just requires some tooling (like everything with monorepos)
Sure but if they change it in a negative way they lose because they own the mayority. That's why to be able to change anything you have to have a huge stake, it's like having skin in the game.
Is it really a joke? Because if this is seen as a valid argument in the Ethereuem community then they've really gone off the deep end.
I haven't tried in Git, but with Mercurial merging repos is as simple as pulling from an unrelated repository and merging, that's it. It's a lot simpler than splitting a repo up unless you accept that all of the old history can remain, then you just make a clone and delete what should no longer be a part of the repository.

But monorepo leads to tight coupling, and that is just as much a pain to work on as versioning, or two teams are simultaneously working on the same shared code, and you have not only merge conflicts, but conflicting functionality.
You must be joking. Have you seen the public transportation in Munich? Budapest? Berlin?

http://www.muenchen-touristeninformation.de/MVV-Schnellbahnn...

http://www.hungarybudapestguide.com/wp-content/uploads/detai...

https://www.s-bahn-berlin.de/pdf/VBB-Liniennetz.pdf
Hilariously misguided.

Pretty funny to read that the things I do every day are impossible.

Monorepo and tight coupling are orthogonal issues. Limits on coupling come from the build system, not from the source repository.

Yes, you should assume there is a sophisticated "VFS". What is this "checkout" you speak of? I have no time for that. I am too busy grepping the entire code base, which is apparently not possible.

If the "the realities of build/deploy management at scale are largely identical whether using a monorepo or polyrepo", then why on earth would google invest enormous effort constructing an entire ecosystem around a monorepo? Choices: 1) Google is dumb. 2) Mono and poly are not identical.
> Eh it's not about how often you use something,

It kinda is, though. If I spent a huge amount on something and never used it, that would be a status symbol thing.

> the added value of a 1400 Euro phone over e.g. an iPhone 8

That's implying there's no difference worth the additional cost. The X has a better, bigger display than the 8; better camera(s); better battery; all things which are extremely relevant to my daily use.
Cryptocurrency Trading App That Looks to Set Itself Apart from the Competition
Your comment paints a worse picture than I thought. Mostly because I think a great majority of potential customers are hoping apple will finally eat dirt, get the market's message and stop their new trends, but with those numbers in hand they might think that their mistake was selling the lower priced product and continue on their path on all other areas...
FTI: Apparently "google3" is the Google monorepo

https://news.ycombinator.com/item?id=17123620
> I will try out the Python version,

I don't think there's a Python version, unless you count using Ruckus via Python on Racket[0].

> lack of immediate feedback

When "Automatic Reload and Preview" is enabled, OpenSCAD re-renders the shape whenever the text file is saved, so there's hardly any time delay, although there is arguably a spacial remoteness due to the text being separate from the shape.

> along with the fact that it's more verbose than the point-and-click interface of Fusion.

I personally find it difficult manipulating 3D objects by with a 2D cursor. I've spent a fair amount of time on the point-and-click editor in Blender, and I find it less confusing to have a textual expression of the shapes at hand.

Perhaps the one (possibly accidental) killer-feature about OpenSCAD is that it works well with external editors, such as vim.

[0]: https://github.com/pedropramos/PyonR
An open-source eventstore for Node.js
It’s good enough for dollars and cents if you put thought into it, but you can’t just represent money as double-precision dollars and expect to get the results you need.
The kernel is not a monorepo. The kernel is a large(ish) repo.

A monorepo would be if you put the kernel AND userspace in the same repo (e.g. all the code for a Yocto distro). To me, when people talk about a monorepo they are talking about putting separate pieces of the architecture in a single repo.

It's a great example actually. If it was all in a monorepo and you could release it together then you wouldn't have to worry about the breaking userspace, you could make the changes to both sides at once. In practice because that's not how releasing works in that environment, you can't do that.
Most people, most use cases, don't want irreversibility.

Reversible transactions are a huge positive.
Talent exists, and is very real. [0] Talent is immensely important, and I find that there's a growing movement to dismiss it and pretend it's all about hard work.

Most people can get pretty good at a particular task if they dedicate enough time. But you're never, ever going to be as good as Magnus Carlsen, Terrence Tao, Michael Phelps, Euler, or DaVinci just by hard work and a positive mindset.

[0] https://slatestarcodex.com/2015/01/31/the-parable-of-the-tal...
That begs the question then, what happens to these early-20s geniuses once they are late 20s/30s?
Site looks great. I'd shrink the footer.

Content wise it's hard to know how to judge it. London has decent restaurants from nearly everywhere, but some of the best are not central (New Malden for Korean, Green Lanes for Turkish).
I've met two that made my jaw drop. One was a guy I went to university with, 19 yo first time I met him, who was extremely good and had been running his own web developing business as a side gig since he was 16 (for Swedish readers, just to get a sense of how good he is, he made www.breakit.se in 2014, no idea if he's still maintaining it though or if they've switched to a different stack). I haven't heard of anyone who knows who he is know in this city who's also seen a better JS developer.
However, he was a real pain to work with. If you didn't work quickly enough for his taste he would tell you to move away from the keyboard and he'd show you how it's done. He also did not like compromising with other people in discussions and he liked to do other people's tasks without telling them.
Despite that, I recommended him when my boss asked about him with the caveat that he should ask honest questions about expectations on the work culture, specifically team work.
Turns out he insulted my boss and my company pretty quickly in the interview. My boss told this guy about how we've worked hard to do continuous delivery the way we do today and this guy laughed my boss in his face and basically said "well, you might win over a lot of people who write software for the government with that story of how you guys put on your big boy pants but I do six deploys on a bad day". Apparently he instead went to a game studio and is a better fit at that place.

The second dev who took my breath away was a man in his late 40s who had consistently moved from companies as soon as they wanted to put him into management. He loved to code and was very good at it, but for some reason management wanted him to make room for younger hires (can anyone with more experience explain why that would be the case? This man has 20+ years of experience and loves to code, shouldn't he be more preferable to some kid?) so he was able to leverage his contacts he picked up as a consultant to change into high paying developer jobs. He was very understanding of how bad I was when I started out as a developer and was my mentor for a long time and his discipline still inspires me. It was an honor working for him, why people want to make such a good developer into anything but a developer, I'll never know.
> If they get caught cheating, they lose their stake

in that chain. In any distributed blockchain there's going to be several chain(tips) at any given time.
My point was that allowing 'None' was/is a flaw. If you want to shuttle bits of data about in an unsigned/unencrypted/insecure way, that's what raw cookies are for.

Now, as cookies are buckets to dump data, there is of course nothing to stop you encrypting, signing and doing all sorts of things to cookies.
So -- ignorant question here -- why not just use human blood, instead of trying to emulate it? Obviously this has consistency and reproducibility problems of its own, but are they worse than the effects of using a completely alien medium?
> Ready to commit? Whoops, another team made a bunch of commits to their project, and you need to rebase your project before you can commit. (I'm having flashbacks to Clearcase already.)

If they merge cleanly, it's not an issue. If they don't, you need to fix the merge conflict. The work you need to do is proportional to the number of merge conflicts, which isn't special to monorepos.

> Need to roll back the last two commits you made? Sure, that takes two seconds--oh, wait, another team made multiple commits that got interleaved with yours. Have fun cherry picking the files you want to revert.

Again, only an issue if the changes are on the same files. It can be a bit of a pain to revert a stack of diffs, but if it's just a random commit with no other relevent commits to the file, very easy.
I'd say Lisp is S-Expression based, and it's easier to make both text and graphical interface to S-Expressions than to the syntax of typical text based languages.

By Apple's decree and app store policy, any programming language on the iPad that isn't purely based on the JavaScript interpreter in the web browser isn't allowed to download and run executable code, much to the frustration of Alan Kay, who is weary of people comparing the iPad to the Dynabook without acknowledging that Apple left out and prohibited his most important idea on purpose: user programmability.

If Carmack's visual Lisp is implemented as an iOS app with locally running native code, and not purely in JavaScript running in the web browser, then he has to build it himself in XCode on his own Mac for his own use with his own Apple developer certificates, and he isn't allowed to distribute it on the app store.

If you can implement your language purely in JavaScript, like Snap! or the web version of Scratch 3.0, then it'll run everywhere, and isn't an iPad app, just a web app, so it's not bound by the restrictions of Apple's app store. That's the way to go if you can.

https://snap.berkeley.edu/
WebSockets on Android
SEEKING WORK
Location: Zurich, Switzerland

Name: Jessica Goldberg

IQ: 145 on Stanford Binnet test (tested 1 year ago)

Remote: Yes

Willing to relocate: Yes

Technologies: angular 1, angular 2, es6, react, redux, react-native, webpack, html5, css3, sass, scss, jade, node, php, building restful api’s, git, grunt, jenkins, jira, mysql, postgres, redis, mongo, firebase, aws, heroku, python, aws, rust, go, c++, vuejs, java, haskell, ocaml, redshift, bigquery, cloudataflow, google pub/sub, kinesis, lambda, serverless

Rate: €600/hr

Work: I can implement whole ad network or payment processing or sales/marketing/affiliate system from scratch, including data pipelines, bidding, frontend, user experience etc... Everything without fail with an accurate time estimate of features accurate within an error of a week.

I have worked in both technical and management roles.

I am also an expert in direct marketing, customer service and user acquisition.

Email: jessicayesnoyes@gmail.com
Ecwid Competitors
Dublin tram system. Hackers claim to have breached security and demand ransom
> systemd

> simplified

I like systemd, but it never simplified anything, especially with the huge amount of dependencies. At most, it made things relatively uniform across Linux distros, but in the end of the day each distro has to maintain their own .service files anyway.

Lightweight and embedded Linux distros won't use systemd by default in the foreseeable future because it's anything but simple.
My hobby: inserting hyphens for effect.

> gigantic ass-phones.
EPFL, Blue Brain Project, Neuroinformatics team | Software Engineers, Knowledge / Data Engineers and more | Geneva, Switzerland | ONSITE

The goal of the Blue Brain Project is to build biologically accurate digital reconstructions and simulations of the rodent, and ultimately the human brain.

Are you looking to work on an open source project using cutting-edge technology in a nice working environment while contributing to the greater good?

Come join our Neuroinformatics team to help us build Blue Brain Nexus ( https://bluebrain.github.io/nexus/ ), a knowledge graph for provenance based, semantic enabled data management and data driven science.

Since Google Knowledge Graph announcement years ago, knowledge graphs are becoming ubiquitous as simple, flexible, expressive and powerful way of integrating, searching and sharing data in large organizations. In a knowledge graph, a domain of application is broken down into entities - the Things- (people, organisations, software, workflows, events, etc.) connected by mean of relationships whom semantic are explicit. This simple and expressive data model makes knowledge graphs suitable for powering intelligent system and services. By joining Blue Brain Nexus team, you’ll contribute to the development of a scalable knowledge graph technology.

Some of our technology stack: Scala/Akka, Typescript/React, Openshift/Kubernetes, ElasticSearch, RDF based Graph Database, Linked Data, SPARQL, JSON-LD.

We have many positions open. For more details and for applying:

- Scala Developer: https://go.epfl.ch/bs8

- Frontend Developer: https://go.epfl.ch/bs9

- Knowledge Engineer: https://go.epfl.ch/bsA

- Data Integration Engineer: https://go.epfl.ch/bsB

- Data Integration Specialist: https://go.epfl.ch/bsC

- Manager, Data and Knowledge Engineering: https://go.epfl.ch/bsD

- Computer Vision Engineer: https://go.epfl.ch/bsE