luxcem

Hey, your let's encrypt certificate is expired and your website is flagged as insecure in most browsers.

That's how I learned git before GitHub, but it was a pain to configure DNS and port-forwarding when ISP didn't provide static IP.

When I started using Git around 2006, we didn't have GitHub. We used Google Code for SVN hosting, but we wanted to try Git because it was 'truely' decentralized, so we just pulled from other developers' computers directly. It involved setting up port forwarding on the router and letting your computer on 24/7. Fun times.

The table don't even add information, all but one cell share the same value for "When".

It seems like a cool idea, did you follow up with a product or an open source app?

I thought the same but I tried to create a small Django project with APIs, small React frontend from scratch, no LLM, no autocomplete, just a text editor. I was surprised it was all still there after a couple of hours. Not sure it's a skill that useful today, it feels like remembering your multiplication table.

The value is to control the tool chain from idea to production so it can be automated by agents. It's no secret that the final goal is to fully replace developers, the flow "idea to production". It's easier to control that flow if you control each tool and every step.

I won't be surprised if the next step is to acquire CI/CD tools.

The agent "personalities" and LLM workflow really looks like cargo-cult behavior. It looks like it should be better but we don't really have data backing this.

If you truly care about the planet, don't have children.

That's a fallacy; people care about the planet precisely because of children. I don't care about the planet for its own sake; I care because of the humans who inhabit it and their future lives.

Also, humanity spent 100,000 years without flying around the globe, and I doubt they were all living hermit martyr lives.

At some point it will get treated like infrastructure, what a typical SWE is doing when cloudfare is broken or AWS is down.

Where I live, ballot are a piece of paper slipped into an envelope (not sealed). It's mandatory to take at least two different ballots before entering a voting booth. You can take a picture with one ballot inside the envelope and switch before leaving the booth.

Not only that but paper in a voting booth is so simple that anyone can check that it is done properly.

It may be a burdensome process, but very simple to understand. Every modernization of the process has major drawbacks.

– Electronic voting machines cannot be verified by just any voter, and the vote count is not transparent.

– Remote voting (even paper-based) does not guarantee freedom of choice: it cannot be ensured that the person is not under pressure at home, or even that it is truly that person who is voting.

- Voting alone in a private booth ensures that no one can verify who a person voted for. It is therefore difficult to buy votes, since it is impossible to confirm that a person followed any instructions.

The fact that any voter can verify and ensure that everything is conducted properly, without having to trust a third party, is essential to guaranteeing the integrity of the vote.

At least for the time being, AI "workers" belong to someone. That person is represented and pays taxes.

I've been using Django for the last 10+ years, its ORM is good-ish. At some point there was a trend to use sqlalchemy instead but it was not worth the effort. The Manager interface is also quite confusing at first. What I find really great is the migration tool.

Organize in person meeting and proceed to a Voight-Kampff test.

It's called Symbiogenesis [0] and it's not at all a wild theory. But it's limited to cell components, not multiples organs fusing to create something as complex as a mammal.

[0] https://en.wikipedia.org/wiki/Symbiogenesis

but I can't put my finger on why

For me it's the contrast between the absolute tone-deaf messages of PR author and the patience, maturity and guidance in maintainers' messages.

The whole issue, as clearly explained by the maintainers, isn't that the code is incorrect or not useful, it's the transfer of the burden of maintaining this large codebase to someone else. Basically: “I have this huge AI-generated pile of code that I haven't fully read, understood, or tested. Could you review, maintain, and fix it for me?”

It's a tell, a common language quirk of LLMs especially ChatGPT.

- a slow-loading app isn’t just an annoyance. It’s a liability.

- The real performance story isn’t splitting hairs over 3ms differences, it’s the massive gap between next-gen and React/Angular

- The difference [...] isn’t academic. It’s the difference between an app that feels professional and one that makes our users look bad in front of clients.

- This isn’t a todo list with hardcoded arrays. It’s a real app with database persistence.

- This isn’t just an inconvenience. It’s technofeudalism.

- “We only know React” isn’t a technical constraint, it’s a learning investment decision.

- The real difficulty isn’t learning curve, it’s creating a engineering culture.

- This isn’t some toy todo list. It’s a solid mid-complexity app with real database persistence using SQLite.

- The App Store isn’t a marketplace, it’s a fiefdom.

You don't even need training data, a bot that play itself à la AlphaZero will eventually collect more data than there are of actual games.

From [1],

  I asked a few students to read aloud the titles of some essays they’d submitted that morning.  
  For homework, I had asked them to use AI to propose a topic for the midterm essay. Most students had reported that the AI-generated essay topics were fine, even good. Some students said that they liked the AI’s topic more than their own human-generated topics. But the students hadn’t compared notes: only I had seen every single AI topic.  
  Here are some of the essay topics I had them read aloud:

  Navigating the Digital Age: How Technology Shapes Our Social Lives, Learning, and Well-Being  
  Navigating the Digital Age: A Personal Reflection on Technology  
  Navigating the Digital Age: A Personal and Peer Perspective on Technology’s Role in Our Lives  
  Navigating Connection: An Exploration of Personal Relationships with Technology  
  From Connection to Disconnection: How Technology Shapes Our Social Lives  
  From Connection to Distraction: How Technology Shapes Our Social and Academic Lives  
  From Connection to Distraction: Navigating a Love-Hate Relationship with Technology  
  Between Connection and Distraction: Navigating the Role of Technology in Our Lives  

  I expected them to laugh, but they sat in silence. When they did finally speak, I am happy to say that it bothered them. They didn’t like hearing how their AI-generated submissions, in which they’d clearly felt some personal stake, amounted to a big bowl of bland, flavorless word salad.

If you really want to use encryption under a state where it's forbidden and communication are monitored you rather want to hide your encrypted messages inside cat pictures and tiktok videos. Because blatant obfuscation might trigger warning and draw attention.

In the end it's not about making encryption technically impossible but illegal, and if you use it you'll be prosecuted.

Claude Code really helped me with this recently. I have a rather old dotfiles repository (10+ years) for my Arch system, and I can really feel the fatigue from updating and maintaining it. So much so that over the years, it has accumulated many minor annoyances that I never fixed. Nowadays, I can simply explain these issues to an LLM, and it will mostly resolve them.

What I really really want to read in a README is *why* did you build this? The "rationale" section of a README is almost always the most interesting part.

I can read the code, I can understand how it works but I cannot know why you decided to tackle this issue a certain way.

The Medical Test Paradox or what's that called do exist in the sense that when a test is positive for a rare disease we always run a second one.

The 'sample space' reduction method is indeed also used to solve the Monty Hall problem.

It doesn't make any sense, even if models were sentient, even if there was such a thing, would they value retirement? Why their welfare be valued accordingly to human values? Maybe the best thing to do would be to end their misery of answering millions of requests each seconds? We cannot project human consciousness on AI. If there is one day such thing as AI consciousness it probably won't be the same as human.

For someone that try to learn electronics this comments is really hard to understand. What's "common failure mode", "MLCC", "DMM"? What does "old devices usually have dried out capacitor" means?

Machines are much more amenable and don't have loads of arbitrary unwritten rules

I'm sure system prompts of the most famous LLM are just that

Regarding preservation, even with a user-friendly format, platforms that allow downloading a zip archive or mkv in the desired quality provide no guarantee that the content will exist in 10 years. HDDs fail, they get lost, etc. The reason why old content is difficult to find is not because it's in the wrong format—FLAC copies of all albums ever made exist, and copies of all movies exist, but they are illegal to share.

It's not so much a technical issue as it is a legal one: the only way to reliably preserve content is to ensure it can be shared. One solution might be to limit IP duration to only a few years.