Look at the handling of Middle-East by BBC, the Zucman tax at France Television, or the current allegations of fraud in some communities in the US.

My current take is that it is really hard to get a fair unbiased coverage, unless you actually state that you will strive to hire and promote both sides. If these corporations had to publish the composition/promotion/pay of their newsroom across the political spectrum (as they do for example by gender), you may start to have fair unbiased coverage. But many journalists working there see it as their job to describe "not the reality as it happens, but rather as it ought to be" (to quote the CEO of France Television). We should acknowledge that people are biased, and measure the balance of biases rather than assert there is no bias because they serve the greater good.

Macron has pushed for it (to announce as part of his state visit to the UK), the director of the Bayeux Museum has accepted (he is a civil servant, and more subject to politics).

Experts agree that any move is likely to worsen tears in the cloth (a superposition of linen): https://www.latribunedelart.com/bayeux-tapestry-let-s-listen...

The museum where it is exposed is supposed to go through renovation, and experts are worried even to move the tapestry within the same museum just for renovation purposes... one can understand their fears when it's about packing and transporting to the other side of the channel (notwithstanding the amazing level of the British Museum conservation team, among the best in the world).

A possible improvement would be to replace freedom units with their international counterpart (with sane rounding to a two digits precision, or similar).

Probably built 10+ importers, plus some plugins to do automated transaction annotations.

I have not made any update for many years now, because: - Downloading statements is still a pain, have to manually go through all websites. Banks are bad at making the statements available, and worse making it possible to automate it. - The root of the issue is actually that beancount is too slow. Any change/update takes ages. Python is both a blessing (makes it easy to add plugins/importers etc), and a curse (way slower than some other languages.

I believe the creator of beancount has started working on v3 with a mix of C++/python, relying on protobufs, a C++ core for parsing, etc. AFAIK, that is not production-ready yet.

We chose it because it felt "right", giving us c++ performance, productivity when writing, and a feeling of cleanliness from its type system I had not experienced since ... Ocaml.

But what we did not expect was how great it was from a talent perspective. We started hiring at a time where lots of rust developers were being laid off crypto, and the caliber of candidates is just ... amazing. Rust devs enjoy working with the language, and you get a type of developer who likes producing good code, and is usually quite passionate about coding.

So, I understand rust jobs are not easy to get by, but being on the other side of the table, it's a wonderful talent magnet for our team, allowing us to hire great developers.

[1] As-in, they design is iconic.

I'm myself in the long, lengthy and costly process of trying to fight a two years non-compete (well, 1yr garden leave + 1yr non-compete), and it's taxing. It adds stress, makes it harder to market yourself, and on top of that there is this clear asymmetry where the costs if it was to go to high court (£150k) would be huge for you, but petty change for your employer. On top of that, they'd get to claim these as expenses (so pre-tax), but you couldn't get any kind of tax-credit (so effectively post-tax). System is biased, it's about time they would change it.

Comments URL: https://news.ycombinator.com/item?id=3690452

Points: 1

# Comments: 0