wsostt

You might have missed the ending.

> Also, for those wondering, I really really hate the Pixel 7 Pro.

Are they saying that the same 12% of people eat half of the consumed beef each day? Or that 12% of beef consumers eat half of the daily consumption but that group’s membership changes each day?

If I eat a steak and cheeseburger in the same day, am I part of that group or am I never part of the group because I only eat beef 1x per week?

My first introduction to this concept was Tobin Sieber's book Disability Theory[0].

He referred to able-bodied people as TABs, Temporarily Able-Bodied. You are born a helpless infant and, if lucky, die a helpless elder.

> The cycle of life runs in actuality from disability to temporary ability back to disability, and that only if you are among the most fortunate.

[0] https://press.umich.edu/Books/D/Disability-Theory2

Totally agree. I’ll treat Google’s future Gmail AI announcement with a lot of hesitancy. Forget a 3rd-party implementation.

The team has a GitHub repo:

https://github.com/WolframResearch/Arrival-Movie-Live-Coding

I would add that good writing is required for all career advancement.

Senior engineers or architects may do more design than coding and the design needs to be conveyed likely as writing and hopefully a couple diagrams.

Managers absolutely need to be good writers to communicate effectively, advocate for their team, and tell the story of the team’s work.

If you’re an engineer and want to have a higher level job than you have now, getting better at writing is only going to help. I’m not saying it’s a MUST because I’m sure there’s some outliers, but it won’t hurt.

Going to check this out.

FYI - your Obsidian and Logseq links on the honmepage are swapped.

I don’t think the pilots are being scapegoated when they ditched a working plane in the ocean. There were a lot of things that led them there and a lot of reasons it happened, but this crash was avoidable with proper procedures.

If they’re unhappy with their own API, this could provide an abstraction layer for the app. They rewrite their client to use this API and it frees up two teams to work (almost) independently. The UI team can work on their roadmap while the backend team fixes the internal API or retires the logic and implement it into this new layer.

I’m not saying they’ll do this or that it makes sense. But I’ve definitely done it in much smaller projects.

Similar to the Big Ball of Mud [0]:

>If you think good architecture is expensive, try bad architecture.

[0]: http://laputan.org/mud/

Microsoft announcement with some details: https://azure.microsoft.com/en-us/blog/general-availability-...

I question the functionality but the aesthetic reminds me of my old IBM Thinkpad days.

These sections can be blocked on a desktop browser with AdBlock.

Snowflake is so expensive that Capital One has developed a toolkit for managing your instance.

https://www.capitalone.com/software/solutions/

The article defines it as “non medical”. And that doesn't mean that people can't find identity in it.

This is the best interpretation of this list. It’s a great guide to understand what topics you care about. Maybe there are a couple questions in here that would raise red flags for you. You should pursue those as conversation points.

Try LunchMoney as an alternative to Intuit. Solo founder, great support, great roadmap and delivery. She uses Plaid so the integration is similar to Mint.

https://lunchmoney.app

We had a small hand pump toy that would suck up the tub water and spray it. It was a manual pump so it taught cause/effect which is critical for development.

Second the swimming lessons. I have two daughters with a rare genetic condition and they are obsessed with swimming in the pool. My older is physically challenged, wears AFO legs braces, has a seriously disturbed gait, and frequently uses a chair when we’re out in public. But she can swim non-stop for an hour. Great exercise, great strength building, great for safety. I feel like her freedom in the water is an escape from her limitations on land. :D

DynDns can help overcome the static IP barrier. I've used this some years ago but can't vouch for its functionality today.

https://account.dyn.com/

How do you propose stopping estimates from becoming commitments? Genuinely asking because I struggle to not do this as a manager.

You can add a playlist to your library and it will show up in the Playlists section. Navigate to the playlist and look for an icon with throw horizontal lines and a check mark.

This is a perfectly acceptable view of the United States if you only watch television news.

Not OP, but I doubt it. These are individual mandates with mandatory minimums in the tens of millions of dollars for a small shop.

Clients are heard and in charge. These are smart people who will terminate the relationship if their goals aren’t being met. This isn’t your retirement account. These are accounts in the 9+ figure range.

You’re not considering that a lot of active managers are helping clients define bespoke investment strategies that suit their assets and liabilities. They set a strategy, pick a benchmark, and invest. In some cases, a portion of those investments may be passive instruments and other portions may be research-driven asset allocation by the manager.

I've been doing this for a long time now. I present the candidate with a function (on paper) that compiles and runs. It does the job but it does everything poorly: an embedded connection string, leaves the connection open, no error handling, bad variable names, no comments, etc... EVERY candidate can find something wrong with this code and the things they pick up is informative. Juniors can find the easy stuff, more senior-level folks find the deeper flaws about the basic structure of the code like figuring that a lot of this is boilerplate that could be implemented elsewhere.

A certain amount of information can be gleaned from job descriptions from a company’s careers page.

Neither by default. I look to be convinced that they've implemented containers because it made sense for their technical architecture or strategy.

I have a vendor who pitched their new "cloud-native" re-platforming project and it really spooked me. It's data management-type tool that was migrating from a traditional on-prem client/server architecture to an AWS-hosted Angular interface with a MongoDB backend. I got the same pitch a year later and the entire stack had changed. I was spooked the first time; now I'm really spooked and thinking about migrating off the platform.

I agree. I've seen containerization mentioned by many vendors in the last year. It adds another layer of questions to vet like "do they possibly know what they're doing?"

A "water garden". No joke.

https://martinfowler.com/bliki/DataLake.html