Not that it couldn’t be trivial in the abstract, but I’m struggling to imagine a use for a nested list item containing a table of blockquotes. It doesn’t seem at all surprising that a tool wouldn’t anticipate that.
Absolutely! The writers are generally not highly technically experienced, but have to produce highly technical documents that need to be regularly reviewed and changed for years at a time.
Yes. Questions like, "Should I work to 'do little things' intended to put a given coworker 'on an upward spiral'?" versus, "Should I insulate myself from or minimize blowback where any action is going to be received poorly because my incompetence is considered a foregone conclusion?" and, "How long should I remain at an organization where such things occur?" are all things that relate to decisions that are in your control—or at least might be, with enough of a forward-looking defense early on (if you fall into the group of those unlucky enough to need to ponder them).
Really, though, my comment was rather more intended to prompt introspective questions like, "Even if I'm personally on safe footing at my company, is it afflicted by this sort of thing in a way that impacts people who aren't me? And what can I do to either neutralize or minimize the negative consequences those people might experience?" (Readers who are paying attention will notice that this is a form of creating spirals of success for others, as the person I responded to recommended, but an emphasis on the fact that the targets of those actions can be people who have a lesser standing, rather that aiming laterally or upwards.)
For what it’s worth, I don’t think there’s much about Gleam’s design that is specific to “the functional patterns the BEAM was built for.” If you’re getting stuck in abstraction hell, consider asking the community for advice on what would be more idiomatic.
The article admits that the 700k figure “assumes the worst-case scenario that you take the high valuation of the financial authorities (factor 13.75) as base valuation for your exit tax. Instead, you could also find someone to assess the real value of your company, which is likely lower…”
A reasonable person could absolutely think it’s fair to impose a very high exit tax on someone who doesn’t want their books examined even when it would save them money.
What makes you think things need to be special in order to be pushing toward the future? A lot of the work of building something better is incremental and not especially innovative.
People don’t pay attention to how true innovation comes through iteration. We didn’t just magically have the devices we have today from nothing; they are the result of years of subtle improvements over time.
That anybody on HN doesn’t realise this blows my mind, but perhaps they’re only young and think the world has always been full of amazing devices like this since the get go.
It found it helpful that it was presented that simply. The point isn’t what else is or isn’t deductible, it’s that engineering salaries went from being deductible to being amortized.
Businesses don't get to say they're claiming "$900k in costs" ... it depends on what kind of costs... EDIT: and in this instance, it depends on what kind of software engineering.
But why is software engineering treated specially, here? Does Disney have to pay taxes on film animators the same way, given that they're developing a capital asset?
Probably that is a large, rich field, and when you crunch the numbers, collecting corporate income taxes on 80% of essentially all s/w developer salaries in the first year after it goes into effect was a nice push to the CBO numbers related to Trump's 2017 tax cuts.
This is what's happened at my workplace. We account for time spent working on developing new products differently that development time maintaining legacy applications. Because they are reported for tax purposes differently.
This gets really “gray”. I work on web software and we tend to deploy at the end of the day. Meaning only the smallest programs are “new” or not yet in service.
Learning a bit more than “absolutely nothing” about Erlang would make a conversation more productive. The Wikipedia page [0] has some material relevant to your question under the “‘Let it crash’ design philosophy” heading.
