Nice!

Is something like the Reporter App?

PS: not an affiliate, just curious

As someone who played with the DOS text mode fonts a little, I never bothered with that question, assuming left tilt of the arrow was a way to make it visually bigger / more visible

Questions at the end of the article, are the ones, every engineering manager should ask

Interesting. I did the same within just my team. We used Confluence to publish those, describing accomplishments of every IC. This initiative was started to appreciate the work of the team, so I still was concerned if anyone were reading those reports apart from my team, but I never had a question from the Steering Committee "what all of these peeps doing there?" since I started.

Question: what the format you have used (number of words)? Kind of a release notes? Was anyone actually reading those?

E.g.

"Agents can now see their up-to-date balance on the app (previously they had to wait for the weekly email). Here's a screenshot. Here's a direct link to the QA environment so you can try it out yourself."

That's usually it for a given feature.

That's it - ongoing development. You should constantly invest in the development of your SaaS product, unlike the example with the books

Why focus on imposing additional work on developers, rather than users (which, by the definition, is much wider audience) having to workaround hard-coded behavior? Adding color support to cli tools is an additional work for developers in the first place

Anyone cares to share how M1s performs with virtualization tasks? Say Windows desktop or Linux cli?

Note that while people here are gushing over performance, it's worth mentioning that you need to run ARM64 virtualized OSes (both Windows and Linux) for it to work.

Getting Intel x64/x86 VMs to work is... fun and they don't perform nearly as well as you'd expect from the gushing praise.

So double check if your virtualization use-case actually is fine with running ARM guests.

Docker runs a linux VM and it destroys intel macbooks. I hardly notice it running on the M1. Flawless experience with minimal power drain.

A coworker of mine is seeing their M1 performing about 2-4x slower than my Intel MacBook Pro where Docker is invoked. So YMMV

That sounds like they’re running x86 containers. I use Podman amd it’s very fast with ARM but notably slower when emulating x86 and there’s at least one case where this hit a JVM race condition in some old vendor code which still uses JDK8.

I'm able to use arm containers for my work and it doesn't seem any slower than what I'd expect from native performance on my M1.

Ditto: slowness is my cue to rebuild the container for both architectures

I'm using vmware fusion to run ubuntu vms for my daily work. The virtualized 20.04 aarch64 is on par with my x64 desktop (5900x from amd). Surprisingly in both, ST and MT loads. The laptop never runs out of juice at the end of the day when I'm on battery. Also there's no perf. penalty for disconnecting the charger.

Pretty good but note the M1 chip does not support nested virtualization. So you can run Windows/ARM but you can't run Docker, VMWARE or VirtualBox inside that.

Flawlessly.

I've started my IT career as an Technical Support guy in 1995. Back then, computers in local companies were used mostly for Accounting tasks and word processing. So I've seen a lot of accountants and how they work. What bothered me back then is an amount of manual data entry they did. Fast forward to today, and I still see no significant progress in this area. Sure, I am not as close to accounting professionals as before, but it still seems like some good 50-60% of their job is data entry, with various kinds of reporting filling the rest. Perhaps some kind of "IDE" can solve the efficiency problem, but I doubt it would solve effectiveness issue. Still I completely agree, that open standards for data and common protocols is the way to address this, but as long as accounting software vendors trying to maximize their profits, rather than business outcomes of their customers, I'm afraid we're stuck with what we have.