skysight-inc/HackerNews huggingface dataset:
I was curious about the details of this, so I looked it up.

There's a 15% excise tax statewide in CA. It used to be a straight 15% on top of the sale price, but now it's calculated based on the average market price for an arm's length transaction.[1][2] This is usually calculated based on the wholesale price plus a markup of 60%.[3]

On top of that, there's (normal) sales tax applied to the whole purchase, including the excise tax amount.[2] In California, that means a statewide sales tax of 7.25%, plus county and sometimes city sales taxes that can add on an extra 0-3.25%.[4]

In places with very little additional county and city sales taxes, e.g. Newport Beach[5], that means paying 15% excise plus 7.75% sales tax, for an effective total retail tax rate of 23.9125%.

In places with higher county and city sales taxes, e.g. Santa Monica [6] that means paying 15% excise plus 10.25% sales tax, for an effective total retail tax rate of 26.7875%.

San Francisco is on the lower end of the middle of the pack with a sales tax of 8.5% [7], so that means the effective total retail tax rate is 24.775%.

Of course, there are other cultivation taxes, use taxes, special local marijuana excise taxes and other permitting costs that apply to cultivators and distributors and retailers that may get passed along to customers[8][9][10], so you could say that "total taxes" are closer to 40%. But most retail buyers are paying about 24-28% on top of retail list price in sales + excise taxes.

Note: Prop 64 made it so most medical cannabis sales aren't subject to sales tax, so medical users only have to pay the 15% excise tax. [8]

[1] https://www.cdtfa.ca.gov/formspubs/l537.pdf

[2] http://www.cdtfa.ca.gov/industry/cannabis.htm#Retailers

[3] http://www.cdtfa.ca.gov/industry/cannabis.htm#Facts

[4] https://smartasset.com/taxes/california-sales-tax

[5] https://www.avalara.com/taxrates/en/state-rates/california/c...

[6] https://www.avalara.com/taxrates/en/state-rates/california/c...

[7] https://www.avalara.com/taxrates/en/state-rates/california/c...

[8] http://www.cdtfa.ca.gov/industry/cannabis.htm#Started

[9] https://www.latimes.com/projects/la-me-weed-101-tax-location...

[10] http://blog.margolinlawrence.com/all-about-california-cannab...
And that only covers the physiological aspects of things, not counting other aspects (lack of social interaction, lack of meaningful work, etc)
Eh its a tech company. Bonuses usually make their way down to the lower ranks too.
In all fairness that does assume you don’t care about test driving etc. but in general if you don’t have dealer financing needs, are happy to do a private sale or donation for your trade-in, and know what you want and will pay, the dealer experience is mostly just mildly annoying even if you buy a car from one.
Russia Tests 27-Mach Hypersonic Nuclear Glider
How is that a problem? The great recession bailouts were paid back with interest, and FDIC insurance is a feature not a bug.
This is basically the style that rust sort of forces you to write in with allowing shorter forms where the compiler can automate checking that all error states are accounted for.
Great article, but the takeaway is something so profound I fear a lot of people will miss it entirely when getting into the details.

It is:

Understand your tools.

And a second but equally important takeaway is:

Use the least amount of tooling to implement your functionality.

If you understand your tools and you use the least amount of tooling in order to implement your functionality, your website or app will be easier to maintain, more performant, possibly more secure (less code = smaller surface area of bugs and other problems to exploit), and it will train future developers in a more sane art of programming.

I recently inherited a codebase that was a monstrous combination of a Rails backend broken out into multiple namespaced modules + a giant grabbag of service objects + a React front-end with a shocking number of various components — all to accomplish a relevantly small number of basic web app-ish things. (And to top it all off, it was a failed product and I'm only working on it now because a biz dev friend of mine had purchased the product from the original devs.)

All that extra "web-scale" work…for a product that didn't even succeed. They probably could have halved their dev time with a vanilla Rails app and some simple JS sprinkled on top (Stimulus for example), it would have worked perfectly fine, and they would have proven the app in the market (or not). Wait to get a thousand paying users — THEN rewrite with whatever fancy-pants frontend framework and microservices backend you like.

We really need to do a better job as an industry of pushing back against complex tools and complex development processes until they're absolutely necessary. Don't reach for a jackhammer when a chisel will do just fine.
> There's somewhere down the line where people are going to be tired of seeing your ads and either flag them or not want to visit your site as they know what they are in for.

This happens. Personally, I do remember and sometimes blacklist companies that annoy me with ads too much. E.g. way before Groupon got known for being a force of destruction of small businesses, they pissed me off with retargeted ads, and earned a lifetime ban.
Thanks, it's just in "unreleased mode" yet. The idea is to merge all social networks (flickr, whatsapp, youtube, google photos...) in a single one, with granular privacy controls. Right now you can only upload pictures (it will save the originals too) and create private chat channels though.
Quake 3 Arena had a last-man-standing mod. I don't recall the shrinking arena aspect, though.
I'm a lazy vegetarian, not for animal cruelty reasons but for the bigger, self-preservation issues: artficial pandemic evolution, antibiotic resistance, pollution and climate change contribution.

If you don't get enough bioavailabile vitamin b12, depression is just one of the symptoms. I saw it in the dorms of my university of a few vegans who didn't manage their nutrition. https://en.wikipedia.org/wiki/Vitamin_B12_deficiency
Sure, if the quote is out the door, but it never seems to be from what I've seen.

This was "Here's the price excluding title transfer including delivery"
> I think the average person should be able to publish what they want (no matter how stupid) without specialized knowledge and without being censored.

I agree, it's an unfortunate consequence of monetary incentive.

There's tons of FOSS self-hosted alternatives for any typical centralized service, all of which could be bundled and idiotproofed and sold to average people. But no one is out there innovating and marketing it and pushing it to the mainstream (if the demand is even there - not likely)

Theres a few attempts, like https://nextcloud.com/devices/ , but I would have never heard of them if I didn't have a specific interest in finding open source alternatives to cloud services.
> Though, I suppose having an unused dimension only really hurts efficiency.

That might not be true as it might increase bias and thus might need a more careful hyperparameter tuning to avoid overfitting.
The comment:code ratio is higher than anything I write or that I’ve seen.

However, it does give me some comfort. When it’s not gamed, do other HNers also feel that a high comment:code ratio probably indicates quality?

There are reasons why this may be the case. (More thought, more time and a large team etc)

I don’t advocate using this measure to reward anyone because it would be gamed immediately.
Except I wouldn't call Haiku or ReactOS "research projects." Indeed, one of their goals, whether explicit or implicit, is to provide an alternative to Windows on the desktop.
The government is the people. At some point, the officials need to just get on with it.

The reality is fine-grained democratic voting on every issue does not scale to today's world. People do not have the time, attention, education and understanding to vote properly on everything, and when you add in personal biases, lack of risk management, short-term outlooks, majority power, and special interests; things break down completely.

Many of these things which could improve civic life do not really need a voting process. It's not a system for the people (not anymore) but stays around because it removes accountability and provides regulatory capture for the few who profit. Of course, as you say, the very people who do not take action are the ones that need to take action for this to get better. I do not have an answer for that.
Five Amazing Things We Learned About History from Ancient DNA in 2018
TV audiences were measured through surveys.

... and live metering services like Nielsen, who installed their own metering hardware in participating households' TVs and VCRs and polled them daily over a dedicated phone line.
I'm about 63%* sure the reporter is referring to revenue.

* made up number
Maybe so in this case, but it's likely many new users will read your post, and defaulting to a friendlier tone benefits everyone yeah?
While true, 3 people just making coffee is also something of an outlier.

The average Starbucks sells ~400 cups of coffee a day, but that includes a lot of very low volume locations with less than 3 people.
In your opinion what could be contributed by a sociology major to realistically avoid any of those scandals?
Right - I knew exactly what I wanted since I had driven the car as a rental.
Persistent access via an authentication token is a hell of a lot more reliable than relying on the user not navigating from/refreshing a specific page where XSS is present.
Try computing ECDSA by hand and we'll talk.
To underline this, the amount of money spent on emergency care (the kind where you might not have the opportunity to get an estimate) is in the single digit percentages, and may be as low as 2%.

https://www.politifact.com/truth-o-meter/statements/2013/oct...
These days they generally support the main element.
I hate to break it to you, but Colorado Springs has been worse in most ways, roads and otherwise, long before recreational/medical weed was legalized. They've had issues with crime and meth, for a very long time as well.
A code style with lots of verbose if statements? Go is the perfect language!

More seriously I’ve done this style unintentionally before in JavaScript for a similar situation with plenty of branching logic. Stuff that easily could have been have the lines but not as easy to verify by hand. I’m happy to see it being formalized for certain scenarios.
> But even without that, I think it's unethical to claim ownership to any part of someone else's body and tell them what they can and can't do with it.

No one's claiming ownership of the athletes body (because, first sale doctrine.) If they want to cut their skin off and sell the tattoo, that's not an issue.

Ownership of the copyright on the tattoo is not ownership of any part of the athlete's body.
If a friend gave me a free safe, and then a thief cracked it open easily due to a fragile lock and stole my money, I wouldn't blame my friend.
While I can understand the basic philosophy, it seems an unfortunate example to pick something that had 2 catastrophic failures out of 135 launches. Although, I suppose, neither of them were due to software...
Porting to a language supporting exceptions would be a huge simplification. But then maybe it would stop being a space shuttle ...
How about the bugs in IDEA? You try to refactor, and it does a search-and-replace even on text literals, messing up not just comments but strings. Sure, there is an option to disable that, but you have to use a special shortcut to bring up a popup to disable it, and you have to do it every time. Same feature, behaves differently when started from menu or from shortcut.. Then the where-used-list not working, just because, well it bugs out from time to time... For features i need, for the way i work, Netbeans is more dependable, and fun to code in. I see features in IDEA that are similar to Visual Studio, and its a bit funny, how they try to copy it.
I think it's likely to indicate low quality. Comments are for where the code wasn't clear enough.
By this line of reasoning, companies don't own the code their engineers write either. Art collectors don't own the art they paid for. Etc. What a bunch of bullshit. Have these people not heard of work for hire? The artists were paid for their copyright (in addition to the actual manual work). They no longer own the copyright. That's the whole point of the transaction. That's the only reason money was exchanged. No one in their right mind would get a tattoo they couldn't display; something the artist could really demand if they held the copyright. Does something this obvious seriously need litigation? That is some serious misinterpretation of copyright law. As bad as our copyright laws are, they can't possibly be this bad to allow these obviously bullshit cases to stand, can they?
Maybe a loose correlation? Highly commented code was probably not written under tremendous time pressure; uncommented code can go either way. Wrongly commented code is painful, though.

And then there's something I recall running into, a decade ago:

using namespace std; // using namespace standard
You may check out Panda, it allows you to add custom RSS feeds. https://chrome.google.com/webstore/detail/panda-5-news-inspi...
Terrible book. The concept is explained in two or three pages and repeated during the whole book without introducing anything new.

Watch a free YouTube review and go spend the money and time on something else.
The article only mentioned that the amendment was introduced by a republican and the current governor happens to be republican.

>Roll Call # 952 Yeas 106 Nays 1

http://www.legislature.mi.gov/(S(0jea3dr1fnip1bve0xixi4we))/...
Violates title guidelines.

https://news.ycombinator.com/newsguidelines.html
I actually would say it’s almost the opposite, if you’re writing clean, expressive code it shouldn’t need explaining.

And if your code is clean, you shouldn’t have a bunch of redundant comments explaining the obvious.
I think it indicates pride more than anything. If I write something that is just business as usual or commonplace my comments are pretty lacking. If it is something very interesting or that I am proud to have done, I usually write some very detailed comments. This probably correlates to better quality just because it was something I was interested in doing rather than shoveling code.
I think it's situationally useful. If I take the author of the OP code at their word, this is one of those situations.

Core, critical plumbing/logic at the kernel of business critical, long-lived applications, will be the source of my stress-dreams long into the twilight years of my life; in the form of a lack of documentation and a presence of organic growth.

To criticize myself quite bluntly: If the core code I worked on at work looked like this, I'd feel a great deal more comfortable in some of the changes/digging that inevitably arises.

I would never use it as an absolute metric; but I'd use the level of comfort e.g. a new dev feels when looking at something that might otherwise be a spiderweb and saying "Oh this makes sense" (As I do when looking at OP) as a north star for the most sensitive bits of logic.
The best Christmas presents are free and come from hacker news
Some code do require this style.

If the code is complicated, sometimes it's better to make it extra explicit than just relying on the reader's comprehension (including empty else blocks, for example)

Because in a nested A/B/C condition it is very easy to not notice what happens in the case where A v !B v C and/or why is it different from A v B v !C especially when some of those can't happen together (but then the code does "something" and "can't happen together" means "it will happen in that very weird case")
Extracting Permissions and Dependencies from an APK; a New Project
This style of code with an emphasis on branch completeness is the biggest virtue Go gets from the lack of exceptions.

I personally dislike that style since that level of detail seems extraneous for normal tasks, but when you need to write code with absolute assurances like this then preventing the stack from being unwound without an explicit return (or panic, because some stuff is just terrible) is quite helpful to inspect and insure you have full coverage.
Long comments tend to scare me because they often detail some horrific hack that I'm going to have to deal with.
"it became clear that we needed to ensure that every single condition was handled and accounted for in the code"

This is a feature of several (mostly functional) programming languages, e.g. Haskell. Fun to see that often people figure out that these types of concepts are a smart way to write your code. Too bad it usually means many people reinvent the wheel instead of learning about computer science history and other languages.
Nice. At some point one rolls up your sleeves and says "right, this part is important and needs to work and I need to be sure I have got it right" At that point space shuttle style works pretty well (usually for me I am writing some security / control dispatch for the umpteenth time)
Googles core products required them to hire people that could interview, hire, design, build, and deploy software. Along the way, they had many failures and learned a lot of lessons.

If my company’s core products or services are centered on let’s say acquiring surface and mineral rights, discovering hydrocarbons, and using the right technology for drilling, it makes practically zero sense for me to now also try to become an expert at maintaining servers, hiring top tier software engineer, etc etc. I don’t have the kinds of problems to keep them engaged nor do I have the budget.

Software is a part of the business insofar that it enables business, but it’s not ultimately what drives profit.

Many of the top tech companies outsource HR software or recruiting entirely, use travel and expense software software as a service, Oracle financials for payroll instead of writing it themselves, etc etc. Why? Because they want to invest their money and talent into the core areas that make them a profit.
League of Legends has been around since 2009, versus Candy Crush Saga in 2012.
There were many other close calls, most having to do with the thermal system on the external tank, which is what damaged Columbia. It was a known issue for almost the entire program.

As you said, nothing having to do with the control system.
Knuth allegedly attributes the stability of TeX to his literate programming style.
Better to make blindly throwing exceptions impossible.
Never split the difference can be a life changing book, at least for me it was.

I still have to put it to practice more but now I know that the tools are there.

Can’t recommend it enough. I would force everyone to read it every year if I could. That’s how good the book is.
I regret not bothering to put stupid/simple things on GitHub earlier than I did. In part because using GitHub is, in fact, particularly educational in itself. Getting used to using version control for your own stuff will make it drastically less painful when you are trying to follow the expectations of a large organization. I also find putting personal projects on GitHub encourages me to use best practices, like ensuring no personal data ends up in the code out of convenience and the like.

Building some sort of personal projects is an awesome way to force yourself to learn things (apart from digging in and helping with other people's projects), and I would encourage you to see if there's anything that would excite you to build, and then tell you to figure out how to build it.

Funny story, I studied for (and have my bachelor's in) game development, and I ended up choosing to work in the IT field, where I actually prefer for my Mon-Fri. (You've probably already realized this, but IT and dev have almost no shared skills whatsoever, and my degree was almost useless for my actual job.)

I've probably learned a lot more just screwing around with hobby code than I really did in school, and despite not being in class for it or doing dev for a living, I am writing more (and better) code than I was a year ago.

Lately one of the things that's often kicked off ideas/projects for me is the Succinctly ebook series from Syncfusion: https://www.syncfusion.com/ebooks It's mostly .NET-focused, but has a lot of very short, well-written introductions to a given topic or project type. I've only really dug into a couple of them so far, but every one has been a positive experience.

If you're trying to work for a FAANG (which you really shouldn't), you need to memorize all sorts of algorithms and related jargon mostly for the purposes of the interview, but for most jobs you just need to be able to look at a general thing you need to implement with code... and implement it with code.
There's nothing lazy in there, right?
The key is that modal number of contributors is probably 1.
In other news, physics textbooks are all wrong because infinite sheets and spherical cows don't exist.
I love this! It's the "jazz music" of software development. Something which breaks all the "rules" but does so purposefully and explicitly so that it can become better than the "rules" allow.

A naive look at this and my head is screaming that this file is way too big, has way too many branches and nested if statements, has a lot of "pointless comments" that just describe what the line or few lines around it is doing, and has a lot of "logic" in the comments which could quickly become outdated or wrong compared to the actual code.

Yet at the same time, it's probably a hell of a lot easier to maintain and manage than splitting the logic up among tens or hundreds of files, it contains a lot of the inherently complex work it's doing to this file, and it is so well and heavily commented that it should be pretty easy to ensure that any changes also keep the comments up to date (after all, any change without changing the resulting comments should show up like a sore thumb, and will most likely prompt the reviewer to look into it at the very least).
I comment to myself before I write code. It’s in English. Then I write code. So every line of code is commented by default.

I think this provides me higher quality, less bug ridden results. So if others use comments in this style I would tend to believe it does increase code quality.

If a line of code doesn’t match the comment, something is clearly wrong. ;)
In a world of pre-1990s, high-deductible, 80/20 insurance, this would happen less as the insurance company might not do the 800lb gorilla thing until the patient maxes their deductibles, and high deductibles give the consumer a strong incentive to negotiate directly with the provider.
That first link redirects to spam on mobile. I sure wouldn’t trust them with my credit card.
Orphaned currency: the odd case of Somali shillings (2013)
And with the beauty of pattern matching in Rust, it's usually very painless.