"I first tried to write a story when I was about seven. It was about a dragon. I remember nothing about it except a philological fact. My mother said nothing about the dragon, but pointed out that one could not say “A green great dragon,” but had to say “a great green dragon.” I wondered why, and still do." - J. R. R. Tolkien
Vocal language is not a solved problem and hopefully never will be. I think it is important that we all maintain our respective languages. Let them flow and change and never fetter them. Co-opt words, phrases and more as you like but cherish your roots.
Mr T invented an "Elvish" script and language and I think he also did so for Dwarves too. I'm pretty sure he was a prof at Oxbridge with a focus in languages, mostly English.
Most English native speakers never notice adjective order as being a thing.
It is a thing and I suspect Prof Tolkien learned that dimension comes first and colour second. I don't know why we insist on this but it is pretty deep!
Swyfft is an Insurtech, primarily focused on Homeowners. We're not as well known as Lemonade and Hippo (we'd rather keep our equity than give it away, if it's all the same), but from an actual business perspective, we're arguably doing better. We've already got a number of smart, friendly and hard-working developers on our team, and need more.
Our backend is C#/.NET Core/SQL, our front-end is TypeScript/React. The positions we've got are mostly focused on the backend, but some good full-stack or front-end skills would be great. Insurance experience would be great too, but, well, I didn't have any when I started either.
If you check out our jobs (https://swyfft.bamboohr.com/jobs/), ignore the "city" in the job description - that's a limitation of the HR platform we're on. We've been fully remote since long before Covid, and you can work from anywhere in the US.
As it turns out, Daniel Bennett is an atheist materialist crank who has developed evasive "materialist arguments" which apparently tell us that the universe has no cause of existence, which turns out (shock, horror!) to be the standard atheist cant that he already believes, and so his arguments tell us nothing else...
Heck, still is. C# is a nice, pragmatic, practical language, and the VS/Resharper combination can't be beat anywhere, period. I love how lazy it lets me be.
Funny enough, I developed libraries mostly, in both for server use (nhibernate/castle), and for client side use (windows phone), and i can say pretty confidently that development environment for windows phone 8 was far superior to what android had, too. Android was a platform for years while wp8 was really new.
Microsoft knows how to create developer tools, and languages.
It's an ugly secret that WP in many regards was the best platform out there. If it was about 90's desktop operating systems it would be BeOS out of the options Windows 98, MacOS 8 or BeOS.
But it was not only late to market but also Microsoft's PHB's managed it pretty ugly.
Chesterton's fence has long been a staple of HN discussions. Unfortunately, it involves no risk/reward analysis and it invariably leads to needless conservatism. That's probably not a big deal in medical research where risks are often high, but it's a problem when applied as a general principle.
(The opposite wisdom is probably grandma's ham [1]. Consider that if grandma had passed away, they might never be allowed to try cooking the whole ham.)
The point of Chesterton's fence is cost/benefit analysis. It's not saying the fence mustn't go; it's saying you need to know why the fence was put there in order to evaluate whether it's best removed or left in place - that is, your analysis needs to be informed by understanding of the status quo in order to be accurate.
Grandma's ham is a great example. It might have been some subtle trichinosis-related failure case that cutting the end off a ham reliably prevents, and it's a shame we had to lose your great-uncle Joe to find out about that. Or it might have been an issue of pan length. You can't know until you ask, so you ask if you can. If you can't ask, then sure, you do the best you can with what you have - I should like to hope there are no blind dogmatists here. But if you can ask, you'd be a fool not to.
And FWIW, I remember complaining about this to Don Syme something like 5+ years ago, and while he gave lip service to the idea that F# needed better tooling (and better tooling interop with C# specifically), I don't think he was really convinced.
It's the "Go to Definition" and "Find all References" pieces that are so annoying to me, and slow me down tremendously. It means that (practically) you have to do your whole solution in one language for it to feel like a unified solution, and that makes it hard to start by bolting an F# project onto an existing solution.
I've successfully used Pivotal Tracker for my last three startups. It's an opinionated tool whose opinions don't always match mine, but it works well, and I've scaled it to teams up to about 15-20 participants. Beyond that, it seems to get bulky and hard to work with, but I don't know if that's so much a limitation with Pivotal, or with how I've tended to use it.
reply