What a ridiculous hyperbole of what it "usually" means.
3,368 karma · joined March 5, 2010
What a ridiculous hyperbole of what it "usually" means.
Finding a good solution for VueJS, which has it's own .vue files was particularly hard. I ended up building on top an existing i18n extract tool and integrating it with the VueJS compiler to extract both HTML and JS translations.
What I'd like to see, that I have not seen anywhere (other than a broken and not currently maintained Webpack module) is a plugin for Babel or Typescript compilers that allows the compiler to compile translations into the final output packages and produce one for each language. I think this is preferable to loading translations at runtime and swapping them in.
And while we're at it, why do we care about the background of entrepreneurs around here? I mean just walk me through the business model and give me your KPIs already.
/s
"So we know you've been out of school for 10 years, but can you send us a copy of your report cards?"
Besides, his statement isn't an argument, and present no facts or information.
> Imbecilic remark. Do you know how many humans would die if we eliminated mosquitos? Any idea?
petters also appears to be correct on what would happen if we had these issues in North America. Your own province kills mosquitos en masse and those ones aren't even carrying deadly disease they are just a nuisance.
https://www.cbc.ca/news/canada/manitoba/deltamethrin-first-u...
That is a very bold assertion I have seen no evidence for. I write very few tests in Ruby or Javascript aimed at validating types.
Agile card boards like this bear little resemblance to Kanban, but the name caught on with the original Kanban software book. It is still a decent book though, and does in fact cover many of the principles of lean kanban. That said, I've rarely met a team using a kanban board that is familiar with the book or the principles of kanban.
https://www.amazon.ca/Kanban-Successful-Evolutionary-Technol...
This sounds completely hand wavy. If the design is in fact modular and built of autonomous components then it should be relatively easy to test and should be tested. Types are no substitute for testing and are completely orthogonal to testing.
> Test code is brittle code
If this is the case then the code being tested is more than likely brittle as well. Test code reflects the system under test more than anything else.
> You need tests because you're using a dynamically typed language
No you simply need tests in any language.
They also admitted that despite their findings they found it very difficult to personally give up on recycling. That's what makes the lie so effective. We want to believe we are helping, that we are doing something effective that makes up for our wastefulness and excess consumption. We aren't.
I'm not sure what you experience with CQRS has been but CQRS is not a solution for scale it is a solution for long-term maintenance costs of a growing codebase by enforcing the decoupling of services.
The original Airpods are amazing only because they work well at least 90% of the time, unlike just about every bluetooth headphone out there.
I have found the Beats Pro's generally as reliable and convenient but occasionally they flake out completely and are unable to pair properly with anything. Hours later they will work again. I've seen the a few threads online complaining about this behaviour. It is uncommon but a shockingly bad problem considering the cost.
Given what Apple is asking for, for these products they need to be pretty much perfect. I'll be interested to see how users review these.
Is there any more to discuss on the topic of Bitcoin being outrageously wasteful? Or is this pretty much the final word?
Is Bitcoin figuratively, and almost literally, a tire fire?
I mean I have an iPhone 8 and what I see are:
- An edge-to-edge screen
- Longer battery life
- Faster processors
- Improved cameras (don't care much myself but it is still improved)
- FaceID
- Updated Wifi and LTE technologies (not sure how much hype that is)
- More durable (apparently) and more water resistant (at least compared to my 8)
- Multiple wireless headphone support (not sure I need this either but it is still a feature others will use)
I don't need to upgrade for any of these things, which is probably a good thing in terms of e-waste, but it is still definitely a clear upgrade from my current phone.
> As soon as we finished the Rails 5.2 upgrade last year, we started upgrading our application to Rails 6.0.
> Instead of waiting for the final release, we’d upgrade every week by pulling in the latest changes from Rails master and run all of our tests against that new version. This allowed us to find regressions quickly and early—often finding regressions in Rails master just hours after they were introduced. Upgrading weekly made it easy to find where these regressions were introduced since we were bisecting Rails with only a week’s worth of commits instead of more than a year of commits. Once our build for Rails 6.0 was green, we’d merge the pull request to master, and all new code that went into GitHub would need to pass in Rails 5.2 and the newest master build of Rails.
Realistically how many hours of work went into this upgrade process then?
Edit: I should add I think it really is wonderful that Github contributed so much to the new release and was so involved. I'm just not sure that it is realistic or even ideal for the average Rails consumer to upgrade in this manner.