KiranRao0

I agree that memorization is a very useful skill, but I believe it’s over-used in some education systems.

There have been classes I’ve taken where ~half of the evaluation is brute memorizing dates/event names. Ive also taken classes (machine design) where the majority of the evaluation is open book and about solving problems. Most classes land somewhere in the middle.

I think there is a bias towards memorization-based testing because it’s easy. Coming up with trivia questions is easy. Grading those answers is easy. A students can’t complain about marks when they get a date wrong.

Coming up with problem solving questions is hard. Grading them is ambiguous. Students will complain that their mark should be higher. Everything is harder.

If the testing is memorization based, students will get good at memorizing facts and spitting them out on the test. If the test is problems solving, students will optimize for that.

My naive guess is that business with no tech component hire consultants, and these are part of the sales pitch.

Or governments/large organizations performing box checking exercises

My conclusion from the comic is that the client is happy. Clients like this don’t really want their designers expertise.

Does anyone have sample sites that return this?

OCaml is not lazy.

src: https://signalsandthreads.com/future-of-programming/

Can someone provide a tl;dr on him/why he’s important?

I think this is the right line of thinking. My understanding of the grandparent's argument is 2 pieces:

1. Heterogeneity/homogeneity of labour.

2. Tight/lose labour market.

I think Argument 1 is the weaker argument. There's a lot of fungibility between software roles. However, there's a higher learning cost. Moving to a new software company requires a few months before someone is close to full productivity. This in contrast between a painter moving from a Ford supplier to a GM supplier will likely close to full productivity within a few weeks. The cost (to the employer) is lower to rehire someone.

Argument 2 is the stronger argument, but may not be forever. In a tight labour market, I see very little need for unions. If the marginal worker can (and will) leave their position for a better position (pay, benefits, culture, etc), I see little need for unions. However, if the labour market for software engineers shifts in favor of businesses, this will change rapidly.

This project seems amazing.

What are the potential downsides? Increased latency when routing? Unpredictable query times (cross shard vs in shard)?

Everything I hear something like “to get money and more credibility”, I can’t help myself thinking of the Key and Peele sketch about robbing a bank:

https://www.youtube.com/watch?v=ceijkZQI1HM&pp=ygUZUm9iIGEgY...

I don’t think less of this type of content exists. Its just harder to find when inundated with all other slop on the internet.

Agreed that homes can be better insulated. However, poorly insulated homes still need heat. Heat pumps seem like a good step despite poor insulation.

Reddit used to be my go-to. However, it has become more difficult (not impossible) to find subreddits with nuance. Many have become either over-moderated or entirely one-sided. Plus the enshittification always rubs me the wrong way.

Very interesting article. I'm guessing this will remain a cat/mouse game for a while.

However, any moves will increase the cost of training on un-licensed internet data. This will shift the balance slightly closer towards AI companies licensing data as opposed to using scraped data. Emphasis on slightly.

You have to assume all publicly available data is used for training.

If you don’t want people using your images, consider data poisoning techniques to punish systems that train on them.

https://www.lakera.ai/blog/training-data-poisoning https://www.technologyreview.com/2023/10/23/1082189/data-poi...

Per the wikipedia article: “Modern computers use about a billion times as much energy per operation.”

I’m guessing the efficiency gains can be considerable before hitting this limit.

Cool, I haven’t seen that one before!

Im also sure that if theres enough customer demand (from people willing to spend $M), AWS will make network connected FPGA happen.

One key consideration is “provable fairness”. It’s my understanding that exchanges use techniques like long, same length fiber optic cables to all racks within the exchange datacenter to convince customers that everyone is on a fair playing field.

This is a lot harder to do when a server is virtualized somewhere on some rack on EC2. Exactly as mentioned, people will try to optimize by spinning up/down instances as close to the exchange server as possible. Customers will be unhappy because they can’t prove that it’s fair, even if they have the closest server.

Overall great, thought provoking writing btw

Unfortunately, deactivating wasn't allowed (or at least wasn't easy) by the OEM's ROM. There may be an adb command, but it wasn't worth the effort.

I considered a custom ROM, but:

* My grandmother is averse to all change

* Transferring stuff (apps, settings, pictures) over would have been a pain

* It's a lot easier to support a single utility app than support an entire OS

> Cars are very obviously not the future of human transport

I wish this were true. However, I'm seeing the trend pointing in the opposite direction almost everywhere. For example, almost every European country has seen a rise in the motorization rate. [1] China is also firmly on the rise, and America remains 80-90% [2]

Given this, I don't expect that OSM has the ability/authority to make a dent in motor vehicle usage rates. I do, however, believe they can take advantage of the way the world exists today to improve open source mapping.

[1] https://ec.europa.eu/eurostat/web/products-eurostat-news/w/D...

[2] https://www.forbes.com/advisor/car-insurance/car-ownership-s...

[Not cited, but neet]: https://www.jstor.org/stable/27503807

My grandmother's primary method of communication is a cheap Android tablet. It unfortunately includes a preinstalled SMS app that upsells a VoIP SMS service. My grandmother gets extremely frustrated by accidently clicking the message icon and opening an upsell page. There's no way to uninstall the VoIP app.

So instead of giving up and buying a new tablet or paying for an unnecessary service, I hacked together a way to open WhatsApp instead.

https://github.com/Kiran-Rao/openwhatsapp

To me, these lessons feel very similar to the lessons learned working at a midsized company.

Was there any particular takeaways that are exclusive to working at a FOSS?

I find it common for human customer support people to give inaccurate information. I don't know about "outright lying", but I've had people tell me things that are factually incorrect.

Shoving somewhere in a datacenter and virtualizing so that 96 different clients can use it at once.

My personal take: Microsoft isn't facing the same wage competition it used to, so doesn't have to increase wages.

> I really don't want to restart with the hassle of configuring a js project from scratch. Done it already a thousand times, and that's a thousand times too many :)

This is the key. For small apps, it's far more effective to pay the premium to not deal with any DevOps. Once an app gets bigger, it'll make sense to spend more time optimizing cost.

I feel like Vercel is the new Heroku circa 2015. I'm hoping it won't follow Heroku's trajectory, but who knows.

I would expect small class sizes to be considerably more expensive.

Slowing down would be hard since it's a live stream

While I agree, often times the places that need the most heat are those with snow. So it may still be better to optimize for cooling in many cases.

I don't see that as explicitly a bad thing.

If a rational founder thinks they can gain more by working on their friends startup, it might be better for the collective to have more people working on the more promising project.