Comments by "" (@adambickford8720) on "Continuous Delivery" channel.

  1. FP feels leaner to me, you don't need a GoF book just to do basic things in a 'good' way. You don't spend hours trying to shoehorn a non-oo concept into some object, arguing about how "Manager" classes are a code smell or getters are evil. The basic building blocks of FP seem harder to get at first, but i find the aggregate result to be more flexible and easier to understand.
    2
  2. GTFO low code folks, it's the 'this is the year of desktop linux' crowds turn!
    2
  3. Then you should be using waterfall, not agile. When they have to accept that no changes can be made to the plan without invalidating it, they'll quicky decide its the even worse approach.
    2
  4. Complete horseshit. The entire POINT of abstraction is to reuse solutions to solve even bigger problems. You can write a useful full stack app while being blissfully unaware of the OSI model OR pointers.
    2
  5. Its really the link from AI to robotics that's the issue. If AI had a will it couldn't really act on besides twiddling some bits it could be devastating, but not existential.
    2
  6.  @ainocorry3004  and this is why retros are a waste of time. "hey, we want the cameras off" "i don't prefer it and in another context, you'd have no choice, so too bad" "umm, ok, lets spend the next half hour talking about what we 'want to change' i guess"
    2
  7. The Java ecosystem is more important than java or the jvm, especially given docker.
    2
  8. It actually works fairly well if you are very diligent about IaC and test data generation, but if you aren't at near 100% automation, you're gonna have a bad time. In fact, our issue is it's so easy people spin up entire environments to test simple things, which is expensive unless everything is serverless. I think you are way underselling the effort to mock N apis for 'isolated' testing as well as ignoring what it DOESN'T test. You really want to test the 'glue' as well as the 'components' which mocking doesn't really achieve. When you have IaC mastered you can do things like bring up an environment that is dedicated to doing some long running 'nightly' job that requires several async components chatting through multiple pieces of infra (rest calls, MQs, api gateway, etc). It's hard to be overly confident mocking something like that.
    2
  9. I just can't imagine writing javascript when TypeScript is a thing. Understanding static types and generics is a pretty low bar for a dev.
    2
  10. I think it's when you really start considering the extended costs and roi on every 'major' decision: dev time, infra, long term support, compounding returns, optics etc
    2
  11. Have a relatively flat org, flexible deadlines/scope and empowered devs? Agile is a wonderful fit. I can also advise you on how to feed and care for your unicorn.
    2
  12.  @georgehelyar  Thats my point. You can't use agile in a waterfall business model, but I have yet to see a project where the ship date was decided on project state. Yet every single project was ostensibly 'agile'.
    1
  13.  @georgehelyar I've done it all including offering sass for software that wasn't written with that in mind. Overpromising service features is indiscernible from overpromising product features.
    1
  14. ​ @philthompson2239  Who said more code? It'll just take more iterations to reach an acceptable solution that doesn't require a savant to maintain. Given you missed the entire point your self compliment of 'as the smart one' is pretty suspect.
    1
  15.  @philthompson2239  I did not, they are all relative values meant to illustrate the power and value of fast iteration and short feedback loops. We might be duking it out for the bottom 2 producers in the org, only one is half the value of the other. It's not the flexing contest you seem bent on winning. The entire point is no matter your ability level the ability to iterate quickly will lead you to better designs and higher productivity. It can actually be a great asset to the less innately gifted and of enormous value in large teams of disparate abilities. I can't make you smarter but I can make you more efficient. I refuse to believe you're unaware of your aggressive tone. I hope you feel as foolish as you look trying to 'take the high road' now.
    1
  16. I bet those grapes were sour anyway.
    1
  17. You're conflating immutable with effectively immutable. If a bit of object creation is genuinely impacting your performance (it almost certainly isn't), you can use persistent data structures.
    1
  18. Gotta call bullshit on the culture being a result of the methodology. If my company found a way to increase productivity by 100% they'd cut deadlines in half AND increase scope by ~20-30%. If we aren't on the cusp of failing, we're being lazy.
    1
  19. I suspect the "schmoozing" aspect is disproportionately weighted when getting stats from faang companies.
    1
  20. I try to think of a few edge cases, even if it's just to define what happens. For example, what happens when the sum is larger than your return type can express? Does it (need to) work with negative numbers?
    1
  21. Usually that's where some kind of standard comes in. For example, all services will have to support the same JWT IDP (or something federated) to authenticate so each service can handle authorization.
    1
  22.  @stephendgreen1502  autonomous doesn't mean anarchy. You're still obligated to support the apis you publish. That why companies agree on standards as the lowest common denominator. If you agree on open api, it doesn't matter what language or framework you use, but yes, you need to support open api. Its no different than supporting HTTP.
    1
  23. It helps me manage tech debt when the reality of deadlines loom. If I see an implementation that could be better (internal coupling, some poor algorithm/data structure) i can let it slide knowing reimplementing it is relatively low risk.
    1
  24. IME devs are pretty convinced TDD works. It's the mangers that are penny wise and pound foolish about it.
    1
  25. As an interviewer, differentiate yourself and try to leave me feeling excited. Convince me I want to work w/you by saying something funny/insightful/etc. Show me some enthusiasm and engagement! Rant about the design of the java collections API, the ivory towerness of HATEOS, anything! This isn't a mid-term you're trying not to fail, this is your time to convince me you're a peer. I have a dozen more candidates w/the same alphabet soup of 'qualifications' as you; you will struggle trying to "out tech" them. After a certain minimum level it's the intangibles that matter.
    1
  26. @ At times, yes, but many times, it clearly does not. A lot of times it's just work. Someone has to write the rest endpoint and some queries. Having to come to a consensus about doing the DB vs controller first, etc, is not adding value in understanding. It's just a workflow preference. But now its a problem we have to solve just to move forward with the 'obvious' task.
    1
  27. The problem is that you can miss entire paradigm shifts because you don't want to learn the current 'fad'. Reskilling from near ground 0 vs absorbing along the way can create a self-perpetuating obsolescence cycle. Take java 8; that's not just an api, it's a fundamental shift in thinking. I've interviewed folks who clearly haven't learned much after java 5 and they are basically useless now. The trick is cherry picking things that will be helpful in the future, which is largely unknowable.
    1
  28. A lot of it is in the jdk now
    1
  29.  @ErazerPT  That's the hype. In practice, not so much.
    1
  30. Agile will not get you more lines of code out that door than waterfall, it will get the RIGHT lines of code out the door and start getting an roi sooner. If you need predictability, which most business contracts are written around, waterfall is likely the right answer.
    1
  31.  @m13v2  I mean a culture that requires 'rock stars' because of the poor planning, lack of cross training/kt, broken team interactions, etc. You end up w/a handful of these guys making stuff work in an essentially ad-hoc manner, which perpetuates the situation.
    1
  32.  @_Mentat  What does your bad company have to do w/the merits of agile?
    1
  33. I can solve your business problem no matter what it is. I'll copy/paste all of stack overflow if I have to!
    1
  34. Stupid reflection tricks and monkey patching, here i come!
    1
  35. Java the language? Sure. Vs other JVM languages it gets a lot less clear.
    1
  36.  @christianibendorf9086  Deleting a vertical slice of a monolith is the same exact thing
    1
  37.  @christianibendorf9086  Then you're doing it wrong.
    1
  38. Wait until they learn about deployments, rollbacks, versioning and having their entire 'design' destroyed by an edge case that can't be wysiwyg'ed. Then another, and another... then the dev has to make the boxes and click+drag them together.
    1
  39. The problem with the imperative version is it allows arbitrary complexity far too easily. In practice i haven't seen the typical map/filter/reduce type functions end up quite as complex as some of the multiple nested looping structures I've seen where every iteration sets booleans at various scopes to control the flow of the whole thing. For non blocking contexts writing imperative code can quickly get very complex without specific language support. For the functional version, its more an implementation detail.
    1
  40.  @JojOatXGME  I meant it more as a thought experiment than anything.
    1
  41.  @rosstempo3765  You clearly missed the point.
    1
  42.  @rosstempo3765  I've been using git for a decade, this has NOTHING to do with technology. My question is 100% methodology based to the unrealistic degree that technology doesn't limit at all. Does 'stress testing' the idea fall down and where? Specifically, "if we could theoretically create a deployment artifact on every keystroke instantly". This implies its so continuously merged that the concept of a 'branch' is meaningless. I'm not convinced that's a good (manageable) thing.
    1
  43. I'm fighting this now. "Lets just share a .jar of the DTOs". Works great until you get into versioned endpoints, mixing and matching versions (we have to upgrade the WHOLE API to version 2.0? i just need 1 endpoint right now!) and so on.
    1
  44.  @michaelbourke8967  homebuilding isn't agile, a flooring layout is about as waterfall as it gets. if the customer only has a vague idea of what they want to do w/the house and build it ad-hoc, it'll be a money pit too.
    1
  45. And yet most technical interviews are all about space/time complexity, language features/apis, frameworks, etc
    1
  46.  @leftaroundabout  now i'm picturing GLaDOS getting someone to read it gift card numbers 🤭
    1
  47. Same here. You can have a 'monolith' that isn't overly coupled to itself, it just takes discipline vs a physical boundary.
    1
  48. My boss wants metrics and code coverage is the 'nobody was ever fired for buying IBM' answer. So, for my use case, code coverage definitely solves problems.
    1
  49.  @guilhermebencke8525  been watching that strategy fail for 2+ decades now. gl w/that.
    1
  50. If you tap 'shift' 2x (search everywhere) and type 'productivity' you'll find how much all this has actually saved you And ty for not making this an AI upsell
    1