Skip Navigation

Posts
21
Comments
861
Joined
3 yr. ago

  • One Piece is best enjoyed as a manga. Reading it goes much faster and loses a bit of the anime character tropes.

  • Remember how you could play this on the local network with anyone who had a Nintendo DS? Only one person needed the game cartridge. So fucking cool.

  • You have no idea what you're talking about. Stop spreading dangerous misinformation.

    Honestly, delete this comment.

  • Ha. I'd expect nothing less from Theo.

  • Didn't Firefox just release a new feature that prevents fingerprinting? Hard to get a reading on Mozilla these days.

  • My driving instructor said the airbag could rip the skin off your arms lol

  • I suspect every language does this to some extent. Some good examples from Japanese:

    靴 = shoes 下 = under 靴下 = socks

    手 = hand 紙 = paper 手紙 = letter

    歯 = teeth 車 = wheel 歯車 = cog / gear

    火 = fire 山 = mountain 火山 = volcano

    Sadly (?) the Japanese compounds are often only compounds of the symbols, not the spoken words.

    • Saying goodbye to your friend before realizing you both parked next to each other, so you follow not too closely behind so they don't notice.
  • I just own the mistake and turn around. No one gives a fuck in public.

    It's funnier when you are leaving a social event and you need to change directions in front of the people you were just with.

  • Probably won't solve all of your problems, but I like to at least change git's default pager to delta.

  • If it's that prevalent, is it really improper at this point?

  • I agree with the article's ideas, but certain things about the execution bother me.

    1. calculate_order_total_for_customer. I'd just call it calculate_order_total. It's clear than any order will have a customer, it's in the type signature.
    2. is_user_eligible_for_discount. I'd call it user_is_eligible_for_discount. Because inevitably that function is getting called in an if statement, and you'd rather it read closer to proper English: if user_is_eligible_for_discount: ....
    3. "Designing for Tomorrow". I agree that dependency injection is a valuable technique, but it's not always strictly necessary and they seem to say you might as well always do it just in case. That's counter to YAGNI. Make sure you have an immediate use case, or let future you do it if you end up needing it. It's not hard to refactor something to inject a dependency.
  • Permanently Deleted

    Jump
  • "BREAKING" is right. He's breaking our fucking country.

  • As for actual coding, I use ChatGPT sometimes to write SDK glue boilerplate or learn about API semantics. For this kind of stuff it can be much more productive than scanning API docs trying to piece together how to write something simple. Like for example, writing a function to check if an S3 bucket is publicly accessible. That would have taken me a lot longer without ChatGPT.

    In short: it basically replaced google and stack overflow in my workflow, at least as my first information source. I still have to fall back to a real search engine sometimes.

    I do not give LLMs access to my source code tree.

    Sometimes I'll use it for ideas on how to write specific SQL queries, but I've found you have to be extremely careful with this use case because ChatGPT hallucinates some pretty bad SQL sometimes.

  • That does not look like steak.

  • I wonder how long I could survive on canola oil.