• 79 Posts
  • 238 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle







  • I see the next BF will be developed by Dice and 4 other teams? Well I wish them luck on good cooperation but that sounds really scary team-wise.

    But who knows, maybe it’ll help. Because Dice is … ok well I’m old so I don’t know if this is still true but I remember them as one of those studios that just keeps fucking things up. Bugs on bugs. Them and Creative Asembly (Total War). But as I said, I’m old, not sure how things look now

    Bonus rant: But boy, I remember one bug they introduced in BF3 with one patch. The bug was that the under-barrel shotgun attachement didn’t have its own damage, but took the damage from main weapon i.e. 12 pellets x 25 HP = 300 HP. I mean, shit happens but how much of a mess there’s in the code that this happens? I’d genuinely love to see that code. And! And! That testers don’t catch it during testing! How? That it flows through all the stages up to the production. Do you even have some tests? Is there a QA team? And I know I’m not crazy because as a follow up, the EA tried to step in to put things in order. Rant over














  • In my opinion yes, unfortunately. It’ll suffer from Gartner hype cycle soon but it’ll recover and will slowly get better every year to the point it’s really good.

    The worst thing is that I don’t see any “stop sign”. Like f.e. with self driving cars it was kind of obvious that it’ll get ridiculously complex in real life situations, thus having a problem with legislation and mass adoption. But with AI? I don’t know, I don’t see any stop sign … Maybe that it never reaches this high mark we all expect?




  • small tasks that you don’t expect to grow in complexity

    On one conference I heard saying: “There is no such thing as temporary solution and there is no such thing as proof of concept”. It’s an overexaguration of course but it has some truth to it - there’s a high chance that your “small change” or PoC will be used for the next 20 years so write it as robust and resilient as possible and document it. In other words everything will be extended, everything will be maintained, everything will change hands.

    So to your point - is bash production ready? Well, depends. Do you have it in git? Is it part of some automation pipeline? Is it properly documented? Do you by chance have some tests for it? Then yes, it’s production ready.

    If you just “write this quick script and run it in cron” then no. Because in 10 years people will pull their hair screaming “what the hell is hapenning?!”

    Edit: or worse, they’ll scream it during the next incident that’ll happen at 2 AM on Sunday