DivisionSol
Joined 11 years ago
Joined 11 years ago
I don't think anyone assumes when they take the cheap shipping option that they are eating a 10% chance the package never shows up. Nor mis-matched packages. Nor sudden calls from collections. Nor being re-labeled in the database as a 'distributor.'
Author gave time for them to work out the bugs between each attempt, and, seems each attempt went worse.
Classic post-2010s-era support quality.
Example 1: Changing `s` to `displayScore` doesn't fix the problem the code is using `p1`, `p2`, `p1N`, `p2N` AND defining a new `p`. WITH multiple ternaries and 3 mid-function returns.
Example 2: Reasonable, but now you have two functions with similar signatures. Reducing the number of indentation is always good.
Example 3: Creates ANOTHER layer of indentation. Without add'l context the code looks like it could be reduced to a series of inverted conditions with happy/golden-path style sequential if-s instead of 5 indentation deep.
Example 4: Pet peeve and chided by a lot of linters. Empty blocks are generally frowned upon. (You say: "If not equals DO" not "If equals don't do anything ELSE")
Example 5: Good in the context of testing, annoying in that it is a function with a single line. You'd probably be better off stubbing the User class all together. I mean you're already providing a User-type object.
Example 6: Great, 10/10 love it. Would remove the {} and just toss the Throws on the if-statement line itself but that's personal taste.
Example 7: Not awful, but I like to front-load my variable declarations so you can get error-handling out of the way at the start of the function then use those variables to do the computation later. More up front about saying: "Here are the items I will use later in this function"
Example 8: Probably not a simple refactor. If you aren't going to update all the locations in which an "Amount"/"Currency", you're creating an artisanal class for a single use.
Why am I code reviewing this article? Shoo.
Of course you'll need new maps, unit tokens, and scenarios custom to your clone.
I know it is easier said than done, but, rightsholders sit on obscure IP like a dragon on a hoard. If they DID make a new game based on this Squad Leader game, it probably wouldn't be the same game.
Quick edit from reading another post: If one just wants to play VASL looks like what one would want. Reimplementation of the rules in another engine, boom.
And I'm sure we can do scientific research on robot animals just as well as normal animals, just a different kind of research.
Seems like it all works out.
Some upset Twitter users isn't their entire customer base, but as a part of the story I enjoy reading the comments and how the community is responding.
What are the incentives a publisher/developer has for putting anything on a blockchain?
Company B wants nothing to do with Company A's digital assets, and Company A does not want to make transitioning away from their own game easy.
NFTs will never be used in gaming, outside of gimmicks (and all the current attempts talk more about the NFTs instead of any form of actual gameplay.)
Automate the rote software engineering so it's built upon a shared, healthy, secure, etc codebase... Leaving only the harder, more-fun 1% for us to noodle on instead.
However, I think advertising in itself isn't inherently evil. If a chess website served non-tracking, static (no-JS) banner ads about relevant products (maybe, specifically, chess products?) to offset costs, I don't see anything wrong with it. Of course the question is: "what is a relevant product to advertise next to chess?" Would... other board game advertisements be acceptable?
7.8x10^11 tonnes of Carbon to remove from the atmosphere to return to “normal” (Handwavy approximations)
This was 4.16x10^2, in, let’s just say 12 months.
Assuming an absurd 100% increase in volume year over year... they’ll drop the carbon ppm by 1 after... 24 years.
Not meant to doom/gloom, just curious.
Average users appreciate all the extra real estate of their back yard! So much time to do the thing they enjoy, gardening.
Power users hate you, they used those power tools every day! They felt in control! Their backyard garden was meticulously crafted!
Ideally when you take their dozer, back hoe, etc, you put them into an easy to access shed out of sight from most users. Of course it's an engineering/design challenge to 1) create a shed (segment these features without adding complexity), 2) make it easy to use for power users ("wahh, I gotta click through 4 more options!"). They might be able to pull out their auger tractor, but it just isn't as easy as starting the auger tractor right where they left off.
Even with an analogy, it's hard to say: "1% of our users use this feature, tear it out." Even when it imposes > 1% of work on all future features/releases/testing.
Individual packs will always be looked at with doubt, since they’ve probably been weighed and sorted.
Rent is 1/2 as cheap for 2x the sq ft, and property values still currently with in the stratosphere (unlike the Bay Area). No income tax.
Hopefully Austin acts quick and starts building new/upgrading existing buildings to accommodate the growth that's happening.