zffr

It really depends on how you are using AI. If you simply use it to get the answers to homework you won't really learn. If you use it to figure out the topics you need to learn, and to identify/close gaps in your understanding then it is a very useful tool for learning.

IMO the fear is that software engineering becomes a _high_-skill profession.

If the models get good enough to solve all of the low-skill problems, then we only need to keep around the people who are highly skilled. That means a fewer number of software engineers, and a difficult path to becoming someone who is highly skilled.

Here are some reasons to use this instead of the simulator: security research, testing, automation

With webhooks, consumers get to asynchronously respond to updates from a provider. If no data has changed, a provider will not send any updates.

With SCROLL, consumers are responsible for choosing when to ask a provider for updates. Without a mechanism for knowing when data has changed, consumers will be forced to be pessimistic and poll providers for new data on some cadence.

I see two issues with the proposal: (1) SCROLL will lead to an increase in unnecessary network traffic for both the consumer and provider, and (2) because a consumer cannot know when data has changed, the lag between a consumer's local model and the provider's data model will be larger when with Webhooks.

As yegge mentioned, there might be more appetite for trying out this idea now because there are many engineers who are currently unemployed. Offering them short co-op could be beneficial to both the engineer and prospective employer

What’s your use case for this?

As a next step, it could be cool to write unit tests against these screenshots that look for words like you mentioned. That way if a screenshot is updated and a test breaks you will know what documentation to update

One example where I think the law does make sense is for website URL paths.

Over time the paths may change, and this can break existing links. IMO websites should continue to accept old paths and redirect to the new equivalents. Eventually the redirects can be removed when their usage drops low enough.

It would be much snappier, and would trivially support common native features like being able to open messages in new windows.

Why would column-oriented databases be mentioned? My understanding is that these are typically used for OLAP, but the article seems to talk only about OLTP.

The performance of both the website and the iOS app is also not great. On the iOS app, I frequently see frames dropped and scrolling is sometimes blocked for up to a second or more at a time.

LinkedIn's feed is certainly not simple, but modern iPhones should be more than capable of rendering it at 60fps.

Well the executable binaries inside IPAs are encrypted, but the IPA bundles themselves are typically unencrypted. You should be able to see unencrypted assets inside of them

Fair point, I had not considered needing to read and understand code you didn't write yourself.

Especially in a corporate setting, not understanding a keyword you see in a PR could lead to bad code being checked in.

> 3. get rid of roughly 150 of the 200 keywords there are

I don't understand this point. Could you explain?

The new keywords enable new language features (ex: async/await, any, actor), and these features are opt-in. If you don't want to use them, you don't have to.

What are they keywords you think should be removed?

What are the languages with similar or better ergonomics?