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