cwisecarver

I took the time to share it because I like the show and they often report on subjects that cause them to be demonetized or hidden by the algorithm.

She was interviewed on Breaking Points today https://www.youtube.com/watch?v=NvVRnh3JVGQ&list=PLdOud06Yw7...

Relevant: Kumail Nanjiani learns about Automattic https://www.youtube.com/watch?v=BHcrispG_rc

He's actually quite nice over zoom so he just comes off as funny on twitter once you've met him.

They’re only doing this so people can afford Mac Studio/Pro with tons of RAM.

An old boss of mine used to say "Consistent is better than better" and it's always stuck with me.

Pretty sure the article is from vanity fair

The community around Elixir and Erlang is also one of its best features. Everyone I've interacted with, like Jose, is kind and helpful.

I don't know of any off the top of my head or a quick google search. I do know, from the latest ElixirTalk podcast, that it's very careful about what it sends over the wire, only the parts that have changed. If you're interacting with an API to get the same information for a SPA you're probably going to have similar latencies.

Obligatory plug for Phoenix LiveView: https://github.com/phoenixframework/phoenix_live_view

edit: This actually has examples https://dockyard.com/blog/2018/12/12/phoenix-liveview-intera...

Buying research data from a third-party academic and using it for campaign purposes is not the same thing as a campaign creating an app and then using the available data.

Hooray! Now just search for firearms and get the same results.

Headline: refers to a laptop

Article: several hundred words about an architecture that is not currently available in a laptop form factor and probably never will be.

Macs don't reboot without you taking an action if you have automatic update installation disabled. You have to click a button to apply the updates after which it will reboot. But it tells you this in the dialog where you agree to apply the updates. Windows just applies them and reboots when you're not actively using the machine.

Is anyone else concerned about buying a laptop from a Chinese manufacturer?

I own a number of MacBooks and while they were all assembled in China I don't have any concerns about the firmware. As more of these make it to US markets I'm sure if there is something it will come out but I'm currently taking a wait and see approach.

Mine is #BADA55; which is very nearby.

Store just updated. Still on 16GB of RAM.

It does boost production of NDA+ though, right?

Related: https://www.elysiumhealth.com

I've been taking this for about 6 months. Haven't noticed much other than better sleep, easier to wake upon time feeling refreshed.

You might want to try tmuxinator (https://github.com/tmuxinator/tmuxinator).

Normally when immunity is exchanged there is a proffer so that the attorneys know what they're getting in exchange. They'd pull it if it was b.s.

I replied to someone else who asked. https://news.ycombinator.com/item?id=14361539

- FK/M2M across reusable, packaged apps is only bad if you don't match the interfaces correctly. See: almost every third-party Django app that is built to integrate with another application's models.

- Sometimes you want the app concept just for organization. There's nothing bad about that and it makes sharing things inside of a project easier.

- Explicitly naming your database tables doesn't make any sense. You're using an ORM. Accept it or don't use it.

- Explicitly declaring through on a m2m field if you're not adding metadata to the relationship is pointless, but, if you're not using the table naming from Django I could see why they'd be invisible because there's no pattern to follow.

- GenericForeignKeys are dangerous but not for any of the reasons listed. It's because they implicitly force a two way join which seems magic until it becomes debilitatingly slow.

- The entire section on migrations leads me to believe that the first time the migrations are being run is on a production deploy. If you don't know SQL and you don't test your migrations prior to deployment, yes, it will be fairly difficult to determine what kind of performance/locking they're going to have.

- No to Fat Models? This breaks down to "The framework we chose to use suggests a pattern, we also chose not to follow that pattern." That's fine if you want to do that but I wouldn't suggest it to others.

- It's not hard to get signals to not fire in certain circumstances, you put the conditional in the signal callback like almost every other event-driven pattern. Also, bulk updating models doesn't fire signals in Django because save isn't called. Read the documentation.

- Avoid using the ORM? Why choose a framework as complete as Django where 80% of the features are built around or on top of the ORM and then don't use it?

- Caching complex objects makes cache invalidation hard. Well, yes, yes it does.

I've got more than 5 years of experience with Django on a number of teams and at a couple of companies and in my experience almost everything in this article is completely incorrect.

The only things I would agree with is the point about project layout and avoiding django's squashmigrations for the truncate the migrations table, delete the migrations, and create a new initial migration.

Practically everything else in this article is wrong, in my opinion.

Sorry dang. I know your job is hard enough.

What ever happened to IronPython running on the CLR?

Cue the comments stating that no one will use this because the name is bad.