Came hear to say exactly this. I’m no expert, but this sounds like the right answer
Came hear to say exactly this. I’m no expert, but this sounds like the right answer
I just realized something…
At some point, Valve will release a Steam Deck 2 - It will be slimmer and even better than the first. Maybe in a couple of years I am guessing
Then that will be it because other companies will be releasing cheaper devices with their Steam OS. Steam simply cannot compete with them on price, and the feature set (other than faster chips) will mostly be locked in.
In short, there will be now Steam Deck 3 - Gaben strikes again
He obviously gained a lot of weight by the time he ended up playing the nightclub boss in John Wick 4
The tests help you discover what needs to be written, too. Honestly, I can’t imagine starting to write code unless I have at least a rough concept of what to write.
Maybe I’m being judgemental (I don’t mean to be) but what I am trying to say is that, in my experience, writing tests as you code has usually lead to the best outcomes and often the fastest delivery times.
This is why you write the test before the code. You write the test to make sure something fails, then you write the code to make it pass. Then you repeat this until all your behaviors are captured in code. It’s called TDD
But, full marks for writing tests in the first place
And massively increased again in the last five years…