HackerTrans
トップ新着トレンドコメント過去質問紹介求人

tekdude

1,433 カルマ登録 6 年前

投稿

The Most Famous AI Writing Tic Is Also the Most Mysterious

theatlantic.com
15 ポイント·投稿者 tekdude·一昨日·2 コメント

The Pissed-Off Spouses Who Try to Intervene in Their Partners' Jobs

slate.com
3 ポイント·投稿者 tekdude·29 日前·0 コメント

On Blind, Anxious Tech Workers Get the Lowdown on Layoffs

nytimes.com
4 ポイント·投稿者 tekdude·2 か月前·0 コメント

My Son's Math Homework Is Essentially Just Pokémon

theatlantic.com
14 ポイント·投稿者 tekdude·2 か月前·5 コメント

2000s chatbot SmarterChild explains everything about our relationship with A.I

slate.com
3 ポイント·投稿者 tekdude·11 か月前·0 コメント

Trello: How the project management app's update is causing customers to revolt

slate.com
23 ポイント·投稿者 tekdude·11 か月前·8 コメント

OpenAI to Sponsor Driver Alex Palou at Mid-Ohio IndyCar Race

sportsbusinessjournal.com
1 ポイント·投稿者 tekdude·昨年·0 コメント

The Bargain of Working Hard and Getting a Job Simply Doesn't Hold Anymore

slate.com
5 ポイント·投稿者 tekdude·昨年·1 コメント

A.I. job interview: Job hunting was already hard. Then came glitching HR robots

slate.com
4 ポイント·投稿者 tekdude·昨年·0 コメント

Chip Ganassi Racing, OpenAI Announce Strategic Collaboration

chipganassiracing.com
1 ポイント·投稿者 tekdude·昨年·0 コメント

"At Our Companies, Employees Just Disappear"

slate.com
24 ポイント·投稿者 tekdude·昨年·4 コメント

コメント

tekdude
·6 か月前·議論
This won't be at a 5yo level, but here's an attempt: there are a two things specific to private equity that often leads to higher prices and worsening service:

1. PE aren't investors like you and me. We can go to our brokerage and buy shares of a public company, hold those shares, vote on directors and proposals, etc... Or we can buy and sell ETF/mutual fund shares that own companies. Then, we (or fund managers) can sell those shares after any period of time we want. Could be years, decades, or minutes. Whatever meets our investing goals. The same is actually true for hedge funds. We buy a a piece of a company, hold it as long as we want, then sell to take profit/loss. When PE buys a company though, they buy the whole company AND they have a specific timeline in mind. This is because PE firms are actually temporary private "investment funds": partners put in money and expect a certain return on investment after a certain period of time. At the end, that's when the fund needs to wind down and return capital + returns. So, there's already a ticking clock on anything a PE firm buys, and pressure to generate return before time runs out. They typically do this by taking a company public on the stock market (maybe again) or selling it to someone else. (This doesn't always succeed, but there are other options then, like continuation funds.)

2. PE funds also take on a lot of debt. They can't afford to buy whole companies or roll up entire industries just with their investors' funds, so they borrow a lot. Now, the companies they buy for their portfolios not only need to generate returns for their investors, they also need to do that AFTER making payments on that debt. It multiplies the pressure.

There are a lot of cases where PE bought struggling companies, and with discipline and incentives turned things around on a timeline. But there are also a lot of cases where PE bought stable but boring companies, used debt and pressure to force them to raise prices, cut services, lay off workers, and lower quality in order to generate returns at the pace required.

(Most of this I learned from reading Matt Levine columns, I'm not an expert and don't work in this industry at all, so I may have some details wrong.)
tekdude
·10 か月前·議論
One thing you can try with headphones is changing the earpads: specifically the shape, but maybe also the material. I have Shure SRH840A headphones, and out-of-the-box I was NOT happy with the sound. Someone suggested trying different aftermarket earpads, and I found a pair of "angled" pads that changed the sound quality to exactly what I wanted. I was surprised how dramatic the effect was. The pads are huge and look ridiculous, but I only use these headphones at home so it's fine.
tekdude
·10 か月前·議論
I wonder if this supports a cleaner way to throw when the target property's parent object is null? With null-coalescing assignment, you can do the following which will throw when 'x' is null:

  string x = null;
  string y = x ?? throw new ArgumentException("x is null");
It would be interesting to try something like:

  customer?.Name = newName ?? throw new InvalidOperationException("customer is null");
But I don't know how the language would be able to determine which potential null it was throwing for: 'customer' could be null, but so could 'newName'. I guess... maybe you could do:

  (customer ?? throw new InvalidOperationException("customer is null")).Name = newName ?? throw new ArgumentException("newName is null");
But the language already supports that, and it's extremely ugly...
tekdude
·12 か月前·議論
Thanks, yes I'll probably have to give it another try some day. I might be confusing Avalonia and Uno, but I think I first attempted it a couple years ago, and then again last year. I remember spending a whole weekend trying to get it running but wasn't having success. Also, I was a bit turned off by how heavy the development environment was. I had to download and install a tool, then that installed more build tools and packages, and then there was also a "recommended" VS Code extension. With WPF, I've gotten used to writing XAML without a designer, so I can get by with just VSCode, the C# extension, and the .NET CLI.
tekdude
·12 か月前·議論
I kind of wish Microsoft would just continue development of WPF. I've used it for years for various projects, and there is a learning curve but I've since enjoyed working with it. XAML, data bindings, ViewModels... all of it I actually like. But, WPF needs a few improvements to really make it perfect. I tried several of Microsoft's newer frameworks and the open source ones (Avalonia, Uno), but I either couldn't get the sample projects to even build successfully on my machine, or I never got comfortable with development workflow, and went back to what I know.

My big idea to fix WPF is to rebuild the data binding system to use the .NET compile-time code generation feature instead of run-time reflection. I think that would solve a lot of problems. For one, projects could do an actual AOT build of their applications (right now, you either need to rely on an installed .NET runtime or "publish" the project with a lot of .NET libraries included for self-extract, bloating the final file size). Code generation would probably improve performance quite a bit too, maybe open up the possibility to compile for cross-platform, introduce type safety for XAML bindings (rather than getting vague runtime binding errors), remove the need for so much class scaffolding, etc... I've thought about starting an open source project to do it myself, but seems like a pretty big task and I would essentially be starting a project to help with my other project which I already don't have enough time to work on...
tekdude
·12 か月前·議論
Might be worth viewing the full list of changes in the blog post that the article links to:

https://devblogs.microsoft.com/dotnet/dotnet-10-preview-6/