• 0 Posts
  • 86 Comments
Joined 3 years ago
cake
Cake day: July 4th, 2023

help-circle
  • Prism is neither near nor far sighted issues.

    Prism is a muscle problem, where the actual muscles of your eyes get weaker because you arent using them as often to focus on objects far away, so they lose flexibility.

    Akin to how if you sit in a chair all day and arent actively stretching purposefully, you lose flexibility in the rest of your body too.

    As far as I know, focusing on objects has no impact on eye shape changes, its just genetic on which way your eyes start to squish/stretch as you get older. Thats just a byproduct of the fact our face and tissues change as we get older.


  • The “dont sit close to the TV,” thing is objectively truth and is even worse today.

    I used screens a lot growing up, including a laptop and various portable games like the Gameboy and PSP

    This led to my eyes slowly developing the need for prism on my lenses, because they over-correct now focusing on close objects.

    Nowadays smart phones are this problem but way worse too, if you sit in the dark holding it way too close, especially with glasses on, you are slowly deteriorating your eye muscles.

    Unless you exercise them of course, every 20-30min. But most people dont do that.

    I now am having to do constant daily exercises to slowly undo my prism, a year and a half ago I had a prism of 5.0 on each eye, this month I finally got it down to 2.5, which is solid progress!

    However VR doesnt have this issue, its a virtual image that appears to be 2 to 10 or more meters away, so your eyes are focusing like looking at something far away.









  • by the types of people you maybe don’t want using your code anyways

    …companies? Sure I guess, if you want to angle your career trajectory towards “unemployable” by all means lol.

    Personally anyone doing this I’m going to be more likely to use their code

    I am a tech lead, if any dev under me intentionally added/used a tool to our systems because it had malicious undocumented behaviors of any kind, they would be fired immediately and any company that contacted us for reference would be informed of their behavior.

    To be clear, this is the scenario of

    Me: hey I saw you installed [tool], that thing is flagged by our systems for the maintainers having done malicious undocumented stuff in the past

    Dev: haha yeah thats why I used it

    Me: you are joking right?

    Thatd be an instant high level escalation to “strip this person of privs and get them off our system asap, and HR now has to be involved”

    You dont fuckin do shit like that in a real company if you wanna stay employed lol.


  • Most open source maintainers never “license [any] stuff you maintain for big bucks” that is often hard to do and/or goes against the philosophy of open source entirely.

    Uhhh… no this is actually very common. Usually with scaling licenses, “free for use if your company is below [threshold]”, its super common…

    And I don’t even think this is malicious behaviour as it just nukes the code of this package and nothing else if you are not being careful yourself…

    Are you even reading what you just wrote lol.

    Being “sorta” malicious is still malicious. And companies usually have zero tolerance for that shit.

    If you don’t do version control you are not a good programmer, imo

    You really underestimate how much damage this could do then, lol…


  • They only documented it after all the outcry, which is way too late.

    Documenting it post release still counts as having released undocumented behavior.

    And if its malicious (which this 100% is), then it doesn’t fuckin matter anyways lol. You now are treated akin to a trojan maintainer by companies. You’ll get flagged as “don’t ever use anything by this person”

    Super great way to get yourself flagged and lose any opportunity in the future for possibly licensing stuff you maintain for big bucks. What company would risk paying money to someone who does childish stuff like that lol


  • How to get yourself blacklisted by large sweeps of the FOSS community:

    Step 1: Include any kind of undocumented subversive behaviour in your thing.

    That’s it, doesn’t matter what the intent is, simply by demonstrating you are willing to include anything that is remotely subversive without being open about it is usually enough to get blacklisted by a lot of people, because if you did it once… who’s to say you won’t do it again, but possibly worse next time?

    People are extremely coldly receptive to anytime a FOSS dev throws a sudden undisclosed anything in their tool, let alone one that is actively malicious.

    If I’m gonna depend on work life on anything FOSS, I ain’t touching anything like that, regardless of intent, with a 200 foot pole lol.

    All it takes is one button click to get notified:





  • Theres also a massive distinction between consuming something necessary/important, vs consuming something 100% optional.

    Harry Potter isnt food, shelter, or any other kind of critical necessity.

    Theres literally countless better alternatives to Harry Potter media you can choose to consume from that doesnt directly put money straight into the pocket of someone actively funding direct harm

    This isn’t multiple layers of washing here, that money basically goes straight towards actively harming minority groups.

    Its not even a good fucking book, and I used to be a fan of it as a kid, but I went back and read my old books and… it just fuckin sucks dawg, its not good lol.

    Go pick like, any other fandom at least.



  • Have you actually read the study? People keep citing this study without reading it.

    To directly measure the real-world impact of AI tools on software development, we recruited 16 experienced developers from large open-source repositories (averaging 22k+ stars and 1M+ lines of code) that they’ve contributed to for multiple years. Developers provide lists of real issues (246 total) that would be valuable to the repository—bug fixes, features, and refactors that would normally be part of their regular work.

    They grabbed like 8 devs who did not have pre-existing set up workflows for optimizing AI usage, and just throw them into it as a measure of “does it help”

    Imagine if I grabbed 8 devs who had never used neovim before and threw them into it without any plugins installed or configuration and tried to use that as a metric for “is nvim good for productivity”

    People need to stop quoting this fuckass study lol, its basically meaningless.

    Im a developer using agentic workflows with over 17 years experience.

    I am telling you right now, with the right setup, I weekly turn 20 hour jobs into 20 minute jobs.

    Predominantly large “bulk” operations that are mostly just boilerplate code that is necessary, where the AI has an existing huge codebase to draw from as samples and I just give it instructions of “see what already exists? implement more of that following <spec>”

    A great example is integration testing where like 99% of the code is just boilerplate.

    Arrange the same setup every time. Arrange your request following an openapi spec file. Send the request. Assert on the response based on the openapi spec.

    I had an agent pump out 120 integration tests based on a spec file yesterday and they were, for the most part, 100% correct, yesterday. In like an hour.

    The same volume of work would’ve easily taken me way longer.