Hacker News: noobiemcfoob

New comment by noobiemcfoob in "Google Begins Testing Extension Manifest V3 in Chrome Canary"

noobiemcfoob — Mon, 11 Nov 2019 23:15:56 +0000

The only feature keeping me on Chrome is web bluetooth.

New comment by noobiemcfoob in "Modern Data Practice and the SQL Tradition"

noobiemcfoob — Fri, 08 Nov 2019 18:27:09 +0000

You'll have dumped it into a strict database, giving yourself a false sense of order and organization. But later when you need to query that amorphous data, you might be able to use OPENJSON or something else, but a NoSQL solution will have been built to handle this type of query specifically with utilities like key exists and better handling for keys missing or only sometimes being present.

New comment by noobiemcfoob in "Modern Data Practice and the SQL Tradition"

noobiemcfoob — Fri, 08 Nov 2019 17:31:10 +0000

Then argue honestly and work to steelman other's arguments. To address your point, I'd hardly consider IoT platforms to be a "narrow" usecase. Smaller than the whole of computing, surely, but it's a growing field. The reality is that more and more devices will become available that generate all sorts of hard to predict data. Being able to handle those easily will be a large strength for platforms going forward. Dropping this hard to predict data as JSON into a RDMS will certainly come back to haunt you in 5 years.

New comment by noobiemcfoob in "Modern Data Practice and the SQL Tradition"

noobiemcfoob — Fri, 08 Nov 2019 17:22:20 +0000

What's wrong is that you asked for any usecase and then critique one because it's not broad enough for you.

New comment by noobiemcfoob in "Parse, Don’t Validate"

noobiemcfoob — Fri, 08 Nov 2019 17:20:06 +0000

It's hyperbole. A lot like systems that require hard type declarations for each and every function. The advantage of type systems is performance. Any correctness guarantees that come along with it are nice sugar but hardly the point and often misleading.

New comment by noobiemcfoob in "Modern Data Practice and the SQL Tradition"

noobiemcfoob — Fri, 08 Nov 2019 17:13:58 +0000

I've built IoT platforms where data from any device must be accepted. This is largely where my preference for NoSQL comes from. A device created tomorrow will not have a schema I can predict or control. NoSQL allows the easy integration of that device while a traditional database will at worst require a migration for each new device you want to support.

New comment by noobiemcfoob in "Modern Data Practice and the SQL Tradition"

noobiemcfoob — Fri, 08 Nov 2019 15:13:33 +0000

>use Elasticsearch

Found your problem.

New comment by noobiemcfoob in "Modern Data Practice and the SQL Tradition"

noobiemcfoob — Fri, 08 Nov 2019 14:36:51 +0000

“Why didn’t we use an RDBMS in the first place? “

Because initial application specifications are sparse and definitely wrong. If your application is still up and running 5 years later and your data definition hasn't changed much in the past 3, then maybe refactor around an RDBMS. Designing around rigid structures during your first pass is costly. This is why there's been a rise in NoSQL and dynamic languages.

New comment by noobiemcfoob in "Parse, Don’t Validate"

noobiemcfoob — Fri, 08 Nov 2019 13:30:21 +0000

But as soon as you're using "Maybe", you're impeding much of a type systems strengths, as the article outlined.

New comment by noobiemcfoob in "Parse, Don’t Validate"

noobiemcfoob — Fri, 08 Nov 2019 13:24:33 +0000

It's better to assume all code could throw an error. No statement is safe. This becomes particularly important in distributed computing as resources may be offline at any given moment. It's from this perspective that type systems afford a false sense of security and appear to be scratching the itches of overactive Type As.

New comment by noobiemcfoob in "Parse, Don’t Validate"

noobiemcfoob — Fri, 08 Nov 2019 03:47:00 +0000

It throws an error. Errors are a type of behavior. Some of those error behaviors you can cope with. You catch those. Others you can't. You raise those and either the system can cope or it can't and you crash. What part is nonsensical?

New comment by noobiemcfoob in "Parse, Don’t Validate"

noobiemcfoob — Fri, 08 Nov 2019 03:21:04 +0000

I like the concept of encoding properties, like a boolean of non-empty, in an object.

Beyond that, this article further convinced me type systems are for the pedantic. A given function signature is impossible? Seems like just another strength of a dynamic language.

New comment by noobiemcfoob in "What SQL Analysts Need to Know About Python (2016)"

noobiemcfoob — Tue, 05 Nov 2019 01:31:27 +0000

It was both language and database theory, all focused on Oracle. IIRC, it was titled "Database Administration", but I remember having to draw out schema diagrams and learn all the particular arrow types (one-to-one, one-to-many, etc) and what different block shapes meant in the diagram. All that only to get into industry 5 years later and find no one goes beyond basic squares and maybe double-ended arrows in practice >.>

New comment by noobiemcfoob in "What SQL Analysts Need to Know About Python (2016)"

noobiemcfoob — Mon, 04 Nov 2019 23:09:24 +0000

A Data Analyst is a Data Scientist who can't prove Bayes Theorem.

New comment by noobiemcfoob in "What SQL Analysts Need to Know About Python (2016)"

noobiemcfoob — Mon, 04 Nov 2019 23:08:01 +0000

I learned SQL in high school as my first "programming" class, though that's more of a quirk of how I moved through the curriculum. This was prior to learning C++ and then transitioning to Python some years later.

New comment by noobiemcfoob in "Flood of Oil Is Coming, Complicating Efforts to Fight Global Warming"

noobiemcfoob — Mon, 04 Nov 2019 21:42:44 +0000

Perception is important. A lot of these decisions aren't made by people who sat down and wrote down the numbers to arrive at the rational choice. But if I think I have utility for a pick up often because I like to think I'm that rugged, diy type of person, I'll think it's rational to own a pickup and assume the relative prices get massaged away.

/I drove a pick-up for a number of years for this reason until hybrid crossovers became viable.

New comment by noobiemcfoob in "BrainNet: A Multi-Person Brain-to-Brain Interface"

noobiemcfoob — Fri, 01 Nov 2019 21:22:12 +0000

I believe some research out of Duke had already done similar things with chimps, but bringing it to humans is major. Each of these studies becomes a proof of concept for what "should" be true of the brain, but theories fall flat all the time. Each lays a brick in the foundation for building a true BCI.

I'm most excited that this was done with only an 8-channel OpenBCI headset, 16-bit, for the "Receiver". The "Senders" had a much stronger/better headset, but seeing open hardware show up in this is awesomely inspiring!

New comment by noobiemcfoob in "Ask HN: Who is hiring? (November 2019)"

noobiemcfoob — Fri, 01 Nov 2019 19:30:31 +0000

An update, Revenue Analytics will support immigration sponsorship for qualified candidates.

New comment by noobiemcfoob in "Ask HN: Who is hiring? (November 2019)"

noobiemcfoob — Fri, 01 Nov 2019 15:54:04 +0000

Revenue Analytics | Software Engineer | Full-time | ONSITE Atlanta, GA

Revenue Analytics is a SaaS company that helps big companies make big revenue decisions in pricing, products and promotions. Our analytics solutions drive millions in revenue uplift and eliminate wasted time.

We're hiring software engineers of all levels to build out a catalog of analytics products. Our software stack is primarily Python and orchestrated containers in AWS.

Unfortunately, we DO NOT offer visa sponsorship.

Apply at https://www.revenueanalytics.com/careers or email me with a cover letter and resume at lblackwood[at]revenueanalytics[dot]com

New comment by noobiemcfoob in "Show HN: HR code – Designed to be recognized by humans and OCR"

noobiemcfoob — Fri, 01 Nov 2019 15:51:36 +0000

The problem this is addressing is a code being impenetrable by a human. If your solution is adding a second (human readable) code beneath the machine readable code...you haven't addressed the problem. The user must still trust their reader to parse the code.

QR codes' reconstructability is a major strength that this lacks, but I'd bet there's a way to expand this to include ECC around it, much as QR codes can.

BUT...OCR is quickly advancing, so the need for a specialized code a specialized machine can read will diminish over time anyway.