skysight-inc/HackerNews huggingface dataset:
Thanks!

> lazy loading can happen in any component rather than only at "page" level

You can use dynamic imports anywhere in Next using `react-loadable`.

> more things are provided by the team via plugins

Next relies on its thorough `examples` dir for integrations. But it means a lot of manual coding.

I had a crack at a plugin system in the past (i.e plugins for adding features like apollo, redux, etc. AOT like stuff). I found that it obfuscated the code too much. Makes it hard to trace what is happening and make adjustments. The closer the code is to the "Getting Started" examples of Redux, I18n, Apollo, the easier it is to tweak and understand.

E.g. Sometimes it might be clearer to just wrap a Provider manually around the app root, than expose a plugin hook. Because you can see the React tree, whereas with plugins everything is dynamic so you must rely on logging.

I think devs are naturally drawn to DRYness and dividing code up by feature, which is what a plugin system offers, but there are big tradeoffs. I'm interested to dive into Fusion to learn more about their approach though.

> - better support for maintaining server-side complexity (e.g. by using Koa + DI system to make testing/mocking easier)

Great to see you adopting Koa! I use it myself, and feared that the community had stagnated, but now with Fusion, it may be reinvigorated.

> DI system to make testing/mocking easier

Very cautious of DI systems. Same reasons as plugin systems: its hard to see what is going on. And sometimes manually wiring up all the dependencies is actually not much code at all, and you can manage cyclic dependencies and ordering easier.

Keen to dive in deeper though.
Zimbabwe election unrest turns deadly as army opens fire on protesters
Just a precision in case a junior dev read this comment : denormalizing has nothing to do with the problem experienced by the OP. They just queried the whole collection of paiements instead of precomputing a total everytime a new paiement arrived.

Denormalizing would have required having a relation between collections. Here there was just one (so there was nothing to denormalize).

Optimizing for reads ( or simply think about read performance) doesn’t require denormalizing. It can also be a matter of creating an index, or precomputing values in a cache, like in OP case.
Blitzm Systems | Melbourne, Australia | Senior Software Engineer, Database and ETL Engineer | Full-time | Onsite | https://www.biltzm.com.au

Blitzm is a software engineering company founded and run by software engineers. We work together in Melbourne and create solutions for companies around Australia and beyond.

We require two engineers who can focus on a major project using Microsoft stack, Angular and native mobile.

* Senior Software Engineer - be a key decision maker, architect and communicate solutions, lead other developers.

* Database & ETL Engineer - database design, manage database migrations, data warehousing and reporting, MS DB tools.

We work in a social but relaxed share space. We promote everyone to contribute to internal/side projects. We have team tech workshops every Friday. We hire engineers that enjoy both creating software and continually learning how to do it better.

Email applications to: jobs@blitzm.com
Qt for devices is commercial only, not GPL.
Solutions to Extract Data from Ethereum
Xara | Berlin, Germany | Backend Developer | Full-time | Visa | Onsite | www.xara.com

This is your opportunity to work on a product that will be used by millions of people, and to contribute to the most amazing web-based creative tool being developed today. A team of 30 developers is building a new slick product, using the very latest, state of the art web technologies: Javascript, HTML5, CSS and WebGL for only the newest browsers and touch devices. We also use Node.js, React, Vanilla JS, Git, Mocha, Karma and TeamCity.

About you:

Solid commercial experience (3 years +) with:
Server-side programming, Linux configuration, TDD and continuous integration, JavaScript and Node.js, Advanced Bash programming, NOSQL (Redis and MongoDB are required), TSDB, Docker, GIT.

- A solid understanding of cloud deployment strategies and scalable architectures - A desire to work on world-leading web software products - Highly motivated, with a positive attitude to work and the ability to learn quickly - Good trouble-shooting skills with the perseverance to solve problems - Able to work productively, both autonomously and as part of a dynamic team

Some nice to have experience:

Good knowledge of the most common web servers / load balancers (Apache, Nginx, HAProxy), Experience with ELK and Grafana, Experience with AWS or GCP, Experience with Kubernetes, Commercial experience with high-volume scalable architectures, an interest in online security

For You:

- Exciting work with high responsibility - Work in a startup with the ability to have an impact - We promote professional development - Highly motivated and friendly colleagues

Are you interested in new exciting challenges, while working in a young and dynamic environment in Berlin? Please get in touch with us: jobs@xara.com or through http://www.xara.com/jobs/
Tray.io | London | Front/Back/Fullstack Engineers | Full-time | Onsite |
https://tray.io/

Tray.io is ushering in the era of the automated organisation
We believe that any organisation can and should automate. With Tray.io, citizen automators throughout organisations can easily automate complex processes through a powerful, flexible platform, and can connect their entire cloud stack thanks to APIs. Today businesses like IBM, GitHub, Forbes, Lyft, and Digital Ocean rely on Tray.io to connect and automate data flow between the tools they use every day. With Tray.io visual workflow builder our customers create automations to drive their business processes without writing a single line of code. Our challenge is to build a cutting-edge product that is powerful and complete while also being beautiful and easy to use.

You'll contribute directly to this mission with a team that fully supports you to do your best work. You'll join humble but fiercely ambitious people like yourself, who also take great pride in what they do, working in a culture built on friendship, transparency, and above all, looking out for one another. You'll have endless opportunities to learn and grow professionally in a fun, fast-paced, and open environment. Plus, you'll get to make your mark at a rapidly-growing company positioned to completely reinvent a multibillion-dollar industry.

We're looking for engineers (junior and senior) for all our teams Back End, Systems Engineers, Front End, Full stack and QA.

Our current tech stack:
Scala, Go, JavaScript, TypeScript
PostgreSQL, Redis, ElasticSearch, Cassandra, AWS SQS, AWS Kinesis
Docker, Terraform, AWS Lambda, Serverless Framework
Jenkins, Grafana, Prometheus
AWS & Linux

If you can't find a suitable job but you are curious about Tray and want to join a top team, please have a look at our careers page: https://tray.io/jobs
I believe the parent’s point was that running a business that is self-sustaining is actually a difficult endeavour, and doing what looks like ‘squeezing customers’ from the outside is actually what the business needs to do to survive. I think this is a reasonable point, considering that no matter what price point many services are offered at, customers will still complain that it’s too high.

Leading me to my question: is your post satire, or do you really consider charging money for a service to be morally equivalent to murdering natives?
Location: Switzerland

Remote: Indistinct

Willing to relocate: Yes

Technologies: Scala, Python, Java, C++, Git, bash, Hugo, Linux, Gentoo, Apache Flink, R

Résumé/CV: https://www.linkedin.com/in/algui91/ (PDF: https://my.owndrive.com/index.php/s/wjPvcyv88zbolw4)

Email: algui91@gmail.com
Out of interest: How big of a threat is keeping diff files/versioned encrypted containers around when it comes to preventing breaking the encryption? I could imagine that the additional information will reduce the security of the information.
Waiting to be back in sync could take forever, plus you need a Sync Check Relay. Price of those is usually "contact sales team" and they don't work reliably if you don't need more than a couple dozen kW of power. (They're intended for 1MW+ installations).

Just shut it down, flip the switch and restart. Everything else will just be prohibitively expensive because it needs to be very safe.

If you get the phase wrong then you'll either reduce the lifetime of your components or the components explode after the nearest power plant tries to pump all available power into your poor inverter.
Zopa (zopa.com) | London + Barcelona | Visa ONSITE Relocation

Zopa is the UK's leading Peer2Peer lending platform. We are in the currently in the process of building a Digital Bank to offer new products to our customer base - Credit Cards, Deposits and Personal Finance Management, to help people feel good about their money again. You'll be working on brand new greenfield projects across the company.
Amazing offices in both London (on the Thames!) and BCN. We offer flexi-working, relocation, equity.

We are looking for:
Data Engineers, Data Scientists, React Developers, Java Developers, DevOps Engineers, QA (Automation), Product Managers.

Stack:
React, Typescript, ReactNative, Java, Kafka, Kotlin, Groovy, Scala, Go, Python, AWS, Docker, Jenkins, Kubernetes, Redis.

Feel free to reach out to me at aaron.smith@zopa.com or check out: zopa.com/careers

Cheers!
Sure, flat bitmap modes existed, but no game I ever worked on used them. Plus they weren't conceptually simple, either.

On PC there was Mode X, which was so convoluted that I'm grateful to have forgotten how it works.

Before that, on C64, you'd generally build the game background out of a redefined character set, but some of the color bits would be read from a different part of memory.

Setting a pixel in bitmap mode wasn't a walk in the park, either, due to the way the memory was laid out (8x8 blocks). Plus you'd have to write to screen memory this time to set the colors in each 8x8 block.

It was convoluted, is what I'm saying
CPU cache misconceptions, and the MESI cache coherence protocol
Find Crypto jobs in Switzerland
You're right, I should just accept that people are able to hurl insults towards me and start harassment campaigns and make pretty much any social media unusable for me. It's just words.

I should just ignore the thousand notifications with insults, I mean I can't block them can I? That would be some awful censorship.

Can't believe you actually compared this to a dog not barking at other dogs in another reply further down, how disingenuous.
Look into Credit Unions. Even 30 years ago, my CU's mortgages had no PMI.
Your right that AC is super easy to transform. But it’s quite easy to build generators that produce DC.

They’re frequently called dynamos and you find them on old bikes to power the lights.

With modern electronics doing DC-DC transforming is pretty easy (because modern electronics is basically magic). And the reason why high voltage DC transmission is a thing, is because you can get way more power down the same wire with DC compared to AC.

Many high voltage DC lines used to be high voltage AC that was converted to increase the transmission capacity without building more cables.
Me too.

The increase in complexity and lack of visibility from a DI system, vs what the manual wiring code would look like, can be immense.
Hello, fellow 3570K user - I've also been using one for 6 years now as my main (and gaming) machine. Had to upgrade my GPU once (HD6870 originally, now an RX 470) but I can even play Quake Champions without any problems, in addition to all the games that are a few years old. I've decided to evaluate getting a new machin in 2019, not earlier.
Visual Studio / C++ 6.0 (from 1998!) was by far the best C++ environment at least until 2013 came out (The last version I used was VS2012) - You never had to wait for it even in 2000, when I first used it, and definitely not later.

VS2005 (or 2008? can't remember), which I had to switch to because for x64 work, was unbearably slow and unresponsive in comparison -- although the general standards of responsiveness have come down, so today it might not be so bad (see, e.g., Atom, VSCode, everything JetBrains compared to old-guard Sublime)

From my only-slightly-nostalgia-tinted experience, I would correct GP's post to say "If you've never used VC++6 full ide" ...
I agree with what you wrote there, so they should justify by it not by just saying "it's a frequency issue"

As you said:

> Keeping the frequency sync is the easiest problem to solve
People are so mindbogglingly stupid that it hurts.

Every user of these so-called free platforms pay way more than $1 yearly for using them, via products they have been pushed and attention they have lost. If you're a potential high-wage earner, you're paying more than that in an hour!
Antergos most emphatically isn't a distro it's just an installer for arch Linux and quite frankly a poorly designed one that does not always actually work.

After the installer runs if it actually works you aren't left with something much different from a normal arch installation.

The actual distro developers have a lot of work to do as far as assembling a wide range of components and often writing their own like package management systems and recipes for building thousands of packages.

Its unsurprising that people writing 0.1% of distro badly doesn't require much work.
And that's why people write applications to understand and track your public cloud usage, like https://github.com/trackit/trackit ... Most people simply can't follow through what's happening in their cloud apps.
I still hold that part 1 (building abstractions with procedures) of SICP is not that good from a teaching perspective. The continual reliance on more and more obtuse mathematical formulae for the programming examples is sub-obtimal for engaging or informing a reader who does not have a strong mathematical background.

This is made even clearer in part 2 (building abstractions with data) which is an absolute masterclass in clear effective teaching. Part 2 is everything part 1 is not. It is approachable, immediate, ...tactile in its examples.

I've always wondered if the two section were written by the different authors.
I think they should both be paid more. In case you don't remember, socialism is about the state just taking control of the means of production, so where the money comes from is quite obvious.
Not tapes, but sane sys admins. Whoever leaves backups on the same subnet as the production servers, probably with the same credentials too, is NOT sane and should not be working in IT.
So, what should we do instead? The author gives some recommendations:

"Research to make deep learning easier to use has a huge impact, making it faster and simpler to train better networks. Examples of exciting discoveries that have now become standard practice are:

* Dropout allows training on smaller datasets without over-fitting.

* Batch normalization allows for faster training.

* Rectified linear units help avoid gradient explosions.

Newer research to improve ease of use includes:

* The learning rate finder makes the training process more robust.

* Super convergence speeds up training, requiring fewer computational resources.

* “Custom heads” for existing architectures (e.g. modifying ResNet, which was initially designed for classification, so that it can be used to find bounding boxes or perform style transfer) allow for easier architecture reuse across a range of problems.

None of the above discoveries involve bare-metal power; instead, all of them were creative ideas of ways to do things differently."

These seem quite fundamental (except for the last one which sounds like a favorite domain adaptation strategy from the author).

I'm in industry myself, but it's quite hard to come up with fundamental strategies. In particular I'm trying to merge nonparametric Bayesian models with deep networks. By enriching the latent variables in autoencoders to richer priors we might see improvements. Subsequently, we simultaneously need better control variates to do inference in more complex models. See my blog post on the overlooked topic of control variates: https://www.annevanrossum.com/blog/2018/05/26/random-gradien.... If we really want to be creative we need people from academia on board.
That you could do with a super capacitor, but not with a battery.

I know of some railway train setup, which is deployed in Saudi Arabia by Siemens, that uses a combination of battery and super caps to power the train. While the train starts it takes the sparking current from the super caps. While riding it will take the energy slowly from the batteries. While deceleration it will recuperate and will charge up the super caps, because they can be charged easily with a high current. So the super caps are used as a high available energy buffer with very fast charge and discharge capabilities. While the battery is only used during the times of less energy consumption. Also at the stations the super caps are super charged very quickly. With that concept, they can run the train the whole day with only 40% discharge of the battery. The battery is actually way smaller then in a Tesla.

This concept can be applied also locally. The problem: these super capacitors are way expansive so you need to design them to your specific requirements.
Aha, that's if you assume that you're applying for a position that you worked in before, but say you applied for a entry engineering management position and all you did before was develop software without leading anyone else. How should the interview go about from your perspective?
Ask HN: Intrapreneur or startup?
Hi,

Long time HN reader but first time poster here.

I work at a very large corporation, but I've always had the desire to create a startup company.

Currently I have a product idea that I strongly believe is valuable and worth to develop further, however it is an idea that requires a large upfront development before a minimum viable product can be released (5-10 persons developing for 2-3 years).

I could go the intrapreneur way, trying to push development of this new product inside the company, or I could quit and go for a startup myself.

The intrapreneur way is less risky with regards to personal income. I probably could convince the company to have a few people spend their time on this idea. It might also make it easier to connect with potential customers. However I think that if the product turns out to be succesful the personal financial rewards will be lower. I feel that people higher up in the company will gain financially more from my effort than myself.

The startup way is more risky: it requires me to find skilled people which I've tried before and had troubles with finding. Furthermore, it might be more difficult to connect to, and convince customers since it is a startup and not backed by a big company. However, in case of success the financial rewards will go more directly towards myself and will probably exceed the income I will get by staying at my current company.

Taking into account that the product requires a large upfront development, would you recommend the intrapreneur way or the startup way?
Code Shrew teaches programming basics by creating drawings and animations
First of all, SEO is more of common sense.
- It should start with creating a persona for your potential buyer/customer
- You need to know your potential keywords
- Analyse what your potential customers might search for
- You need to understand the intent of the search because there are different types of keywords, all keywords are not created equal. You need to hit those pure buying intent keywords but in a subtle way
- You need to do proper keyword research. I have created a keyword research template to help you all https://docs.google.com/spreadsheets/d/168CBn10UK31sMw-fnP8k...

Yes, in the end, content is the king. Give them what they want, they will come back again.
With your content, you need to make visitors stay for a long time and spend time on the site, Google loves sites/webpages with less bounce rate.

Make sure, you distribute your content periodically on the relevant industry channels and forums.
This uses the Nettle crypto library under the hood. Does anyone know how well viewed (or reviewed) it is? I'm curious to hear more from the devs on their reasoning for picking it (maybe it was the only one with the features needed and a suitable license?)

https://www.lysator.liu.se/~nisse/nettle/
This happened to me directly on Logitech's website. It's why I'll never buy their products again. I received a wireless headset that didn't keep a full day charge longer than 30 minutes. I had to use it plugged in (powering) 24/7. I submitted a 1 star review stating my problem and they removed my feedback without even telling me. It was just gone a few weeks later when I checked it, hoping they hadn't removed it.
It's more like (in good old RDBMS world)
'SELECT * FROM payments' and calculate sum on client
vs
'SELECT SUM(amount) FROM payments WHERE some_id = ?'

though they already had this sum precalculated
Reading this I was concerned that it would be written in Ruby. While Ruby is a reasonable language for server development, it has almost no data science community when compared with some other ecosystems.

I was very glad to see this is Python! Python has some of the best data tools out there, and a mature ecosystem for solving all the engineering problems that go along with a great data stack.
Yes. Because it represents how you've chosen to run your business. You are allowed to judge the business based on their previous behavior.
Control algos don't use machine learning yet for the most part, but base perception most certainly involves convnets.
It reminds me of the BASIC language shipped with the TI-83 calculator!
What is your idea on an opensource recruiting software like Workable?
Recently I have been thinking of creating an open-source clone of Workable.com, with hosted paid version, I am curious what is your idea on this? Workable is a great product but it has some limitations on the type of the features it can provide and also due to low cogs rate there has been always a good idea to compete based on subscription fee to take some small portion of the market share.
> * Ease of upgrading between versions. This is especially critical and important if you have long lived projects.

This is such a big deal and I can't work out how the JavaScript community has been operating under its 'break everything in a week' model for so long with such high traction.

Django has a sane, predictable release schedule. Django has LTS releases with years of support. I work in an agency environment where applications can sit running for years without being touched, and when new work needs to be done - I can't have my entire dependency tree falling from under my feet (or arguably worse, abandoned) because people have decided that backwards compatibility doesn't mean anything.

It's so so hard to not be cynical about this. The entire development world feels like it's more-so every day geared toward time-rich development teams pumping out software in a startup environment frothing over the next big thing. I have to account for every hour of my time, switching between / training other developers on new-hotness JavaScript frameworks is unjustifiable.
I feel like JavaScript is a bit of a special case, because there are people out there who, 5-10 years ago, did HTML, CSS, and jQuery, and called themselves "front-end developers", and then along came Node, so they read a few tutorials because it was just JavaScript, and they got some stuff vaguely working and then rebranded themselves as "full-stack developers" - throw in Firebase and Heroku and you have people who can store data and deploy applications to the web with only the most superficial understanding of what they're doing (and yes, that's how you end up spending $30K accidentally on Firebase and thinking that upgrading Angular might fix the problem).
Hal Abelson on Computer Science [video]