I bought this 2-3 years ago https://cplay2air.com and it has always worked wonderfully. It takes around 5 seconds to connect, which is fine for me since the entertaining system of my car it’s slow to startup anyway (totalling ~10 seconds from turning the key to carplay)
This is a common misconception. I practice TDD at work and side-projects and find it very productive. TDD is best done with end-to-end tests (or automated integration tests, whatever you wanna call it). You write an end-to-end test (I give input A to the entire system, expect output B), first the test fails (because it's unimplemented) and then you implement and it passes.
It works because then your tests become the spec of the system as well, but if you only write unittests there is no spec of the system, only modules of your code. Which is not useful because if you refactor your code and change this module you need to rewrite the test. Whereas in TDD your tests should never be rewritten unless spec changes (new features added, new realization of bugs etc). This way "refactor == change code + make sure tests still pass".
You're of course free to write unittests as well, when you see fit, and there is no need to target a religious X% coverage rate at all. I think coverage targets are cargo-culted, unnecessary, time-consuming and religious. The crucial thing is, while you're writing new code (i.e. implementing a new feature or solving a bug) you need to write an automated test that says "if I do X I expect Y", see it fail, then see it pass, such that "if I do X I expect Y" is a generic claim about the system that will not change in the future unless the expectation from the system changes.
In other words, the example in this comment chain: "run a game, see 'opcode X doesn't exist', implement X, rinse repeat" is actually how TDD is supposed to work.
I'll repeat a comment I saw here on HN some time ago about the productivity issue: if an asteroid were to hit the earth in one month, and there were a team of NASA engineers working to stop it, would you rather say them to work 4 days per week, or 6-7?
Working in a crisis (crunch, etc) mode 100% of the time is not healthy or sustainable.
People can stretch to meet a deadline, or avert a crisis—but they need time to recover afterwards. The extra effort and productivity comes at a cost that needs to be repaid for their health and wellbeing.
The purpose of the 4 day week trials around the world has been to evaluate if there’s a measurable drop in productivity, and it seems overwhelmingly there hasn’t been.
Stretch the timelines out a bit. Say the asteroid is two years off (a fairly typical startup runway). I would much rather know the planning, decisions and execution of the one thing that could save my life were done by well rested and level headed individuals, not stressed out sleep deprived people more prone to missing details and making mistakes.
I make web apps for a living. Why would anyone use a human-race saving, rocket-science complexity, literally life and death situation analogy to determine my working conditions?
I mean, if those scientists are successful they'll be getting a congressional medal of honor, millions of dollars in speaking fees, and probably given their choice of job in space science afterwards. Am I getting those things for pushing some HTML?
I'd like to see them round up as many engineers as possible and rota them on a healthy 24/7 schedule. There comes a point where you just can't be productive for 7 days a week. If 4 days is proven to be productive, then put them on a 4 day rota. Otherwise, the status quo of 5 days.
Some of the greatest ideas are conceived when away from work with just time to think on your own. We always need breaks and rest.
Most people have working lives spanning decades, so maximizing the output of any one month is generally counterproductive.
However, if you have a well-rested, happy and productive team that has adequate time for leisure and recreation, you can turn up the pace for those exceptional months that are really make or break.
But if you try to get people to run at that pace continuously, you'll get a lot of resignations and a few heart attacks at 50.
4 days/week, and I'd want them to be getting good catered food and the best sleeping quarters money can buy. Not working when you're tired and fucking up makes a lot more difference than squeezing out a little more.
Mhmm, that's an anti-piracy PR blurb from an "anti-piracy" service selling site. Not sure it is the most unbiased source... I think it has been demonstrated elsewhere that 1 pirated download does not equate to 1 lost sale.
Where I live (Mexico) I know so many people that have pirated Adobe, Microsoft apps and plenty of games, who there is NO WAY they would have bought the software if they hadn't been able to pirate it.
The concept of a system-wide hierarchical key-value store is actually very useful is some environments.
I had to develop one some time ago [1] for an embedded system, since is super useful to have a single point of truth/configuration/state, if every application agrees on using it (which is the case in such systems were every application is known in advance and developed in house)
I live in Lombardy, and I can assure you that the conditions to meet in order to get tested are the same. Me and my three flatmates had 37-39 °C for some days, including a very bad cough. We called the emergency number, and they said that they could test us only in case of prolonged temperature and/or respiratory problems. This happened like 2-3 weeks ago, and considering the current state of the national health service, I don't think requirements became lesse strict
