HN user
According to the article, this plant would employ 30k-50k people. The secondary effects of these jobs would be equally massive. While I would prefer an American company operating the plant, merely employing this many people would be a serious boon.
I'm guessing you were thinking mostly about financial and political self-interest (the things we usually classify as "greed") when you wrote this post. But I think there are other, equally important ways to be selfish.
For example, humans evolved to be social creatures. Interactions with other humans impact our body chemistry in dramatic ways. I want to avoid loneliness, so I selfishly hold relationships with others. I want to hear people say "thanks" to me, so I selfishly give people gifts. I want to be able to be righteous without hypocrisy, so I selfishly stick to my principles.
Just my two cents. There are a lot of different types of desire in the world. Who's to say that UBI wouldn't be in folks' best self-interest?
I find that you need to explicitly state your intentions ahead of time. Otherwise, people assume the worst, and get defensive right away. Then communication closes down. So my method is this: before I even ask the question, I couch it in nonthreatening terms. Usually, I start with a simple compliment. It doesn't even have to be relevant: "Hey boss, that new policy seems pretty neat. What made you implement it all of a sudden?"
I find this is effective even if you actually do want them to change their decision. Come in with a compliment, then try to lead them to recognize the flaws in the decision themselves.
It shouldn't be about faith. Every "crowd" has all kinds of people, and even the very smartest people aren't always right. By reading critically (and following up with research if necessary), you can decide what's right and what's wrong.
In my experience, H.N. comments have a lot of wrong. But when the content is good, it can be truly great.
I don't think it's either. "Scaling" refers to growing the amount of compute power you are using. This change falls into a different bucket, which is making more efficient use of the compute that's already available.
If they are running multiple Docker containers, the improved efficiency would allow them to run more containers per host computer. Maybe that's what they meant, although it's not really horizontal scaling either.
Zen Buddhism is a classic example.
Sorry, but the OP wasn't talking about ipfs at all. He was talking about Cloudflare.
Having said that, thanks for the interesting digression. You've made me want to try out ipfs.
Same deal when I flew United the past weekend. Samsung Note 7s were not allowed to be turned on or charged on the plane. I think they are taking their cue from the FAA recommendation [0].
This is especially bad for Samsung, I think, because it doesn't just affect folks with a Note 7 -- everyone waiting at the gate hears the announcement. Talk about negative brand associations.
Whether or not you use an SSG, I find the biggest hurdle is getting/making a good theme for your blog. It looks like this comes theme-included, which is actually a pretty big deal if you want to get up and running fast.
Like what?
Have you considered using https://pinboard.in? It's a great tool for bookmark organization using tagging. I have over 3500 private bookmarks on that site, but I rarely lose links or have issues isolating sets of links relating to particular projects. It costs something like $15 for an account, but there are no ads and your data isn't sold or shared if you don't want it to be.
Some mechanical keyboards let you configure this with DIP switches on the keyboard itself. My keyboard even came with an extra set of keycaps for swapping the caps lock and left control keys.
Yeah, it seems like "Another Day, Another Hack" is just the name of the series they use to cover security-breach-related news. It's unfortunate that it confuses the meaning of the article to imply that there was literally "another hack."
A desktop PC is more than able to do good speech recognition as long as it's able to train the model for individual voices. Getting good results without training the model for the user beforehand is harder, and you would probably never be quite as good as a cloud-based system.
A Pi, though, couldn't do well at all, just like you said. If I wanted to build a system like this for myself, I would target an HTPC form factor.
edit: Another possibility, which was explored elsewhere in this thread, would be to keep the listening device "thin", but have the ability to offload the processing to a machine in my LAN instead of one the "cloud".
As another "software engineer", I can say that we simply don't ever need a tool like Jupyter for our jobs. It's excellent for exploratory programming, research, and publishing -- but it's not really meant for software development.
Redux tries to enforce a convention that all application state is stored in a single object (the "store") and modified using a single pure function (the "reducer"). These conventions make it easier to reason about the application's current state.
Applications behave consistently because all state is stored in a single object, so it can't be desynchronized across components. Because all updates use a single function, it becomes easy to track and respond to any state changes by applying middlewares to that function. Things are more testable because all state is available for stubbing, and because the "reducer" is a testable, pure function typically composed of many other smaller, testable pure functions.
Things like time travel become possible because of the purity of the reducing function. Since it's pure, it can't modify the old state object (technically, it can, but it's against the rules). So in theory, we can undo any state change simply by loading the old state object from where it's being stored by some kind of history middleware.
While I agree with your assertion that debugging should ultimately happen in the head instead if in the IDE, debuggers can still be useful for console.log folks like us. Because they show you the values of all the variables in scope, a good debugger is basically the ultimate console.log, and can sometimes speed up the diagnosis process by allowing you to check multiple hypotheses in a single program execution.
Also, sometimes even just using console.log can cause bugs to appear or disappear. I recently encountered a bug which was almost impossible to diagnose with console.log, because the string returned by the .toString() call didn't correspond to the real object's actual properties. Of course, this is a rare case, but it highlights the benefit of trying different tools!
Who would use a beta version of a crypto product in a production setting?
Actually, Amazon already did -- one of the sample Lambda functions you can use is just that. It runs on a scheduled timer, and if I remember correctly, will alert using AWS Simple Notification Service, which can be configured to send alerts to your devices or emails.
I don't think there can really be a distinction between what art "should be" versus what art "is". You could maybe argue that a particular piece or style of art should be different, but does it really make sense to say that art should be something else?
More to the point, I think that definition is a little dissatisfying. By that metric, I have probably never created any art in my life -- because I'm not an artist with limited-edition work in a gallery. To me, that is unacceptable for a definition of art. Artistry is something more intrinsic to human nature than just being a thing made by an "artist" and put in an artistic context to be admired by hipsters and to confuse people.
Just do "tar -xf" for all your file extracting needs. The other command-line parameters are pretty much only needed if you want to override the detected compression format.
They lost nothing more or less than some years (or months?) of their lives.
It's true that it doesn't affect our day-to-day life. But I think it is important in the context of being an informed citizen (and, more fundamentally, an ethical person) to have an understanding of different moral systems and the philosophy of ethics. I recognize that this is a personal opinion though, so I won't try to force it on you.
Are you familiar with the Trolley Problem? [0] It's a simple thought experiment, which is intended to make you re-think whether murder is always an evil act.
Suppose a trolley is barelling down a track towards five tied-down people. If it continues, it'll kill them. But, you have access to a lever which would send the trolley down a side-track instead. But the side-track also has one person tied to it. By pulling the lever, you are effectively murdering that helpless, innocent person -- but you would save the other five. If you don't touch the lever, then you are just an innocent bystander who happened to see a quintuple homicide.
In this case, if you insist that murder is evil, and you refuse to be evil, then you have no choice but to let the five people die. But if you allow that murder is sometimes okay -- which is a utilitarian perspective, in the sense that you care more about the ends than the means -- then it becomes much fuzzier whether murder is inherently evil. Indeed, as soon as you give an explicit definition for evil, it becomes very difficult to defend it. The fact of the matter is, the good/evil dichotomy is false and artificial.
I just want to say, well done on giving your notice.
To someone who's never experienced it, it might seem like having no work would be great, but it's actually terrible for our sense of self-worth in my experience. A surprising number of people are too afraid to leave a position even if they feel it's soul-sucking. It takes serious guts to leave a steady job even if it sucks.
Good luck finding a more exciting position!
Great post, as an AD tutorial and as a (an?) Haskell exercise. Having known nothing about AD before, I feel like I have a good understanding of what it is -- as he says, it's so simple -- but I don't understand why the algorithm is so much faster. Just looking at the differentiator function and the AD function, it actually appears that the AD should take longer because it does more computation per step (both the function and the derivative). But it seems like every article or paper is talking about how to implement AD, not why the algorithm is so efficient. Does anyone happen to know of a good article or paper about that? Ideally, one just as nice and comprehensible as this!
Are you familiar with Ghost, the open-source Markdown-based blogging platform? It might suit what you're looking for.
Also, I haven't written any books, but I wonder if Markdown is the best choice for a canonical format. The syntax is lightweight but also limited. For example, it doesn't support tables, and doesn't differentiate between source code (which should be syntax highlighted) and literal text (which shouldn't). You could define your own extensions, of course, but that breaks the compatibility feature. I think reStructuredText (for example) might be a better choice, although Emacs' Org-mode is my personal favorite document format. I suppose that in the end, whichever's most comfortable for the author to write in is the best.
edit: I should mention that this is in reference to a technical book because I've been thinking about technical writing lately. It just occurred to me that you could be writing the type of book that doesn't need tables or source code, in which case Markdown is probably perfect.
It's a good point that a lot of editor latency issues aren't specific to typing. One thing that has always annoyed me is if an editor has slow find-and-replace for large files or projects.
I also find it interesting that you claim that humans don't notice latency under 100ms as though it is established fact, considering the OP spends basically the whole first section trying to debunk that incorrect but commonly quoted belief.
That looks like a fun project. I like the idea of looking toward an improbable future goal for the sake of better understanding simple problems facing us today (like how to represent and compute semantics).
I think the really difficult problems for that project will probably be importing data into the model (i.e. semantic analysis of content) and scaling the model to a great enough extent for the real benefits of using a semantic structure to appear. The problem of defining a networked object model is arguably already solved, but I don't think there are any solutions that could scale to the extreme number of concepts and connections that such a system would require.
I also have to say, that site really made me want to use Smalltalk as a PIM for some reason.
I really like the idea behind Cycle.js, but I don't think it does a very good job explaining itself. The idea as I understand it is not very complicated, but the language is rather esoteric.
The main benefits of Cycle.js in my eyes are:
1. Emphasis on a single entry point for event handling instead of a million separate event handlers. This is similar to the idea of the "Dispatcher" in Flux -- it's a central handler that manages all user input. But the Flux dispatcher has a specific purpose, whereas the main Cycle handler is more generic (which is, in my opinion, preferable).
2. Use of reactive programming, which is an extremely powerful paradigm in asynchronous environments like the browser. It takes a while to wrap your head around reactive programming but once you do it's absolutely fantastic. The only concern I would have here is that Rx.js adds overhead that might be unnecessary in some cases. But then I guess you would just use a more lightweight framework., so it's not exactly a criticism of Cycle.