Comments by "" (@adambickford8720) on "ThePrimeTime" channel.

  1. I don't like coding in OO or Java, but i like the house it bought me :shrug:
    1600
  2. Shitting on vim after that montage feels like this was a targeted attack on prime. He didn't teabag you, it was a potato sacking.
    1100
  3. People don't seem to understand that O(1) is not FASTER than O(n), it just SCALES better; there's a breakpoint. Imagine a "hashcode as a service" rest call vs doing it in memory: it'd still scale better, but it'd take an awfully large 'n' to get there. I see people missing this in PRs, streaming/looping an array is often faster with small arrays than something like a `HashSet`. And in practice, its really unlikely either makes a tangible difference in most use cases.
    809
  4. My entire OOP experience. Hours of philosophy to create code that doesn't make sense w/o that philosophy and blows up on a simple structural change due to all the coupling.
    494
  5. Prime can't accept that his 'collaboration' argument is entirely an extrovert take. Having people interrupt my flow with their 'advice' is a NEGATIVE. WFH is great because merit takes center stage over politics and schmoozing.
    376
  6. You can almost feel it moving a mechanical something inside your machine with every character. I bet i could hear it with a stethoscope on an HDD.
    256
  7. Most people don't actually understand OOP either, but they put it prominently on the resume and opine about it incessantly.
    238
  8. So you write a micro service to hold the lightbulb and I'll use step functions to rotate the house. It'll scale horizontally, only limited by your budget.
    171
  9. Absolutely ethical, that's exactly why contracts exist. So this guy is just banned from that entire industry for life? The whims of this jackass? For a commodity offering? Pffft. Given how heavily they were tasking an INTERN they just look really silly crying 'ethics'.
    165
  10. When I review my own PR I'm taking off my 'pride of authorship' goggles and putting on my 'well ackshually' code review hat everyone else gets. And people think it's a joke when editors let you change the entire theme based on the db connection. Its only funny until its tragic.
    161
  11. But debugging is 10x more than just inspecting variables. Things like dropping frames, changing values on the stack, etc, saves me a ton of time.
    127
  12. I will not forget the blue-collar scrubs that were ecstatic that AI was going to replace me a year ago (while being completely oblivious that AI is the limiting factor in robotics).
    100
  13. Sorry prime, you're out of touch. Go to a typical corporate gig and what he's saying is obvious. It's by design; almost nobody actually has any amount of autonomy so big brains aren't that useful and engagement plummets. Your ability to schmooze and politic will dictate your success far more than any big-brain tech acumen will. That really sucks for the 'software craftsman' because over selling a jacked up 'solution' at 'the right time' is what wins the day. Places like netflix sucking the cream out of the dev twinkie doesn't help.
    96
  14. Compare a java dev w/1-2 years of experience to one with 10+. Pretty drastic difference, no? (sql injection? idor? session fixation? txn boundaries?) Same thing applies to 'devops'; k8s isn't just some 'configs', there's a whole ecosystem of best practices, frameworks rising/falling, architecture and so on. That equally applies to tracing/logging, etc The reality is you end up with devs doing stuff in application code that should really be infra, but that's not the teams expertise. They are just copy/pasting the top SO results and effectively `chmod 777`ing your cloud account to get the server to work. Generally, theres no checks/balances (that's a silo, yo!) until you're "hacked".
    76
  15. I have yet to meet a senior dev that's impressed by this stuff. Meanwhile, juniors are convinced it's inevitable. I know where my money is placed.
    73
  16. When I reimplement something that's now understood, I usually achieve a similar improvement in metrics despite being the same exact dude. It wasn't your 'Einstein level' of management that pulled that off, either. You exploited and scapegoated the actual talent and advanced your own career; that's corporate america in a nutshell.
    70
  17. It scales exactly as designed, for aws
    70
  18. Readibility is largely down to familiarity. I find it far more readable because i know what 'filter', 'map` etc are going to do even if not specifically *how*. Just seeing the coarse-grained operators I can get a pretty good feel of what's going on where the loop could be mutating anything anywhere. Not only is composition easier, it makes it harder to 'just add a boolean flag' to the loop that invariably goes out of control with complexity. And it is a builder! You're building a pipeline of operators that you eventually call with a 'terminal operator' like `foreach` or `collect`.
    64
  19. Scrum masters are the marriage counselors of dev teams. I have yet to see a good one that needs it.
    57
  20. TBF, i've been running that same grift in java for 20 years now.
    27
  21. Even if its wholesome and great, its one leadership change away from extortion. Hard pass.
    26
  22. Bad companies always find a reason. Remote is an excuse.
    25
  23. Been there. We had a team of 3 doing a PoC that was entirely non-blocking in java; `WebFlux` and 100% functional/reactive programming. We were crushing it by any metric. Then a couple people left, and the new custodians despised everything about it and did their best to fight it every step of the way. Productivity tanked and bugs thrived even with the same tech/code base.
    25
  24.  @Rohinthas  I feel personally attacked. Real talk: i was complaining about it back then: "we code in xml, bootstrapped in java, and its terrbile". Literally had a project that required writing java swing... in xml. Then at runtime having to xslt it into actual java, to be compiled and dynamically loaded at runtime. It was silly then and just plain offensive now.
    19
  25. When you're 20 ergonomics is 'bullshit'. When coming up on 50 it's the first thing you consider after where the bathroom is.
    18
  26.  @thelaw3536  in real life, what you claimed is nonsense. It's a completely different paradigm; the language is irrelevant.
    17
  27.  @suede__  Literally never had or seen that happen. The only thing i've ever had 'fail' due to debugging was timeouts and mulit-threaded code, which is completely expected.
    15
  28. I'm surprisingly impressed. Kinda crazy how much 'convergence' there is across languages, even the ones you least expect.
    14
  29. It's not just learning a syntax or grammar; every language has an ecosystem and expected idioms. IME java devs will likely take a `List<T>` whereas in C# it tends to be `IEnumerable<T>`. Java solutions tend to be more 'abstract' than C# solutions. C# tends to have better async support, which has a non-trivial impact on the code.
    14
  30. TBFairer, that's the most accurate prep for life after college
    14
  31. Databases are deterministic
    14
  32.  @Snail641  This situation 100% exists.
    13
  33.  @therainman7777  Or he's actually a senior engineer and telling the truth. Cope more.
    12
  34. I've unironically inherited long-lived code bases not far off from this. Literally velocity templates, to generate pig templates, to generate dynamic JS on the server that worked only worked w/the dynamic template generated by that request (mostly html ids).
    12
  35. I think it depends on the ROI of clever, which largely depends on how bright the dev is. If you understand "clever" it can save you tons of boilerplate and allow for very terse, clear code. But if your project is long lived and you have rotating crew of 'commodity' devs you really need to consider your LCD. The damage a 'good' dev leaves behind when a company typically hires clowns is immense. The design will be compromised out of ignorance and words like 'spaghetti' are all but certain.
    10
  36. We need less silos! Collaboration is the key to velocity! 1 month later... we are missing too many commitments due to all the distractions! People aren't managing their time properly!
    10
  37. The analogy i use is playing an instrument vs programming in midi. On a practical level, you can 'play' any instrument from extinct to fantastical and create entire arrangements by yourself with midi. It's always perfect and consistent. However, you are missing a vital tool: the feedback loop of ad-hoc creation; of improvisation and inspiration. Those things matter when you're not quite sure where you want to go but have a general idea.
    10
  38.  @freesoftwareextremist8119  100%. There are old fools as well. Still, there's generally a correlation with experience and specialization.
    9
  39. Premature abstraction is roughly 3,432,872 times worse than premature optimizations.
    8
  40.  @Fupicat  Oh, but they try to use it there too
    8
  41. This will make actual programmers even more valuable as the supply drops off exponentially.
    8
  42. As is the opposite
    8
  43. You're falling for snake oil. Enjoy.
    7
  44. Its like spam: it wasn't illegal until the government wasn't making money on stamps.
    7
  45. You are buying nothing by doing that as its still the callers problem. You've added no information and added noise. If you were translating it to a RUNTIME exception or adding some contextual information to the error string it'd be potentially useful.
    7
  46. IME success as a lead is largely dictated by the org and its culture. Some orgs just want an official 'face' at the meetings to represent the team, so you get a bit more paperwork and a couple chores. Some orgs are looking for a scapegoat or a miracle and you'll likely fill one of those 2 roles perfectly! It's a pretty different skillset and i'm not convinced SWEs are best positioned for the transition. You can't just push the He-Man button and come out the other side of a weekend bender w/working code (i.e. success) anymore. Good bye actionable error messages, hello politics and spin!
    7
  47. What really bothers me is that my portfolio manager is probably falling for this crap
    7
  48. No, because checked exceptions still send the control flow to outer space. Errors as values come back to the caller.
    7
  49. Agism and tech bullet lists mean 10 years of experience from 20 years ago is effectively useless; even legacy shops fancy themselves as on the cusp of upgrading and will pass you over. I personally love that there's always something new and shiny to play with, but I also get how it isn't really 'optional'. If you want to sit on your sweet vb6 or ROR skills, you'll eventually be stuck in a very poorly managed gig you hate with very few options.
    7
  50. You're going to supply a source, right?
    6
  51. But angular will put hair on your chest. Pair that with java, and everything after that will seem 'not that bad'.
    6
  52. When you've actually earned something, youll understand
    6
  53. Nope, control flow is the key. Exceptions are still worse.
    6
  54. In practice AWS will likely forgive that
    6
  55. So simple, nobody does it.
    5
  56. If in office is so great, why does it have to be mandated?
    5
  57.  @therainman7777  vs the juniors who think its magic. I know which i'm hiring.
    5
  58. I post on SO because if you've got a thick skin, you'll level up quick via Cunningham's Law ("the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer")
    5
  59. You will always be an "imposter" given the right context. Instead, you have to see it as you're the person who will grow the most by the end.
    5
  60.  @raptorate2872  Exactly what i thought.
    4
  61. It took me >3 months to get the 'gist' subdomain of 'github' unblocked for read access. I had to do all my research on my phone as most articles hosted the actual code that way.
    4
  62. If you aren't building tools/libraries, it's almost useless precisely because those efforts abstracted the need for common cases. Most java devs are completely ignorant of how threading works despite being a core language feature, they just know not to create new ones in a servlet. Thats all the business needs the vast majority of the time so ime there's usually 1-2 guys that actually understand this 'difficult' CS stuff. Or C) there are plenty of good jobs that interview appropriately and its less time and effort to just apply to those. IME, a lot of the l33tcoders have chips on their shoulders. YMMV.
    4
  63. At the end of the day you have to connect code/function/args together to work at all, so why settle for 'knowing' it works when I can prove it? Types add very little friction while giving massive yields in performance, refactoring, etc. Even structural typing is 1000x better than dynamic typing. I personally find dynamic typing harder because I have to dedicate my limited brain power to the state of the 'object' structure as well as its actual state.
    4
  64. And it shows
    4
  65. Feels like the 80/20 rule here. You can get 80% of the DX w/o huge penalties to performance, but that last 20% is usually where you hit the 'poorly performing leaky abstraction' point.
    4
  66.  @muhwyndham  just the fact i can trivially break encapsulation is huge, especially with 3rd party stuff.
    4
  67.  @DagarCoH  Sorry, i meant 'you' as anyone doing what was shown in the video :) It can be very helpful to report on other state at the time of the error for logging to debug it, even if you can't recover.
    4
  68.  @Nikkuuu69  on the other side, i relocated to a new city years ago for better jobs. I'd have never considered that w/o navigation.
    4
  69.  @AkimboOfficial  exactly this. Common sense conclusion: if it worked as advertised, why would they sell it to you instead of putting you out of business?
    4
  70. c-tier dev way over his head, trying to schmooze his way out of it. Just skill up, dude.
    4
  71. I actually get nervous where there ISN'T a day 1 patch for games these days. You know the game needs it, but it isn't ready yet so will be rushed so you're really looking at a "day 2" patch before it's actually playable.
    4
  72.  @rahzaelfoe3288  Programming in midi, not playing a midi instrument. You knew this before posting.
    4
  73.  @hungrymusicwolf  Exactly this. And the reverse is also true: could you think about it for a hot second before 'bouncing it off' me? If i had a nickel for every question where the answer was the top result on google i'd be retired.
    4
  74.  @sathalel4084  The irony of a low eq scrub coming out swinging about ineptitude.
    4
  75. If you think paid GCP support is bad when you're a current customer, you should see how helpful they are with migrating off GCP to aws.
    4
  76.  @Drummerx04  Imagination is nice, facts are better. I quick google says this is bullshit, so there's that
    3
  77.  @Rohinthas  I was hoping for more than a vague appeal to authority. There was a very specific claim we used to work 15 hours a week
    3
  78. Stateless modular monoliths are essentially the sweet spot; easy to do large re-factorings and modules allow you to manage it like microservices without the crippling cost of redefining a logical boundary. Microservices in a mono repo can make sense in some cases if you need that level of autonomy. The 'for real' polyglot, bring your own pipeline, infra, monitoring etc microservices architecture is rarely the correct answer in my experience.
    3
  79. Yeah... no. Java 8 is nothing like java < 8. Nobody mutates in place anymore, even in the core APIs. How's that corba package doing? Have you tried the `Flow` api i.e. reactive programming? You can't write a meaningful app without 100+ annotations. Hell, we aren't even WORA/JIT these days! Java is nothing like it was 20 years ago.
    3
  80.  @peppybocan  That's my point; it really isn't. Take a 20 year java dev who is stuck on < java 8 and show them this code. I know they won't understand it because i watch people botch it on a regular basis in interviews. They might grok what its doing, but they can't write or explain it. Its not just new apis; its an entire paradigm shift. Python and ruby devs are more familiar with this than an old school java dev: getUsers() .filter(u -> u.getAge() > 18) .limit(3) .sorted(Comparator.comparing(User::getRating)) .map(User::getName) .toList()
    3
  81. Feels extra good when the DBA supplies you with a more performant query and it takes a week of hibernate spelunking to figure out how to generate it.
    3
  82. IME the kind of agency prime is talking about is well above IC dev pay grade. In practice your advice/warnings are ignored, and the blame game comes in the future.
    3
  83.  @microcolonel  Whenever someone has a contorted 'analogy' they can be safely written off as an idiot
    3
  84.  @FromTheWombTotheGrave  then it isn't delivering on the promises, exactly like i said. Can't have it both ways.
    3
  85. Do you want it done right, or right now? The correct answer depends on the context. I'm not convinced JS etc is that much faster once you consider the entire ecosystem. I heard similar claims years ago when dynamic vs static languages debates were all the rage but never experienced it personally, even java is fine productivity wise if you use things like lombok, spring and a decent IDE. By the time you get done w/all the cloud BS the language seems like a small factor in the overall scheme. To me it feels almost like 'skipping tests saves time' argument where its only true in cases where it doesn't really matter.
    3
  86. Once you get used to having type information you understand the 'gains' of loose typing are a false economy. You almost always sacrifice tooling and, most likely, correctness. Its exceedingly rare that being loosely typed is a good thing ime. Sure, maybe if i'm doing something a bit more reflection based or dealing with a truly dynamic payload and maps are too janky w/o providing real safety.
    3
  87. Just simple styling could do it. Make the mutually exclusive behavior visually obvious.
    2
  88.  @artemkotelevych2523  What kills me is when its running in a managed runtime, in a vm, using a text based protocol (json), likely blocking on I/O... and this is the thing that gets cited 'for performance.'
    2
  89.  @CottidaeSEA  you are essentially trading performance for correctness and predictability. This is a trend among almost all the major languages. It allows frameworks to use identity checks for equality which is quite a bit more performant in large graphs. In practice, you are very unlikely to see a meaningful performance gap.
    2
  90. I remember working on a java thick client and there was more effort around if it was 'real mvc' than solving the users problem. Don't lose sight of the actual goal.
    2
  91.  @Drummerx04  Credible source that's accessible. Try critical thinking
    2
  92. Intellij lets me do everything via keyboard and it's at least as robust was what I'm seeing here. I think it might even have vim binds/mode specifically? Sure, it takes probably ~100x the ram to do it, but it's doing it.
    2
  93. I shoot for the smallest scope and visibility possible by default. If a function is 100+ lines long and the last few lines have all this 'cruft' in scope only related to previous steps, that feels messy. Related, i find reading in-line lambda functions far easier than have to jump down to a 2-3 line function in some other place, and you don't have the scope pollution issue.
    2
  94. Know what's cooler than xbox at work? Going home 2 hours earlier to play xbox with your friends and family.
    2
  95. The longer a tech is around the more likely you are to have had to support a poorly written/maintained codebase, which makes you hate the tech. JPA seems 'fine' but i despise every codebase i've ever seen it used in and rightfully hate it from experience :shrug:
    2
  96. I'd treat it like an instrument: just learn a songs you enjoy. Do things that keep you interested and want to keep doing it, the journey has to be pleasant too. Eventually you'll get fed up with hitting plateaus in self-learning and start seeing the value in things like data structures. You'll see that code that does 'the thing' you did in 1/5 the code and be intrigued; now you have a real reason to grind. I liken leetcode to jazz. Sure, its technically impressive and not everyone can do it, but it has little value in the real world. And certainly, nobody is going to pay you for it alone.
    2
  97.  @MetalGearsOfThought  allegedly
    2
  98. How them green threads treating you?
    2
  99. This is called "Offensive Programming". Fail fast, fail obviously. `The premise for offensive programming is to distinguish between expectable errors, coming from outside the program's line of defense, however improbable, versus preventable internal errors that shall not happen if all its software components behave as expected.`
    2
  100. Autotune feels like its essentially JIT? Also, once you understand the superset, is it really python? Type systems, structs, etc aren't just some syntactical sugar and take a bit of learning to truly understand.
    2
  101. Countries w/no military have the most prosperous people.
    2
  102. Java is attempting to keep everything "blue" via `VirtualThread`s, essentially multiplexing 1:N to real threads. It allows you to "block" on a value per normal function call semantics, but in practice the VirtualThread gets taken off the current 'carrier thread' by the jvm and placed back once it is unblocked. Scaling millions of virtual threads is fine.
    2
  103. Serverless is a gamble: will you make for up the rip-off $/GFLOP of compute with your actual duty cycle? 10x the cost but 1/20th the usage is a win. Of course aws knows that by the time you hit that breakpoint you're probably locked-in :evil-pinky: Remember, aws is renting you the same hardware in Virginia either way.
    2
  104. I bet no such mechanism existed for ranking the 'leaders'
    2
  105. Is it a complete trainwreck on wsl like intellij?
    2
  106. How's heroku doing?
    2
  107. So instead of writing bad code and refactoring, I'll be inputting bad prompts and reprompting? The more things change...
    2
  108. I'm looking to hire devs, not be some c-suite wannabe's day gig.
    2
  109.  @FromTheWombTotheGrave  sure. now let me know when its actually good and not just 'better'.
    2
  110.  @FromTheWombTotheGrave  lmao, ok child
    2
  111.  @FromTheWombTotheGrave  if your little fantasy takes off i'll take a whole month to learn it. If you're wrong you've wasted years chasing your tail with nothing to show for it. I've lived through many of these 'devpocalypse' to know this is just more hype.
    2
  112. Me not knowing what you do is a GOOD thing as I'm no longer having people waste my time with what is effectively trivia (i don't actually care what your kids are up to either). 12 people, and some don't know what the others are doing, implies your team is too big and likely 2 teams in disguise.
    2
  113. Literally posts a bubble sort 'gotcha' and says he doesn't do them! When you've constrained the problem enough that there are obviously 'correct' and 'incorrect' solutions, that's a 'gotcha'. Real problems don't have ideal, provable solutions, just tradeoffs or judgment calls from experience. I'm far more interested in someone who can articulate the kind of tradeoffs they expect they'll have to make, which tradeoffs are 'bedrock' and can't be easily changed (async/blocking, event carried state, etc). I want to hear about cost, risks, likelihood of being wrong, implicit assumptions about the solution, etc. It should feel like 2 guys riffing on a solution and you choose the one that went the best, not just who scored the highest out of 100 possible points.
    2
  114. And how do you suppose that's implemented?
    2
  115. Channels that provide a consistent stream of vapid/shallow content like this are what youtube promotes. You can complain about it... or grow a sweet stache and profit off of hot takes :shrug: (ProTip: create a 2nd channel to really work the algorithm!) There's a channel i enjoy that has specifically said they can't do 'deep dives' anymore because the algorithm will kill the channel in the interim. its too bad because even though there's an audience for it, he's encouraged to do 'readers comments' on a frequent basis instead. Clickbait or die.
    2
  116. It's been longer than 10 years; Java is infamous for abstracting things to the Nth degree since it came out.
    2
  117. I see PRs with injection attacks nobody notices while they argue about if the string "SUCCESS" should be a class constant even though it only appears once :facepalm:
    2
  118.  @kormannn1  The market says otherwise
    2
  119. I promise your screed of OO indirection is a complete mess to anyone who hasn't read at least a half dozen books on OO, design patterns, etc. And if you have, its suddenly 'elegant'. Pipe down FP zealots, i can say the same about hofs and monads. And yet both agree the lowly procedural programmer is the real hillbilly here :)
    2
  120.  @cosmic3689  Thats not even close to what i said. The idea that any turing complete solution is fungible is... just plain dumb.
    2
  121. Not only is there a ton to learn but everything being serverless means live services, which means moving targets in the backend. Same with the front end with evergreen browsers and evolving specs. There's a reason these gigs pay six figures.
    2
  122. The lack of xsd was the problem, the best you could do is create a Map of strings.
    1
  123. "InJeCtIoN AtTaCk!1!1" vs "isn't that an injection attack via string interpolation?" Turns out it is not string interpolation, though it looks a lot like it. That first case makes you look like a fool, in the 2nd you've expressed a concern while leaving the door open to being wrong, learning and growing. Of course if you're proven right, you can still pull out deez nuts.
    1
  124. People are moving away from mutability in general to the point where frameworks expect/demand it.
    1
  125.  @CottidaeSEA  its a different paradigm with its own pros and cons. its not that people don't understand, they just don't agree on the value of the trade-offs. immutable code is easier to understand as you don't have to worry about state over time. you don't have to 'manage' state, so it reduces bugs. it's a big part of why functional programming is on the rise and these apis support that nicely. if performance is critical you might want to consider something like persistent structs, object pooling, mutable structs, etc. but if you don't have measurements and SLAs, the 'performance' claim isn't very convincing.
    1
  126.  @CottidaeSEA  that's just one PoV but there are many other ways to think about solving that problem with different constraints. For example, most front-end frameworks model state changing over time as either a `signal` or `observable`, which emits immutable values over time. The reason is because when you're in a highly concurrent environment mutability is a nightmare.
    1
  127. AI is also the limiting factor of robotics. If SWE jobs are gone, everyone else will be < 10 years behind.
    1
  128. The most powerful gaming console has never 'won' a console war either. JSP is fine. Applets... deserve all the hate they get and more.
    1
  129. It's the problem space and solution paradigm that are hard, the language is almost incidental. I know this because I write immutable/functional java... and the oop dinosaurs say its 'unreadable' despite being "java". They'd have an easier time coping with OOP solutions in typescript.
    1
  130. It's easier to add code than to change it. Only couple/abstract when you have to and w/the smallest possible 'surface area'.
    1
  131.  @Rohinthas  A book behind a paywall isn't credible. You know you are being dishonest. We're done.
    1
  132.  @heisvi9317  Do people really not know the difference between a primary source and secondary source? At best this paywalled book is referencing primary sources. If so, cut the appeal to authority and go to those primary sources to make the case directly. This whole tangent is pure dishonesty. We're nowhere near that level of academia here, I'm setting the bar very low: show me the specific source for the claim around 14-hour work weeks. Spoiler: You can't.
    1
  133.  @kc12394  Still waiting for the claim to be substantiated
    1
  134. ​ @Alarios711  Lets be crystal clear on the dishonesty in this echo chamber: Its an appeal to authority when it just cites the authors credentials WITHOUT ADDRESSING THE QUESTION. That is a very specific question that should have many corroborating, primary sources. Let me type this slowly: it is not credible source for the purposes of corroborating this specific claim. But go on, type out another screed misrepresenting me but still not providing the simple evidence
    1
  135. Now talk about the literal millions of ideas that billed themselves as the next car and failed.
    1
  136.  @albertoarmando6711  Doing things like running jira on a single core w/128mb of ram. Save $10 on cloud. spend 1m on people waiting.
    1
  137. That happened to me coming back after angular.js hit the scene. I didn't understand why we needed node, it was going to be served from tomcat!
    1
  138. For vendor lockin: Iaas > PaaS
    1
  139. Been training my whole life for this; I already go through dozens of commands in my cli history to avoid typing that one command out.
    1
  140. Who would use VB without the tooling? Exactly. Now imagine that level of tooling with a good language.
    1
  141. About a year ago I went from HA, 24/7, proprietary everything, 'change advisory board', etc. to a small app just used by internal users between 9-5 and no PHI/PII. I feel like I'm getting away with murder; similar pay and its an order of magnitude easier and 2 orders more pleasant.
    1
  142.  @zoeherriot  It explains the quality of most teachers
    1
  143. aws lambda is in a similar situation with reactive/async code. aws is going to block on a req/resp, it's not going to reuse that 'vm' for the next request as aws will give that request its own 'instance' of the 'vm' (could be code, image, etc). Java virtual threads don't color your functions. I know, right?
    1
  144. Eh, its the internet. The fact they didn't question my gender, sexual preference, race, etc. means it was refreshingly cordial. More practically, if they weren't like this it'd be n00b overflow with verbose, go nowhere questions that aren't helpful to anyone flooding the site.
    1
  145. If you see theo as anything more than contrarian entertainment, I genuinely don't care about your opinion.
    1
  146. ​ @Forty8-Forty5-Fifty8  That's my point. The lower hanging fruit will go away, pulling up the ladder. I see a lot not clearing the gap. There will also be many that will be deterred from entering the field all together. And its not like people with actual understanding aren't using these tools as well.
    1
  147. The 600 column thing isn't that crazy. I've seen it where a `User` had a couple dozen properties, some of which were collections of other entities that also had collections of entities. So now you are either over-fetching a whole lot, N+1ing, or you're having to manage a 'fetch' strategy to tell the ORM which subgraph to populate. You know, like a sql projection but w/all kinds of vestigial null properties that are semantically ambigous.
    1
  148. Corporate coding 101: don't level up the devs, dumb down the code. Better devs will leave and then we have to hire expensive ones to replace them.
    1
  149. What a great display of how you can know so much but still end up with imposter syndrome. Its also been 10+ years since i got to flex on someone for using a scriptlet in a jsp. Why'd i even bother? 😿
    1
  150. This feels like using a typesafe language via its reflection api to solve 'regular' business problems. That's going to be... unfun.
    1
  151. No, it's not. Penny wise, pound foolish.
    1
  152.  @nemanjatrivic9505  You missed the ENTIRE point of the conversation. You can write an entire website using print writers and string literals in almost any language. However, almost any templating language will be more productive and maintainable because that's what they are designed for. You're assuming there is no ROI, which is self-evidently wrong.
    1
  153.  @therainman7777  you've more than proven you're ignorant. I literally couldn't care less about your opinion.
    1
  154. It's also about employers and expectations. When I started those frameworks didn't exist so it was just expected you would have to spend days to weeks just getting cross browser javascript working. Writing your own libraries wasn't unthinkable, which was an opportunity to learn how to write larger codebases (even if you were one of the red shirts finding out OOP is mostly BS 😥). Now you're expected to deliver something that's actually useful, but the prereqs for `useful` is pretty high. By the time a more senior person chunks it down to something the jr can understand, they might as well finish it off. But then we have a bootstrapping problem.
    1
  155. "I re-wrote my app in dogshit.js and it took HALF the code!!". Right. You now understand the problem and wrote an appropriate solution.
    1
  156. I've watched a scrum master cause an entire high functioning team to quit. Adding tons of "structure" doesn't add value if the team is already performing well. It actually slows everything way down.
    1
  157.  @juicymelodic  nope. Years ago I could get a gig just doing html/css/js. No frameworks, no server side, etc. Due to tech (including ai), I now have to do front end with N frameworks, backend distributed MSA design and cloud infra. Am i being exploited? Is this 'the man' stealing my wages? No. Setting up a datacenter used to take literal physical labor and now it's a few clicks in an html form. That skill is now genuinely worth less unless you leave near a cloud providers data center. When advancements come out you either skill up or get out. An artist should now expect to deliver an actual product/service/experience. Standalone art just isn't that valuable anymore. Is it better than AI art? Sure, but MDF is far more popular than 'real' wood for a reason.
    1
  158. Common sense take: If AI was that good, you'd be using it to 'disrupt' my market instead of trying to sell it to me.
    1
  159.  @evanhu2661  Thats the problem; OOP advocates rarely have anything to compare it to but are convinced its the best.
    1
  160. @ And those same countries will do that same with AI. That was the point.
    1
  161.  @Saliferous  Like your post plagiarized the alphabet?
    1
  162.  @Saliferous  2011 called, they want their meme back. But tell me how you don't understand ai without telling me...
    1
  163.  @Saliferous  I hope you're taking yourself seriously, cuz nobody else is.
    1
  164. "Ticket Grooming" (pointing) and Sprint Planning are separate, otherwise it's just too long. Then of course dailies and don't forget the retro! The best part is all the whining about the 'burn down' chart after all that managerial masturbation provides nothing of value.
    1
  165. Dear ChatGPT; as an incompetent dev who's about to be fired, why is prod down?
    1
  166. You know how people can live in a city for years but can't go more than about a mile without GPS? That's now your devs with AI. As long as they are only traveling to well-known places, you'll be ok.
    1
  167.  @chigozie123  i dont have to restart the app server, get things back to the state that the bug appears in, etc. I can just return/change a new value from the debugger, no need to bounce the app. You can also use good old 'printf' in a non-suspending break point; no need to soil the source code. Then, if i don't need it i just disable the breakpoint vs deleting the printf. If i need it back, i re-enable the breakpoint. You can even mange groups of these printf breakpoints in intellij to enable a bunch with one click. The fact i can drop frame in case i manually step too far is a coincidence 👀
    1
  168.  @CodeFun691  or, just maybe, that's the kind of codebases actual engineers end up with? Why is it the more aggressive they are, the dumber? Its beyond correlation at this point.
    1
  169.  @vitalyl1327  you might be in some crazy edge case where it's not useful, but for 99.9% of projects it's an unambiguous win. Aggregating and analyzing gigs of logs for simple stuff is easily an order of magnitude less productive in the vast majority of cases. And you missed the point, logging is a small fraction of what a debugger is capable of. Logging only solves that portion with debatable 'gains'.
    1
  170.  @NeoChromer  i honestly feel its insecure devs trying to 'flex' they don't 'need' a debugger.
    1
  171. The other 'problem' with many small methods is the method name is a form of 'documentation' with the same issues as comments. Then you end up with stuff like `getStateCode()` that actually also returns Canadian territories since we onboarded customer X. Even when correct, unless that's making a service call or something, the simple inline predicate is probably less cognitive load than navigating and retaining the 'helper' method.
    1
  172. It's a passive-aggressive bait-and-switch and everyone knows it. You wouldn't have this community in the first place if you pulled that crap initially and you know it.
    1
  173. At a certain level of drama queenage it's not worth it, even if i agree at some level.
    1
  174. Because there's always that tool that wants to do it in 1 line: record Measurement(String station, double value) {} stream(input.split("\n")) .map(line -> line.split(";")) .map(vals -> new Measurement(vals[0], Double.parseDouble(vals[1]))) .collect(collectingAndThen( groupingBy( Measurement::station, collectingAndThen( toList(), a -> a.stream() .mapToDouble(Measurement::value) .summaryStatistics())), grouped -> grouped.entrySet().stream() .sorted(comparingByKey()) .map(entry -> "%s=%.1f/%.1f/%.1f".formatted( entry.getKey(), entry.getValue().getMin(), entry.getValue().getAverage(), entry.getValue().getMax())) .collect(joining(", ", "{", "}")) ));
    1
  175. Oversold and scam are on a spectrum.
    1
  176. SIMD? i don't even know what architecture aws runs my stuff on at all and it could vary from run to run. Still super interesting to know what i don't know
    1
  177. Pedals and steering wheels were practical at one time but are essentially obsolete these days. However, it still works fine as a UI even if a joystick could pull it off. Moving away from that better provide some real, tangible benefits. 'innovative' and 'diversity' aren't selling points.
    1
  178. Real talk: you learn them both and cringe as every PR is just imperative programming cargo culting the trappings of your advocated paradigm. You slowly let the imperative soy boys win because you don't have enough time (and talent) to do it 'right'. Incoming legacy app.
    1
  179.  @perc-ai  There's a TON of content out there. Look up anything about reactive programming on the server
    1
  180. If their devs are this dishonest, can you imagine their marketing team?
    1
  181. Blameless... until we need to decide promotions or layoffs.
    1
  182. Turns out the stripper doesn't care about your responses either. Or your therapist. Stop paying either and see what happens.
    1
  183. The stunning lack of features I can rationalize; the 1 letter variable was the death knell.
    1
  184. TBF, I spent many early years flailing on the jvm with google until I figured stuff out that the c++ guys were convinced I'd never understand. If used properly i think it could be a great bootstrapper for a dev with grit.
    1
  185. Groovy had a similar 'opt in' to types and it was as awful as it sounds. Whimsically typed is the worst of both worlds, not the best.
    1
  186. I feel like i should have stronger opinions on this; I just try to keep that serialization stuff in some dark corner as isolated as much as possible from my precious 'real code'.
    1
  187. TBF, you don't know how bad jeremy was to start. Maybe he finally finished that react todo app.
    1
  188. At least they skipped the equally bloated and inane scrum ceremonies before it hit 'development'
    1
  189. Not really: var nullOrValue = Try.of(() -> "foo") .mapTry(this::someExceptionThrowingMethod) .mapTry(this::randomNPEMethod) .getOrElseGet(null);
    1
  190. You start doing smart shit when you run out of dumb shit to try.
    1
  191.  @RenThraysk  what, exactly, would it take for you to admit you were wrong?
    1
  192. As a Java dev, i was super excited to see real competition when .net core came out. At a technical level, it's just better in pretty much every way. I think i'm the only one that noticed. I still follow c# to see where java will be in 6-8 years.
    1
  193. Anything that pays well has some limiting factor; its either difficult, dangerous or disgusting. Your call.
    1
  194. DEI as a pillar? Aggressive IP defense? The most insufferable community this side of scala? No thanks.
    1
  195. Your scrum plan, your 'rewards'.
    1
  196. I don't get the hate on TS' `any`. I view it like reflection; you're specifically opting to sidestep the guarantees of the language to do something "clever". You generally shouldn't need it, but when you do, you better know what you're doing.
    1
  197.  @ThePrimeTimeagen  If you made a 3rd channel i'd sub to that one too. thats the game
    1
  198. Isn't Rust just a linter over machine code?
    1
  199.  @Microphunktv-jb3kj  it does exist, but it's not at all what these morons think it means. It's an actual crime, not some soy boy sad he isn't more valuable.
    1
  200. The only way a counteroffer works is when your company is so poorly run, they never fix the root cause of any problem and can't position themselves to retalite. Till the next raise, because you're going to have to coerce that one out of them too.
    1
  201. If it's so great, why are you selling it to me instead of 'disrupting' my market? Surely my lunch is but a few prompts away from being eaten?
    1
  202. I lot of development is fashion. OO and FP are essentially complete opposites, yet they both work. static/dynamic types also both work, despite both camps claims against the other.
    1
  203. I so want to dunk on prime for being borderline illiterate when reading out loud, except I do the same damn thing :(
    1
  204. Cuz generics are sooo extravagant.
    1
  205. Cutest couple in tech!
    1
  206.  @neoncyberia  Heard this w/rational and uml. Heard it again with BPMN. RAD and all the low/no code hype too. Heard the fearmongering again w/offshoring and nearshoring. Turns out, it isn't a tooling problem.
    1
  207.  @yakovAU  no, they don't, they already know how to code. They aren't the ones desperate for a market disruption that isn't coming.
    1
  208.  @yakovAU  That's the hype the juniors can't get enough of.
    1
  209. We could 'scaffold' a full crud site from a db schema 20 years ago with ruby on rails (or generate the db from the objects). And yet, its not even really a player these days despite that 'productivity'.
    1
  210. I just need enough to get 'hello world' off the ground. Once there, i can break and fix it repeatedly until i grok it. At that point i'll search around for specific things that i'm inferring incorrectly or try to understand why my intuition was wrong.
    1
  211.  @homewardboundphotos  do you know how many of these predictions you clowns have made over the years? But this time is real, yo!
    1
  212.  @TheCactuar124  He straight demonstrated it you tool
    1
  213.  @spyroninja  people like you are exactly why going to the office sucks.
    1
  214.  @youtubeenjoyer1743  Your experience is very limited
    1
  215.  @yyny0  Despite your confidence, it can in java at the very least: Thread.currentThread().getStackTrace() and that can be put into any kind of return value.
    1
  216. Why do you even want to live now?
    1
  217. Microbenchmarks are usually testing disk cache, branch prediction, etc. more than any meaningful code. Sometimes the smallest change can completely invalidate the findings. Don't write specialized code unless you have a specialized problem.
    1
  218. Extroverts are often given disproportionate weight/success in 'live' interactions since being likable, well-spoken and/or quicker witted rule the day. They also tend to do better on politicking due to 'people skills' like spin, reading the room, body language etc. Of course those folks want a return to the office; I'm sure the HS QB is way more into the homecoming game too!
    1
  219.  @jongeduard  cuz nobody trusts a company more than Oracle!
    1
  220. Shouldn't that much 'talent' be able to produce something better than a bootcamp 1st project? Do you have the same squandering talent with money?
    1
  221. Given I think it's impossible, this is bad news
    1
  222. Java checked exceptions are kind of the same thing in that they are 'viral'. They are also incredibly unpopular.
    1
  223. There's a reason no other language has used checked exceptions. Even spring, the defacto standard in java, converts them to runtime by default. On paper they're great, in practice they suck.
    1
  224. Can't wait for the kids to start saying I'm out of touch because chatgpt has been stroking their ego for 4 years and convinced them they are a savant.
    1
  225. I could use a drum machine and save a ton of time and money, but what if my goal is to learn the drums and not write derivative track #53454334?
    1
  226. Lose 5 billion? WB wishes they were that successful!
    1
  227. My issue is that in java, JPA is ~100x more complex than the SQL you're abstracting... even if it doesn't leak. Most vexing of all is when the DBA says 'here, this query uses one millionth of the resources' and you have NO IDEA how to get the actual ORM to spit that out, but the DBA query doesn't quite line up w/the object boundaries in your code so you can't just 'raw dog it'. And that's if youre LUCKY... For example `db.selectAll().count()` may do a count query... or it may pull back the entire DB into a list and then take its length. Nobody can answer w/o reading the docs, then you find out 'it depends' on 100 different settings, your driver, the actual RDBMS and the versions of all those parts. I know exactly what `select count(*)` does even in RDBMs' i have never used.
    1
  228. Gherkin/cucumber, bpmn, the list goes on and on. Real talk: the devs end up with it or its neglected.
    1
  229.  @keoghanwhimsically2268  ah, good call, my bad!
    1
  230. I wish this attitude was more prevalent. These days, if someone fails it's 'proof' that they weren't supported enough (so obviously someone else's fault).
    1
  231. He's far more likeable and charismatic than i would have guessed going by my memory of his blogs back in the day.
    1
  232. Clean code is adding architectural layers before asking what the problem we're solving is.
    1
  233.  @wlockuz4467  Instead of getting the data and applying your code to it (like a loop), you pass your code to the monad an IT will apply your code to the data. You just don't exactly know if, how or when cuz abstraction, which is the entire point. For example, in an Option/Maybe/Try monad your code will only be applied to the data if it exists.
    1