i'd pay way more than 100k for a tinnitus cure. it would be worth significantly delaying retirement for. but there's nothing on the horizon. and yes, i have adapted to it well enough that it doesn't cause me anxiety and don't notice it 98% of the time. i just miss pure hearing.
Could we not waste time on making inane comments like this, just for today. What you just said has nothing to do with this article, nor does it match anything Apple does, as they don't even serve advertisements in any form, and offer lots of ways for users to cut down on advertising.
Is there a good grid control (ie a data grid) for Blazor? A colleague reviewed the offering from Infragistics and it wasn't anywhere near their WPF data grid control.
There are grid controls from the usual commercial vendors like Radzen and Telerik. I used them briefly during a free trial. It has a funny name, but MudBlazor [1] has been the MIT licensed library I have been using lately. I have been using their Table control, which may be what you are looking for in a data grid. [2] Check it out and see.
I don't want "mental health support" from work. I only need that if my workplace is causing serious mental health issues in the first place. (Which it is at present.)
A personal counterpoint: I do want mental health support from work. Many of the downsides of complex childhood trauma didn’t start to really interfere with my life until my late 20s/early 30s.
When I started really struggling at a job I’d already established myself in, I learned of and am incredibly grateful for the mental health benefits offered by my employer and for leaders who are open, understanding and willing to work with me when things aren’t going well.
When I first had to broach the subject, easily finding resources about the company’s EAP benefits instead of feeling like it was all some hush hush thing really helped reduce the anxiety of opening up about a difficulty topic.
I think it depends on what mental health support means. If it means helping pay for therapy and managers making accommodations and being genuinely supportive of people when they're having a hard time, that's fantastic.
Unfortunately at many companies it just means a presentation from HR every couple of months that boils down to "10 strategies to cope with the burnout we're causing". Meanwhile the people with actual power to change things keep pushing the same "aggressive" deadlines and refusing to provide the support/resources necessary to meet them in a healthy and sustainable way.
a small gripe about the otherwise excellent writing:
> at that point high standards are not merely useless but positively harmful. There are a few people who start too many new projects, but far more, I suspect, who are deterred by fear of failure from starting projects that would have succeeded if they had.
I think this buries the lede a bit. And "success" isn't a good measure, when the important thing many times is self-development or even just the skating feeling.
we have a homegrown push-based streaming library in .net based on reactive (it supports indexed joins of "tables") and we're looking for something more infrastructural as we move to the cloud.
I'd love to use this while teaching my kid how to program. That goes better if we both have access to the same screen. We tried repl.it but it's too wonky (cursor doesn't quite stay synchronized etc) - I think repl.it tries to do too much and ends up not so great. I could use coscreen with vs code. We're a linux household though - we'll be waiting.
our team (C#) did an extended proof of concept in F# about ten years ago. we found that it was easier to hero-code in F# but harder to work as a team over time in F#. we ended up embracing a lot of the functional paradigm in C#, which seems like a very good compromise.
The next question is whether this is from lack of common constructs/conventions by those new to F# or if it would always pervade as seems to be the case with Lisps. e.g. Clojure was specifically made to cover more in its library and syntax to promote standard styles.
Rather than thinking F# didn't/doesn't work, what were the reasons and what could be changed so it did work well?
Maybe some workflow changes like more design discussions before putting up a PR for review, or pair programming with rotating pairs so that conventions emerge. Also over time the codebase itself if it has benefited from convergence would show repeating patterns of adopted conventions.
I see the language itself as unapproachable only by reputation/lineage. In practice it can be on about the level of Elixir which is gaining traction and success stories.
Could it be that you are just observing productivity? It seems plausible that anything which slows things down helps people work on a thing as a team because it's easier to keep up and there is more time and energy available to organise teamwork.
"Hero-coding" is the kind of thing where you alone go into a fugue state for a week, and emerge on Sunday night, covered in blood and with your hair standing on end, holding a crystal redolent with eldritch power.
Here's my stab at it (though I could be wrong). It's like perl, easy for experts to write a lot of it fast, but hard for anyone else to grok what's going on.
As an anecdote, I see it come up with clojure a lot. Some of the clojure devs in my company can spin up a lot of interesting applications and fast. However, trying to read any of there code can be nearly impossible. Why? Usually because of a generous helping of their own metaprogramming constructs that they've built up over time. I've watched them program and it's both interesting and really hard to follow.
The big problem we've ran into is these clojure projects have been really hard for teams to get into. As a result, the worst thing has happened, many of them are being scrapped and rewritten in java because they are too hard to maintain otherwise.
> easier to hero-code in F# but harder to work as a team
Allowing hero-coding in any language makes it harder to work as a team, so using language that leverages hero output only makes it worse. I wouldn't say that the power of the language is the thing that should be blamed.
I can certainly see that using constructs that the team as a whole isn't ready to adopt being a problem that also comes up in adoption of Scala.
