ByteCode.News
Submit RSS Atom Podcast Sign in

Back to the channels

#java

  1. Para Why is Texas limiting nevet?!
  2. dreamreal ha. ha. ha.
  3. Para Anything cool going on?
  4. dreamreal I'm adding an annotation for rss content to nevet so I can train it more gooder
  5. dreamreal but I found some bugs along the way, as one does
  6. Para I got a pretty cool maintenance PR in today. -17k rows + 15k rows, most of the diff is package-lock.json going nuts because I moved ancient frontend from whatever webpack to vite+typescript.
  7. Para Actual diff is like -6k rows of cruft.
  8. dreamreal heh
  9. Para And major stuff at that; lots of dao classes to records, more up-to-date and idiomic code all over, testcontainers so that the thing can now actually run the test suite in CI, DevX stuff... all in all pretty neat.
  10. Para Have to knock on wood, I don't get to spend a week on just making things prettier that often :)
  11. dreamreal As long as it works!
  12. dreamreal I've actually been really happy with the UI updates on nevet - I have been ignoring the nextjs UI except for bugs (and since neither I nor anyone else I know uses it: no reported bugs! No reports, no bugs, right?) and the new UIs are both much nicer in completely different ways
  13. dreamreal https://news.ycombinator.com/item?id=50022246 please upvote if you think it's worth it
  14. javabot dreamreal's title: "Listening Too Fast | Hacker News"
  15. nevet Listening Too Fast | Hacker News
  16. Para From what I understand, there's a specific language processing skill which everyone has and adeptness varies a lot from one person to another; reading and ingesting text without thinking what it _sounds_ like. Speed readers know how to skip the "sound" part entirely, and is the basis of speed reading.
  17. Para Basically you just need to look at a word to understand it, but something in us wants to push it to the speech part of our brain as well, and that's just extra processing for no reason as you're not going to speak aloud what you're reading.
  18. dreamreal ... so gimme the upvotes! That's not my karma that you're helping but it IS my site
  19. dreamreal and did you read the article
  20. Para I need to re-read it, I'm a terrible reader.
  21. Para soon :)
  22. dreamreal I actually pointed that out IN THE SECOND PARAGRAPH!!!
  23. dreamreal you proved the thesis!
  24. * dreamreal fumes
  25. Para Monkey together strong?
  26. Para Okay, to be serious. I tend to say "only jokes have punchlines", it's basically an inverse of "Put the conclusion first. Don't bury the lede." with the same basic idea.
  27. dreamreal sure, but ... again, you're addressing the *sender* and not the receiver
  28. sbalmos dreamreal: oh that's easy. unsafe { receiver = &*sender }.
  29. Para So I think my particular droning problem is a bit of a difficult one here - for me - to fit into what I think you're trying to say. I blather a lot. My LLM prompts reflect this, it's not that I try to cram a lot of rules and context and whatnot into a prompt, but I end up explaining a lot of tangential things. In human discussions I've gotten better over the years to provide mental checkpoints and
  30. Para pauses to keep things at least somewhat coherent, but my brain in actuality is still racing way too fast for decent discussion.
  31. dreamreal Hrmm
  32. dreamreal so you're missing it, then
  33. dreamreal which is fair
  34. Para Most of my prompting strategies nowadays involve "ask first, don't execute" in some form because of this. I've learned to chain myself.
  35. dreamreal can I still get the upvote though?
  36. Para I'd have to register.
  37. Para And I wonder if that would actually be net negative.
  38. dreamreal well, that's mine, too: I definitely demand explanation and requirement compliance, and I don't let it run tests in isolation ever
  39. dreamreal it isn't a net negative, no
  40. Para I really don't understand the sycopanthy in ChatGPT et al, no normal person wants a discussion of any kind work like that.
  41. Para It used to be absolute garbage a few years ago, it's been tuned down a lot since but it's still kinda horrible.
  42. dreamreal I think you have a vastly generous opinion of the normal people out there
  43. Para Fair, my "normal" benchmark is quite far from an average IT worker.
  44. Para (that'd be my sister who's worked in retail for +20 years)
  45. dreamreal In my experience there are a lot of people who will use an LLM as inefficiently as possible with absolutely craptastic guardrails, waiting for it to screw up, and then they're like "SEE?!?!?! IT'S ALL A LIE!" ... while someone else using the exact same service and model runs rings around them because they're actually using it properly
  46. Para Sure. There's actually currently two major LLM driven efforts going which could be used a context. First, the *craft tools, reimplementing Adobe products. The issue tracker is entertaining in its own right, with lofty claims of replacing all Adobe products and all. "Why?" applies there only superficially.
  47. dreamreal I tryto think generously of my fellow humans but they keep tryna make it hard
  48. Para The other one is PS5 emulation, which just this week has exploded wildly due to Sony being Sony. There's now _multiple_ emulators, each focusing on slightly different things, with 50...200x performance boosts. One emulator is focusing on building translation layer for the GPU instructions (they just reached 100% coverage), another one is running the PS5 OS, and then there's the more traditional "run
  49. Para this game" type of emulators also doing leaps.
  50. Para At the very base level these are the same, reimplement a specific piece of software, but interest and popularity and general acceptance are almost polar opposites.
  51. Para While people can agree that both Adobe licensing and Sony going digital sucks, somehow essentially the same solution is seen either as "waste of tokens but kinda neat" and "absolutely awesome".
  52. Para But, it's quite obvious people generally don't listen, no need to use some recent things as example for that.
  53. Para I had a customer support call (I was calling an ISP) today where I was interrupted because I was apparently explaining enough to the support person's opinion about the rather complex state of circumstances I was having a problem with.
  54. Para It got kinda frustrating because what I was trying to stay in the very beginning had to be repeated several times a bit later because of said interruption.
  55. Para And even that is kinda annoying; I recognize that as The Family Resident Nerd I know way too many things beforehand and can provide L2 debugging info right from the get-go, but there's no "skip first level of support" anywhere.
  56. NeXeN skip-level support, what a great idea! an extension for escalation!