cehrlich

This is my experience as well. Going on a long run if you ate garbage the day before feels terrible, so you get conditioned to eat clean.

When he has people on who don't have media training / talking points (for example Brian Kernighan is a great guest) the podcast is fantastic. He asks good questions and lets the the guest talk. The conversation goes on for however long it should, often several hours.

I found his demeanour a bit strange when I first came across him, but warmed up to it over time. For many of his guests, they've never done a better long form interview/conversation than what they did on Lex's show.

If you look at the current crash on a Log chart it's not as bad as the 2018 crash was (yet?).

I personally don't hold any crypto and don't care much for it either way, but it seems reasonable that companies that fundamentally believe in it (as opposed to riding the wave and buying football stadiums) would be in it for a long run and hopefully have what it takes to survive a serious crash.

> Most men get somewhere like 0-4 matches a week and most women get somewhere like 100-1000. That’s a 25x difference best-case scenario and often it’s over 100x. Which is kind of insane considering there are about 50/50 men to women ratio in real life.

How is this statistically possible? Women getting way more _likes_ is plausible if men swipe right much more than women do. But each _match_ involves a man and a woman getting a match.

Agreed, "normies" is a fine shorthand for "people who are not concerned with the niche thing we're currently talking about", but seeing people who think of it as an actual category that they judge people by is a dangerous mental model that a lot of people on here seem to fall victim to.

there were huge protests against vaccines and mask mandates not too long ago (not making a moral judgment here, just saying people are definitely not afraid to voice their opinions loudly in public on some issues)

I'm happy with it.

Here's a tip for anyone with docker compatibility problems: If you add `platform: "linux/amd64"` to your docker-compose (there's also a similar command for Dockerfile iirc), it just gets the x64 images and emulates those.

There is emulation overhead of course, but it's not perceivable in my experience, compared to running native images.

One thing I'd be curious to know is how large the current open platforms are compared to those of 20+ years ago. The internet as a whole is so much bigger that it's hard to maintain a sense of scale.

For example, how many people are using Matrix now, compared to IRC 20 years ago? IRC had 10M users in 2003 [1], Matrix has 28M 'global visible accounts', but who knows what that means.

Maybe it's ok for these platforms to remain 'small', growing slowly. Sure we'd all love to win the fight for a free internet tomorrow, but it's also important to maintain a realistic perspective.

Disclaimer: Usenet is still growing, but I presume that's just alt.binary - According to Wikipedia [1] it had 15M daily posts in 2010, and 171M daily posts in 2021.

[1] https://en.wikipedia.org/wiki/Internet_Relay_Chat [2] https://en.wikipedia.org/wiki/Matrix_(protocol) [1] https://en.wikipedia.org/wiki/Usenet

Yeah, same in Austria. Energy prices on my provider are going up by 90%, many food items are up 50%+ since the start of the year, and outside of some grumbling in private conversations I've not heard much complaining.

The MacBook Pro 14"/16" can charge via USB-C, so almost certainly.

Lenovo M14. The design and hinge is great and the panel is fine, but I actually wouldn't recommend this one as it's 1920x1080 which scales poorly with MacOS. For VSCode or a web browser it's fine though, I just use CMD+(+/-).

Ideally I'd recommend anything with 2560x1440 or 2560x1600 resolution.

M2 will be faster in single core, M1 Pro will be faster in multi core.

Taking Apple's 20% claim at face value:

Geekbench Single Core - M1, M1 Pro: 1700, M2: 2040

Geekbench Multi Core - M1: 7700, M1 Pro 8-core: 9000, M2: 9200, M1 Pro 10-core: 12400

Of course we'll see M2 Pro/Max sooner or later, which will presumably match M2 on single core just like the previous gen.

Think about what you do and what you need. I bought an M1 MacBook Air to keep me going until the Apple Silicon 16" Pro, and ended up staying with the Air.

16GB is fine for a typical web dev setup with three Docker containers. When I go out for more than a day I take an external monitor with me, the total package weighs less than a 16" Pro and has way more screen real estate.

Of course there's some people who definitely need the 16" Pro.

Mario Run was also just not a very good game (this is obviously an opinion, but still…). I wonder how it would go if Nintendo tried releasing an actual good game for $10 or some other amount, not an infinite runner with a Mario skin.

The Django documentation is outstanding. Django was my first time doing web programming, and the docs both got me up and running in no time, and also repeatedly surprised me by having easy to understand answers to whatever obscure thing I wanted to know.

Freelance clients who think that meetings don’t “count” as work and thus shouldn’t be invoiced.

Obviously it’s up to me to fire these clients, but still…

I am looking for a Junior Frontend or Full-Stack (with Node) SWE role.

  Location: Vienna, Austria
  Remote: Either is fine.
  Willing to relocate: Maybe. Would definitely be interested in relocating to London, or Japan (can work there on a spousal visa). Anywhere else depends on the job.
  Technologies: TypeScript, React/Next.js, CSS, Redux, React Query, Express, Postgres, MongoDB, REST, GraphQL, Jest, Cypress, Docker, GitHub Actions, AWS (EC2/S3/RDS), Git, Linux

Self taught programmer with a background in design, currently working as a University lecturer while building out projects and contributing to OSS, looking to transition into doing development full time. I’m a full stack developer with a particular strength in front end design/styling but can contribute anywhere in the stack.

Portfolio: https://c-ehrlich.dev

Github: https://github.com/c-ehrlich

Email: ehrlich dot christopher at google's email service dot com

CV: on request

I don't know about other parts of the UK, but I interviewed for some (senior) lecturer positions last year and the salary was a joke by London standards. I'm not comparing to lofty SWE salaries here, but just compared to what it takes to make a decent living in London.

It’s true that there are a lot of different ways to do the same thing, but the good news is you’re doing the same thing and the difference is mostly just syntax. Someone who has used Redux extensively can get up and running with Zustand in no time, and vice versa. Likewise React Query and Apollo Client are basically the same thing.

Build tools are a bigger issue, but fortunately most front end devs don’t actually need to deal with them all that often.

Not great.

A bit more than two years ago my wife went back home to Japan to give birth to our daughter. Then covid hit and her stay there was prolonged. At some point she decided she'd rather stay there permanently.

I accepted that she wasn't going to change her mind, so I started doing everything I can to prepare for a variety of possible futures: - Learning web development to transition from my current career as a university lecturer in an unrelated subject, as this would give me the possibility to sooner or later work remote which might allow me to move to Japan, and/or earn more so that I don't end up struggling to make ends meet in case of a divorce. - Learning Japanese to a level where I can read most things and hold a decent conversation, to make the option of moving to Japan viable.

I went to Japan for a month recently and realized that it's basically impossible for me as a foreigner to ever have a satisfying social life there, despite speaking the language to a decent level. I'm not sure I can live there without completely destroying what's left of my mental health.

Now that I feel just about ready to start applying to some React/Node jobs, the market crashes and from what I've read many companies here in Europe are implementing hiring freezes, especially on Junior roles. On top of that the market in Austria has never been anywhere near as good as some other places. Of course I only need one job, but it's very demotivating.

Most days I spend 14-16 hours between my current job, commute, programming, and language learning. I basically enjoy all three of those things, but the grind is wearing me out. I find that when I take time to meet family and friends I'm so exhausted mentally that I often barely participate in conversations, and feel guilty the whole time that I'm not being productive.

The irony of it is that if Google's algorithm made sense at all (Why is a recipe being downranked for being older than one year?), people wouldn't have to do all of this stuff.

It's a vicious circle and I don't know if it's possible to escape at this point by any means other than inventing a better search algorithm and convincing a large number of people to use it.

TypeScript stuff:

1. A tool for debugging TypeScript (in VSCode) that shows the provided and expected types, and how they are different, in a way that is easy to read.

Instead of having a bunch of nested paragraphs in plain text, show it in two columns, each displaying how a normal person would write a type declaration. Maybe even use color (highlighting?) to show which parts are different.

2. A tool for VSCode that lets you expand (into a modal or whatever) types that are abbreviated when you hover them

Photopea is great and I’ve been using it a lot lately. But while it’s getting close to feature parity with Photoshop, the fundamental algorithms are significantly worse.

One example to test this: create a new layer, select a rectangular area, fill it with the paint bucket tool. Then use free transform to rotate that rectangle 45 degrees. The edges will be a mess. Its even worse at other angles.

I don’t want to slander Photopea because as I said I use it a lot, but I’d suggest to spend a while with it before deciding that you’re ready to ditch Photoshop/GIMP/Affinity.

I wonder if there isn't a third factor:

3. Android OEMs can't make a good small phone, even if there was the demand to produce it at scale

Because of how efficient Apple's SoCs are compared to Snapdragons, Android phones typically have much larger batteries than iPhones while getting about the same battery life. Big battery requires a big phone. The occasional somewhat small Android phone (for example Galaxy S10e) tends to have awful battery life.

Looks interesting, especially the frankenstein model in the ThinkPad T41 chassis as that has a lovely keyboard and display aspect ratio.

However I think the biggest problem to tackle here is not the hardware but the software. If it runs for example some kind of regular Linux distribution or Android it won't be very usable as they're just not designed for e-ink. If on the other hand it runs something custom, it would need to be able to sync documents to the exact syncing setup that I currently use for me to consider buying it (and of course also the exact syncing setup of any other potential buyer, of which there are probably close to infinite, especially in the kind of circles that this device appeals to in the first place).

I once wrote a Twitter clone in Vanilla JS, just for the sake of it.

I'm glad we have frameworks.

Not entirely on topic, but is there anything like a “generic component library” that just gives accessibility and has as little opinion about design as possible, but can them be styled with Tailwind?

I think Tailwind is a great way to get a good looking site very fast, but I’d rather use eg a Toggle component that someone else built and tested than create my own and inevitably make some kind of accessibility mistake.

This is absolutely true. But if cleaning your data takes barely any compute and only fails less than 1% of the time, it’s splitting hairs.

The way I think about it is, how would I write it if performance didn’t matter? And then from that point I think about what compromises I can make that improve performance at the expense of something else (readability, etc)

Disclaimer: I’m not trying to argue that my preference is _better_.

I tend to prefer the approach of

  fetch A
  wash A
  fetch B
  wash B

in terms of being easier to read. Of course sometimes there are performance benefits to firing off all the requests right at the start.

Anyway I definitely agree that not separating the core logic out from the data fetching/cleaning is a bad idea.

The downside is you might end up resenting your hobby