skysight-inc/HackerNews huggingface dataset:
Hi HNers,

It's been awhile since we posted here about our release of CoinHub[1] and everyone gave some amazing feedback. Since then, we’ve expanded to build our own data network because we grew frustrated with the lack of real-time pricing, news, and social posts. Most of the stuff out there is polled and could be up to 15 minutes late. So we’ve launched Blockmodo[2].

One thing that we had a huge issue with is keeping track with all the coins that are in the market. We decided to open source our entire token database:

https://github.com/Blockmodo/coin_registry

We’ve spent hundreds of hours curating information on hundreds of coins and we wanted the process to be a community process going forward. Let us know what you think!

- Blockmodo Team

[1] https://news.ycombinator.com/item?id=15403495 (New Version Soon)

[2] https://www.blockmodo.com
1) Power industry magazines, regulated utilities, mainstream newspapers, and others have
2) This source, regardless of bias, is reporting published public price information for long-term contracts, and comparing said published price information to other published price information. So what's your objection beyond the focus of the site?
I would go so far as to suggest that if you need a debugger, you're probably doing it wrong.

I have found that code that needs a debugger is code that is written in an extremely stateful fashion.

The very reason why debuggers exist is to deal with code that has a dozen variables book-keeping complex state that you need to track closely to figure out how something works (or why something doesn't). Debuggers even have "watches" to track something closely so that it doesn't change underneath you, when you aren't looking.

To me this is a code smell. I would suggest that instead of using a debugger, we ought to be composing small functions together.

Small and pure functions only need an REPL to test.

Once you make sure the function is behaving right, you can almost just copy paste over the test cases you ran in your REPL into unit tests.

The simplest way to enforce this discipline is to do away with assignments, and instead constrain oneself to using expressions. This forces one to break code into smaller functions. Code written this way turns out to be much more readable, as well as reusable.

I suggest that we eschew the debugger in favour of the REPL.
Adding Location to CNN layers helps in tasks that benefit from location
Just Code Challenge
Migrants, not immigrants. There is a difference.
PG&E has an option where you can choose to have 50% or 100% of your power come from solar:

>...When you enroll, PG&E will purchase additional, new solar resources to meet your electricity needs as well as those of other participating customers.

As you might have guessed, you pay a premium for his option:

>...Your monthly electric energy statement will include a charge for the solar power you are purchasing and related program charges, as well as a credit for the standard generation you are no longer purchasing. Today, the net of these charges and credits is a premium.

https://www.pge.com/en_US/residential/solar-and-vehicles/opt...
Why does it have to be electric heat? Natural Gas is doing a good job right now. Let's work on supplying electricity, for things that require electricity first. When we've moved away non renewable energy sources for electricity generation, then move onto the heating issues in colder climates.
Not everyone wants to see their software used. Some want to see the ideas in the code be used elsewhere. In that case the code is meant so others to study and understand.

You can see this in software papers where the algorithm is described by pseudocode, or only the core part of the algorithm is shown. Presumably the rest of the code is obvious to others in the field.

Releasing non-portable source is a step above that common practice.

I've used Autotools. I've contributed to Autotools. I agree that it's a steaming monstrosity. I never want to look at an m4 macro again.
Cloud Software for Rental Property Managers – Free Open Source, Online Demo
Whenever I get bored at my job, I read a couple of Raymond Chen's blog posts, and I am reminded that I am actually very happy that my job tends to be boring. ;-)
I've been waiting to get a new MacBook until they fix the keyboard issue. Any word on that with these newer models? Or are they doubling down...
Hawaii post-Cook ended up losing a lot of its population, because of that and other immigration it began to lose its culture. Other culture loss came fron Westernization and Christianity (Missionaries), the Hawaiian language itself was on the decline because of suppression until a renaissance in the 1970s.

The distinction of Hawaiian in reference to native people is a only made off the islands. To anyone from Hawaii or familiar with it calling it a Hawaiian shirt literally is wrong in our understanding of the word.

To try and spread that understanding of Hawaiian as reference to native peoples is to spread the knowledge that Hawaii is a multiethnic place with distinct native culture alongside its American, Asian and other Polynesian influences.
is the expense of desalinization the electricity? Which would go down with adoption of solar?
Right but then there are other non-trivial things that you have to spend on that you wouldn't on non-AWS.

And really there are very few hints that are non-trivial and not a problem on non-AWS either.

In the end, AWS is still more expensive time and money wise, it's just a question of whether it's worth it and what you want to spend your time on. (For me, spending it on the AWSy things is not interesting)
HPE supercomputer will help simulate mammalian brains
Elastic.co X-Pack has machine learning for log anomalies and people buy and use that stuff. Has anybody direct experience with that?
I would never in a million years, as a developer, give my personal phone number to a client. That's probably why.

I get the same issue where I work. The client states that "everything is broken," but it often turns out that their own servers are down (or sometimes our API guys made a breaking change and I wasn't informed, but that's not common anymore). I find this stuff out when I get to work in the morning, because they certainly aren't calling me directly.
> Laws like that tend to spill over into the legal migrant community.

If / when that happens, OP would then be correct in his claim. Until then, he is incorrect.
I'd assume they take issue with the racism and the opposition to the rule of law.

Although I cannot imagine Americans being happy that racists opposed to the rule of law are cowering behind their constitution.
Oh, sorry. I thought we were discussing this in good faith.
If the keyboard hasn't changed significantly I'll stick to my 2015 MBP for yet another year.
Netflix’s app is getting a cool new feature, but only on Android
I was thinking the same thing. The gigafactory isn't mention in this, but could there be synergies with Tesla's (somewhat shady... pun intended) acquisition of SolarCity?

These sorts of installs aren't exactly the same thing, but maybe SolarCity needs to pivot to from distributed consumer to large scale utility.
Absolutely right! Which is why I am connecting directly with the project developers. Also, I specifically built it to run over Solidity source code. As opposed to EVM bytecode like other tools. Only 1% of contracts have their Solidity code public on Etherscan. Making this accessible to 100% of the original developers and only 1% of attackers, should limit it to white-hat uses.
I'm not an expert, but my understanding is that WASM has two formats: a text-based format called WAT, and a binary format called WASM.

In order to run the code in the browser, the code will have to be compiled to the binary format.

So where WAT comes in is your methods for producing WASM files now become one of the following:

Source in <otherlang> -> WAT -> WASM

Source in <otherlang> -> WASM

WAT -> WASM

So the human-readable WAT can either be used as a compile target for another language, which can easily be compiled into WASM, or you can write the WAT manually and compile it. Alternatively other languages might be able to compile directly to the binary format, skipping WAT representation entirely.
I too was considering to remove that, I probably will!
You have to read a bunch of news articles and keep an eye out for articles that actually include numbers. I don't know of any public databases aggregating that sort of information. There are commercial services that sell data and reports.

Keep in mind that solar electricity, like any form of electricity generation, has location-specific and project-specific cost factors. Building any form of power plant is cheaper in China than in Germany. Solar power prices in Nevada are almost always going to be cheaper than in Michigan, because even if the construction costs are the same, the arrays will get more sun per year in Nevada.
FCC Proposes Changing Comment System After WSJ Found Thousands of Fakes
Oh no you're fine. I wasn't criticizing your explanation, just prefacing that I'm pretty ignorant with this stuff. But I find what you're building very interesting.
>Houses built to the German Passivhaus standard would do just fine in Ohio. I used to live in Ohio and Western Pennsylvania, so I should know. There was one Minnesota church built with polystyrene panels that had to start running air conditioning in the middle of winter, the insulation was so good.

You'd have to level most structures and rebuild from scratch to manage that in large parts of North America to make a difference.

Never mind the fact heaters aren't the only thing that use electricity at night.
Sure, many communities have that problem. But I think there are at least some where that would not be the case anymore if they raised their tax rates.
I think that disassembling WebAssembly is easier than trying to make sense of a highly minified/obfuscated JavaScript bundle. The time of easily readable web code has been dead for quite a while now I would say.
While we probably will always have to debug, and if not the "code" it will be a specification formal enough so that it can be considered code anyway, there are different ways to approach its role within the lifecycle of software development: on the two extremes, one can "quickly" but somehow randomly throw lines without thinking much about it, then try the result and correct the few defects that their few tries reveal (and leave dozen to hundreds of other defects to be discovered at more inconvenient times); or one can think a lot about the problem, study a lot about the software where the change must be done, and carefully write some code that perfectly implement what is needed, with very few defects both on the what and on the how side. Note that the "quick" aspect of the first approach is a complete myth (if taken to the extreme, and except for trivially short runs or if the result does not matter that much), because a system can not be developed like that in the long term without collapsing on itself, so there will either be spectacular failures or unplanned dev slowdown, and if the slowdown route is taken, the result will be poorer as if a careful approach would have been taken in the first place, while the velocity might not even be higher.

Of course, all degrees exists between the two extremes, and when going too far on one side for a given application is going to cause more problems than it solves (e.g. missing time to market opportunities).

Anyway, some projects, maybe those related to computer infrastructure or actually any kind of infrastructure, are more naturally positioned on the careful track (and even then it depends on which aspect, for ex cyber security is still largely an afterthought in large parts of the industry), and the careful track only need debugging as a non-trivial activity when everything else has failed, so hopefully in very small quantities. But it is not that when it is really needed as a last resort, good tooling are not needed. It is just that it is confined to unreleased side projects / tooling, or when it happens in prod it marks a so serious failure that compared to other projects, those hopefully do not happen that often. In those contexts, a project which need too much debugging can be at the risk of dying.

So the mean "value" of debugging might be somehow smaller than the mean "value" of designing and writing code and otherwise organizing things so that we do not have to debug (that often).
Oh sure, but I still wouldn't feel happy telling my shareholders that circa 75% of my product volume could disappear. And if that happened it would necessarily leave Cortex-A vulnerable (the Innovator's Dilemma in action).
Is there anything specific about that source besides the name that increases your skepticism? By that logic, one could say that anyone posting under a pseudonym containing "sol" shouldn't be trusted when they comment on a solar topic either.
Won't upgrade a single Apple product in my house until we get a resolution on MacBook Air. We are already evaluating leaving Apple products due to their complacency and won't be upgrading until we see movement on pricing and product development regarding the MacBooks. It's a sad state of affairs when you are waiting 3 years to update and you can't because your vendor of choice refuses to update your product category.

Hopefully they sort things out before we commit to a switch in early 2019. We aren't the only ones either we've had friends leave already and some are either waiting on us to blaze a path forward or are already planning to leave the platform.

I think Apple needs to seriously consider the long-term impact to their business of losing their major platform advocates; from artists, to developers, to technology savvy people that have a dramatic affect on the spending habits of others. Myself alone have easily and directly impacted about $50k worth of consumer spending, not a lot I know, but I'm also confident I'm not alone and this is a trend that is going the wrong direction.

Just thought I'd share where I'm at and those in my circle.

Also of you are imminently switching or have switched I'd love to know what you switched too and why.
I actually meant the opposite : most companies do terribly, and then smash some buzz word lipstick on that pig.
I think non-AWS still comes out in the end.
According to the article this is one of two places in the entire country making these ladders.
It probably is a waste of time, unless time is not a critical factor. If time is not a critical factor, it'd be a premature optimization to bother with a kiln.
For those using iCloud, another simple trick is to

alias n='vim ~/Library/Mobile\ Documents/com~apple~CloudDocs/Notes.md'

Then just type

n

to access your scratch pad. All nicely synced between devices.
Name constraints are a thing. Local CA should be constrained to signing only local names (roughly matching dhcp domain-name/domain-search options).
It strikes me as some type of attribution error. Not the FAE we all know, but a different or more general one. As in, results are not attributed to the cause.

But in the antibiotics example, it's the other way around. The results are ignored in spite of the cause ("I feel better, therefore I'm done"). That one could also just be regular old ignorance, but that's a boring topic of discussion.
My impression with this sort of thing is that the restrictions aren't because the people administering the program are worried about cheating, but because they're worried about cratering the local agricultural economy.

If everyone is able to buy rice airdropped in by a richer government or charity for a token amount (or free), it becomes very difficult to support yourself as a local rice farmer. If only a subset of the population which was previously unable to buy a significant amount of rice is able to do so, it doesn't affect the local rice market.

The misdistribution mentioned at the beginning of the article is a worst possible case: the poorest people not given their cheap rice are unable to afford enough to eat at all; people who may be hurting but aren't the worst off get cheap or free rice instead of buying rice they might (barely) be able to afford from local rice farmers.
Yes, this is a good idea, just expensive.

There are both passive and active options.

You need to drill pretty deep and have multiple wells, or have alot of land surface area and excavate (not too deep though).

Other option is using water from a well or spring and dumping that water back into another well or stream (with an increase in water temp.).
Seems like just new processors for the macbook "pro" .

The iPad pro 11 inch could be interesting though. It doesn't have a keyboard so Apple shouldn't be able to mess it up.
You'd think but photovlotaics have already been targeted as far as importing into the U.S., counterveiling and anti-dumping duties and what not.

They dodged this recent tariff change that took effect this week as 8541.40.60 tariffs currently aren't included in this tariff war with China but they could see more aggressive action.
> Only a debugger can show you the steps and conditions involved that lead to that invalid value.

No. Static analysis can and is actually what is used most of the time. Either with an automated tool, or with your brain.

Of course debugging is also needed, but the right mix between the two is needed, and you are actually doing it even if you use a debugger a lot (at least I hope so, otherwise you are probably not fixing your bugs correctly way too often).
The distinction of Hawaiian as a colloquial reference to anything from the state of Hawaii is made only outside of the state itself.

I can't change the way English itself works so there will always be that meaning, but to anyone from Hawaii, that distinction reminds us that native Hawaiians are distinct from the people of Hawaii today.

The Hawaiian culture has had its fair share of erasure and suppression. To make the distinction is an attempt to honor and remember the unique identity of native Hawaiians.
It's only human-readable like disassembling a binary into assembly code. https://webassembly.github.io/spec/core/text/index.html Whether you can make heads or tails of the code in that format depends on how friendly the compiler was that produced the binary.
Apple mocked Microsoft as an underdog ("I'm a Mac, and I'm a PC"), and it worked. They don't mock Microsoft now.
I almost sympathize but

1. Maximum cert lifetimes are falling, once upon a time you'd just pony up the cash and get five years. A year ago it was 36 months, for a few months now it's been 825 days, and there is downward pressure. So you are still going to need to renew this cert, and that means...

2. You can and should automate. Imagine buying a device in 2018 that expects you to manually input an IP address because "Eh, we could do DHCP but this was less effort (for us)". That'd be crazy right? Time to feel the same way about certificate automation.
You can look up Locational Marginal Pricing (LMP) data. Some Independent System Operators publish the information online. It varies pretty widely by region, and by time of day, time of year, condition of the grid, etc.

ERCOT: http://www.ercot.com/content/cdr/contours/rtmLmpHg.html
CAISO: http://www.caiso.com/PriceMap/Pages/default.aspx
MISO: https://api.misoenergy.org/MISORTWD/lmpcontourmap.html
Let’s push for self-signed certicates everywhere ! Let’s do Trust On First Use like SSH and now we’re done with all this certificates authorities bloated bureaucraties
It's a shame that there isn't the regulatory flexibility to subsidize desalination plants, because desalination plants are sort of like insurance policies in that you usually don't need them that much until a drought hits and then you really wish you had them.

That sort of long term risk averse thinking is exactly where the market economy needs to be supplemented.
Debuggers help to isolate _where_ code breaks as much as what state it was in when it broke.

Seeing that fn1 breaks on DataB is not as useful as seeing that fn1(f2(DataA)) is the actual error.
It's not better than google
I found a good TED talk on depression
Also:

https://caret.io/
https://typora.io/
They were already breaking things into separate services. They violated DRY by putting the same or similar code into all of them. Then instead of cleaning up the DRY violations by refactoring into a shared service or refactoring into a shared library as a static asset, they factored it out into a mushy shared library still in lots of flux.

Whether they were wanting to factor into another service with a defined and mostly static API or a common library with a defined and mostly static API, it was a failure to factor common code into an amorphous blob that gates the release of all the other services. Instead, they've de-modularized the code and called that a success.

If you're drawing hard lines between services and having them talk to one another, having one of these models for at least parts of that makes a lot of sense:
* filter system of the flow-based nature
* REST API that does a transformation and returns transformed data
* message broker with producer/consumer model where the consumer of one queue does a transform and puts the data into another queue
* a full actor model
* a full flow-based model
Facebook Opens Its Servers to Scientists Studying Fake News
Given that they are -electric-, I would think they’re thinking of stealthy operations. For ‘regular’ military use, noise and pollutions are less of a concern than for civilian use.
interviewing is only a small part of the picture. mvp has so eroded the notion of correctness that whole organizations don't even look for bugs anymore.

try upgrading the dependencies. wrap the service in a harness to make sure it gets restarted when it fails. forget about proactively looking for bugs, wait until they come in, and if you have time that week before they slip into the 'stale - never to be addressed' pile, spend a few minutes trying to reproduce and mark 'works for me'
Slightly off topic... Interesting thing about solar in Utah (maybe everywhere? Not sure about the specifics): Utah gives every land owner pollution credits. They're allowed to pollute X units worth per year or something like that. Depending on certain criteria you're allotted a certain amount of credits. The problem is, these credits are transferable. So if I, for example, don't pollute, I can sell my credits off to someone who wants to pollute more than average.

Something (I think is shady) some companies are doing is selling solar for really cheap in dollars, but they subsidize the cost by selling it for credits. Average Joe is going to think he's polluting less, however since he sold off his pollution credits, his solar purchase has authorized someone else to pollute for him. Netting us nothing in the end.

(not an expert, so I may have misunderstandings and be oversimplifying things, but the point should be easy to understand)
Remember for a couple of years in the early to mid-'00s when there was a Cambrian explosion in iPod models?

iPod with Photo, iPod with Video, iPod with color displays, Minis and Nanos with radically different hardware form factors with each iteration. Upon revisiting, it appears that the photo-color-video iPods were all variations of the original, and released in successive years, but it still felt like a dizzying array of different device types, at least to me at the time.

It feels like all the emerging new form factors are doing the same to iPhones and iPads, to some extent. Both the iPhone SE and 5C feel like one-offs, evolutionary dead ends. The inconsistency in size between the first and second gen smaller iPad Pro's. The product lines, when looking at the changes from year to year, feel like a jumble. Not as much of a mess as from other companies, of course, but still a little reminiscent of the iPod years. Doubt it will affect the quality of the products or the bottom line, but still messier than it used to be.
Thanks. It does break the code doesn't it, but I'm planning on implementing a magnifying glass: https://github.com/browsh-org/browsh/issues/33
Ok, fine, rice is unlimited and your idea is great.