ByteCode.News
Submit RSS Atom Sign in

Back to the channels

#java

  1. deebo dreamreal: if you can find the channel name, you can request the channel page in xml for rss and get it there :), even the video page might respond to content-type application/xml+atom or what ever it is
  2. dreamreal deebo: wait, for what now?
  3. deebo youtube links
  4. dreamreal Oh, thank you. Actually, the youtube page itself has the content, I was just extracting it improperly; fixing that. Twitter is going to be a separate issue.
  5. dreamreal hey, https://x.com/dev_maims/status/2022588131623501927
  6. dreamreal okay, so javabot's lost it too.
  7. [twisti] is he making hateful blog posts too
  8. Chronos Of course, experienced people know that the "refactor later" step rarely, if ever, happens.
  9. gas51627 Hello.
  10. jottinger oi
  11. if-p-then-q Hiya! Decided to go back to Emacs and see if I could use it now I understood Java and Maven better, writing my unit tests, it's actually great! https://paste.pictures/VmpAmURks2.png
  12. Para TBH I see that as a downgrade but if it works for you, great.
  13. if-p-then-q In some ways compared to IntelliJ IDEA it is a downgrade for Java programming, but since on this machine (my main study machine) my Window Manager is Emacs, it makes sense for me to develop in Emacs even with some small concessions to convenience, but everything necessary for smooth development (provided understanding of CLI Maven) is here.
  14. if-p-then-q Also I have IntelliJ installed on this machine and can still use it no issue, with its window managed by Emacs :)
  15. if-p-then-q Appreciate that there is a really good linux version that was simple to install too, and that the Toolbox app worked despite me having a tiling window manager, just worked natively and popped up a window.
  16. if-p-then-q I had a question regarding unit tests and mocking actually: so when values are randomly generated, it is sufficient to test that they *are* getting generating at all, by mocking them, and returning a set value? I am using Mockito
  17. if-p-then-q Shouldn't I be doing a statistical analysis on the distribution of their values and conformity to range?
  18. Para Well, then the question becomes whether your randomly generated data is correct and comprehensive or not.
  19. if-p-then-q Ah I see, yes, that does not matter really, well conformity to range does, so should I test specifically for that?
  20. Para I don't really see why that would matter.
  21. Para Point of generative testing is to reduce otherwise too large workloads by taking a sample of all the possible values.
  22. Para It's doesn't really matter what the sample is or how well it distributes etc. as long as it conforms.
  23. Para With the big exception that if you're trying to develop a new, say, normal distribution algorithm and you want to make sure that conforms to such things.
  24. if-p-then-q I see... yes. I believe my current tests are therefore sufficient.
  25. if-p-then-q I wish I had developed the tests in tandem with the program but I had no idea how to write them before and a blockage of action due to blockage of imagination.
  26. Para Eh, such happens.
  27. Para TDD is good for solving specific problems but exploratory development tends to be really hard if you try to do it through a test suite.
  28. Para Or maybe not hard but...tedious?
  29. if-p-then-q Hmm ok
  30. if-p-then-q My usual approach is System.out.println
  31. if-p-then-q But it would have been handy to have some sort of programmatic testing as I was going along in places, which I could have then filled out at the end to present evidence of a rigorous testing regimen in my report.
  32. if-p-then-q Not that it matters, I am enjoying writing these tests. I'm going to get on with it now. Oh how do I run the tests?
  33. if-p-then-q In the CLI?
  34. jottinger mvn package!
  35. jottinger ~tdd
  36. javabot TDD stands for "test driven development," a methodology that emphasizes definition requirements as test conditions, and generally writes those requirements as tests before implementing functionality. Wants a rapid test cycle, and is really nice when requirements exist. See ~junit, ~testng.
  37. jottinger anyone saying tdd is tedious is doing it wrong
  38. jottinger for one thing, it's tee-dee-deeyous
  39. jottinger for another, it's a fantastic way of ensuring you understand what the code is supposed to do and does it
  40. Para What TDD gives is iteration speed and certainty. Both are good.
  41. jottinger What it TAKES is confusion and stupidity and a little time to understand what you're actually trying to do.
  42. jottinger When you don't know what you're attempting, TDD punishes the crap out of you. And it should.
  43. jottinger if you don't know what you're doing, everything you do is going to show it.
  44. Para Then there's of course REPL but I don't think anyone in Java world really uses that even though there's now one available :)
  45. Para ...which kinda gives me an idea, I'm going to force myself to use it in my next hobby project.
  46. Para I kinda need it as well, I'll be calling an API with really annoying rate limiter so having an actual cache while live developing will be useful.
  47. if-p-then-q There's a Java REPL???
  48. Para jshell, kinda
  49. Para ~jep222
  50. javabot 'JEP 222: jshell: The Java Shell (Read-Eval-Print Loop)' can be found at http://openjdk.java.net/jeps/222
  51. nevet javabot mentioned url: http://openjdk.java.net/jeps/222 ("JEP 222: jshell: The Java Shell (Read-Eval-Print Loop)")
  52. if-p-then-q Interesting thanks
  53. if-p-then-q is JavaDoc.io often slow?
  54. if-p-then-q Ah it's loaded!
  55. cheeser javadoc.io, i think, explodes the javadoc jars on first request before serving (and probably has to download them) so there will be some delay
  56. if-p-then-q Ok thanks :)