Note this shows me how many RSS readers have accessed my RSS daily. I can't actually track each person, although I have a report I'm working on for the end of the year.
3,993 karma · joined September 16, 2013
Note this shows me how many RSS readers have accessed my RSS daily. I can't actually track each person, although I have a report I'm working on for the end of the year.
One thing I failed to notice was that RSS was still active. So this year, I started consistently contributing, over 150 so far, and I see RSS picking up right where it left off [0]. A lot of my blog post suck, but I write them as an observation and my current understanding of a subject. Readers have agency to skip what they don't like and only read what they like.
And if they did in fact spend 6 months painstakingly building it, it wouldn't hurt to break it down into multiple PRs. There is just so much room for error reviewing such a giant PR.
If they don't bother writing the code, why should you bother reading it? Use an LLM to review it, and eventually approve it. Then of course, wait for the customer to complain, and feed the complaint back to the LLM. /s
Large LLM generated PRs are not a solution. They just shift the problem to the next person in the chain.
Detection is not what is going to solve the problem. We need to go back and reevaluate why we are asking students to write in the first place. And how we can still achieve the goal of teaching even when these modern tools are one click away.
I've found a better approach to using AI for writing. First, if I don't bother writing it, why should you bother reading it? LLMs can be great soundboards. Treat them as teachers, not assistants. Your teacher is not gonna write your essay for you, but he will teach you how to write, and spot the parts that need clarification. I will share my process in the coming days, hopefully it will get some traction.
When I decided to record an audio version of my book, I started with Audacity. But it quickly failed me when I started losing track of what files I was using, and if I deleted a file from the timeline, it was impossible to track what was what. All this because Audacity doesn't have a media manager. Instead, you have to open a folder on the side and manage media yourself. I've written a blog post about it, didn't get much traction. But as of a few days ago, one of the developers commented that a media me is "on our shortlist of new features to include".
I am really looking forward to version 4.0, I hope Audacity gets its Blender moment.
As of last week, impressions have also dropped. Maybe people not clicking on my links anymore is the result?
I don't believe in these methods, but the company as a whole is going to align. I do not pretend I'm excited about it, but I remember that I am in a room with full grown adults. I've addressed the issue, and made sure to frame it with "we are aligning with the rest of the company" as opposed to just saying this is the way forward, deal with it.
Edit: Coincidentally one of my blog posts is on the front page right now and addresses similar issues -> https://news.ycombinator.com/item?id=45359604
A big thanks to Ton. And don't forget that you can support the blender foundation.
- "Hey, I applied, could you hire me?"
- "I have a compsci, I'm qualified, I sent a resume"
- "can I use you as a reference?"
These are people I've never met, yet they are so direct to the point of being rude. But to the best of my knowledge, they are real people. And what it looks like is that I'm contact #258 in a spreadsheet, because they have to cast an extremely wide net to hope for a single response. When I respond, they are lost because they don't even remember which of the job I was a contact for.I don't envy anyone looking for a job right now.
I just checked one of our repos right now and it has a 981 packages. It's not even realistic to vet the packages or to know which one is compromised. 99% of them are dependencies of dependencies. Where do we even get started?
However, RSS! People have literally emailed me to tell me that they are unsubscribing from my newsletter but "Don't worry, I follow you through RSS." My traffic is larger than ever thanks to RSS. I syndicate the full content, not just a summary, yet people still click and visit my tiny blog.
Google traffic, mainstream social media, all of them don't care about my blog. But from time to time, random people send me an email, and that makes up for it.
A technology is a tool you can adopt in your toolchain to perform at task, even if in this case it's outsourcing cognitive load. For a subscription company, well, as long as the subscription is active, you get to outsource some of the cognitive load. When Anthropic's CEO says that white color jobs will disappear, he means that he is selling Enterprise subscriptions, and that companies will inevitably buy it.
navigator.share({
title: "hello",
text: "World",
url: window.location.href
});
Plus if the page has images, the browser will automatically use it.So their feature is not just text to speech, but a reading of a summarized version of the articles. But here is the problem. The documentation has no fluff. You don't want a summary, you want the actual details. When you are reading the document that describes how the recovery fee is calculated, you want to know exactly how it is calculated.
I've ran it on multiple documents and it misses key information. An unsuspecting user might take it at face value. So this feature looks impressive, but it misses the entire point of documentation. Which is *preserving the details*.
But in the long term, when experienced developers actually feel comfortable letting LLMs write large swats of code, or when the machine no longer needs to generate human readable code, then we will start forgetting how it works.