Hacker News new | past | comments | ask | show | jobs | submit | atjoslin's comments login

I use it for a very large monorepo to replace prettier. So much faster! Also have it run on save in my editor now.

Now linting full codebase on precommit and it’s faster than just linting staged files with prettier!


<3 <3 <3 <3 THANK YOU


to what purpose


grain.co


"Well, gee, that's a lot. I'd be really impressed if our team could get to `$GOAL x 0.75` in $TIME. `GOAL x 0.25` is a big ask, we'll have to see..."

Lots of under promising. Aggressively, even when you get tired of it.


I even used this for a family call the other day to clip someone's dumb joke and share it later with fam.


Cool, he got paid and all, but keep in mind that's $22M of yours and my tax money.

EDIT: Nevermind, I did not read the article before commenting. My mistake.


Isn't it from the settlement money?


Interestingly the settlement money still does a bit affect our taxes still.

Monsanto makes $80 million less in revenue this year due to the settlement. ~$80 mill less profit ~= $20 mill fewer taxes.


Correct me if I'm wrong, but they don't make $80M less, they just lose $80M from the amount they have made in the past (already taxed)


This would be counted as a loss for this years tax purposes. So they will pay fewer taxes this year.


Settlements that are classified as penalties are generally not tax deductible. Settlements that are classified as remedial/restorative generally are.

This was no doubt a topic of discussion and planning before the settlement was entered into. The article repeatedly refers to it as a "penalty", but it's unclear if that's colloquial or specifically informed language.


I doubt Monsanto pays an effective tax rate anywhere close to 20%. Further the people who receive the settlement pay taxes on it thus the taxpayer is likely better of.


Yep. I'm already sour against the IRS from just doing some tax calculations, saw the article title, and didn't even read the article before commenting! Edited my comment.


The reason most people tell me they use todos is, "you can't do everything up front."

I agree, but I hate TODOs. They're the worst form of keeping track of technical debt.

Just open a ticket! I like to have a tag/label called "debt" that I put these "TODO, bad implementation" type of problems under.

That way at least it's tracked.


A preferred method for doing this at Google is to open a bug, and then leave the TODO in the code with a reference to the bug number. This has the advantage that if someone comes by to refactor the code later, they'll have the chance to go look at the bug (possibly taking it and working on it, possibly resolving it as obsolete if the original issue no longer applies, etc).

Having the two-directional link between the bug and the code is quite useful, especially for what is probably the most frequent use I've seen for TODOs: "We could do this better, but the better way is blocked on circumstances beyond our control. Once those change, revisit this."


I actually like that - perhaps that allows you to implement blocking as well, for example: "TODO: X cannot be improved until Z & Y is complete.".

The projects I work on tend to have a very quick life cycle, so there isn't even a ticketing system in place other than the occasional post it note. There just isn't the time and the team is tight.


This is my preferred method, but if there is any sort of bureaucracy in place around creating a ticket then it's not a solution that gets used.


AngularClass knows what they're doing. This course is gonna be legit.


+1 -- I use Stout all the time. I don't have to rely on anyone's uptime except AWS's. Stout's just a "shortcut" for using AWS infrastructure that I have full control of.

With Surge, I'd have to trust some startup's build tool not to fail at a vital time.


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: