Perhaps it’s feasible that other trace elements in seawater, e.g. gold, uranium, etc. could also be economically extracted...
522 karma · joined July 16, 2010
Perhaps it’s feasible that other trace elements in seawater, e.g. gold, uranium, etc. could also be economically extracted...
Hardware is physical and can be quirky. Signals take real clock time to settle down and your CPU is probably much faster than the transition time. Hardware can and does have bugs just like software. A bad ground pin can make your hardware do “impossible” things.
You need to have much more awareness of the context your code runs in the further down the stack you go.
The expressiveness and power you get from being able to cast and solve problems in matrix form is similar to the lightbulb that pops up when one “gets” the relational algebraic power underpinning SQL.
I have to assume that it is fundamentally much more capable, but the video in the article makes it look (to the end user) quite similar.
My last two vehicles were
1. 2005 Chrysler Pacifica. Paid $16,500 in '07. Sold in '17 for $1,900. A few sets of tires, insurance premiums, and (gently) hitting a couple of deer put it around $225/mo over those 11 years.
2. 2009 Pontiac Vibe. Paid $14,500 in '11. Still have it and it's only needed minor repairs (knock on wood). Sitting around $250/mo TCO, but it's still worth a few thousand.
YMMV.
-- The Richest Man in Babylon
Like most of the issues, the solution requires experience to know when you are at the Goldilocks point (Just Right). This specific issue has a lot in common with managing database migrations in django or any other migration system.
The ideal situation is to create migrations that can always be rolled back, but sometimes this is not possible to do operationally. For example, a schema change that restricts a field from NVARCHAR to INTEGER can only be generically rolled back if all of the unconvertable data is persisted. This can be mitigated by structuring the database to avoid these dead-ends, and that really is only gained by hard-won experience.
The problem with undoing operations via new events is the same thing -- unless you have foreknowledge of this kind of problem, it is very easy to accidentally create events that perform un-undoable actions. A very simple example of a problematic event would be something that modifies a foreign-key relationship -- let's say it's a digital asset in a game and you want the ability to transfer ownership of the item from one player to another.
The simple solution is a event like SetAssetOwner(asset_pk, player_pk). This would set the item's player foreign key field to the player's primary key. Easy. However, you have lost knowledge of where the asset came from and cannot undo this operation. A better solution would be to make an event SwapAssetOwner(asset_pk, owner_pk, recipient_pk). Yes, the owner_pk is technically redundant, but it provides a check against someone trying to steal an item with a maliciously crafted SetAssetOwner event that performs no checking. Even better, this operation can be reverted by sending the same event with the owner and recipient arguments reversed. Since these properties are part of the event message, they will be persisted in the event history and all of the information to undo the event is self-contained.
I can go to google.com or HN because I type the URL into a browser and the page is displayed -- I didn't need to go through an approval process or present a security token or anything else to gain access.
Now, what if I type in a URL into my browser that happens to look like company.com/users/12345/purchases and it displays a page of information. Did I "circumvent" anything in this case? Did I "exceed" my authorized access? If so, what is the fundamental difference between accessing google.com and this hypothetical URL?
https://www.esri.com/en-us/arcgis/products/arcgis-for-person...
Normally an Advanced Desktop license with multiple extensions would run well north of $10,000/yr with an initial purchase price about 4x that amount.
A potential order of magnitude improvement hiding in the memory access patterns of your code makes this worthwhile information for a lot of devs.
1. http://brucefwebster.com/2008/04/15/the-wetware-crisis-the-t...
People always asked how I managed to answer the phone so fast. Electromagnetic Supplementary Perception, of course.
Are you OK with using the grid as a highly-reliable, ~infinite capacity power source to smooth over your uneven solar generation at a cost of selling your excess back at a discounted rate,
or
do you want to try and capture that discount yourself at the cost of having to buy, install and maintain your own integrated battery backup system?
Maybe the calculus works out in your favor for you, specifically. Maybe not. But it's good to have options.
In the Hardy Boys book “Hostages of Hate”, Frank Hardy’s girlfriend, Callie Shaw, is kidnapped and is able to send a secret message to Frank by blinking her eyes on a video recording.
Funny what sticks in your mind from a young age.
It’s at the point that other kids at her school ask her for custom slimes that she makes and sells to them for small $.
Chemistry and entrepreneurship ... could be worse.
“A Story About Magic” is black magic in action. http://catb.org/jargon/html/magic-story.html
“The Story of Mel” is not black magic even though no one else understood his program. http://www.catb.org/jargon/html/story-of-mel.html
How do we know that the Elon Musk of 3000BC didn’t just build a big obelisk for the lulz?
Probably a bigger question of the problems of inferring great significance from extremely few samples...
We avoid the dreaded, "What do you want?" questions around meals and the app's autogenerated shopping list has really helped us reduce food waste and avoid worrying that we're missing one or two ingredients when cooking a meal.
e.g. https://github.com/Esri/storymap-cascade
Almost everything they release is under the Apache license.
Just handing someone an expanded version of "implement good error handling" is not likely to result in a good product. Every project has nuance and subtle trade-offs -- the code review is an opportunity to teach juniors how to map abstract design principles onto concrete implementations without falling back to "cookbook / cargo cult" programming.
I want them to take ownership of their own code, and advance down the path of craftsmanship because I believe this results in long-term value -- both to them personally and to the project at hand.
This. I have a very short list of architectural must-haves that I use when evaluating junior dev's code at the start of a project, and not having robust error handling that preserves submitted form information is right up near the top.
It's an annoying design mistake with two input elements, unworkable with five, and just plain cruel beyond that.
What research is out there on general Affine invariant vision algorithms and techniques?
For context, my practical experience ended in the mid 2000's when "jittering" was a bit of thing along with some occasional closed form estimators based on basic linearization approximations.
Where people get into trouble is when they have a short problem space horizon and don't have a decent feel for the trade-offs being made and a reasonable understanding of how the "wrong solution" is related to the "right solution". That can lead to the creation of a hack-y, fragile and unchangeable system that can really limit progress in the future.