> If you're starting with TDD and unit tests, then you're doing it wrong
Source?
Please. This is just plain wrong. Integration tests also belong to TDD.
Unit tests are very focused, individual, component level tests. Suppose, I want to test my mortgage calculator logic, without bothering about caching, data storage, network IO etc. Then, unit tests are the way to go. But, if I want to test the functionality, just like an end user then Integration Tests are the way to go.
You might also use Integration tests to get your stories approved.
One might say Integration tests belong to BDD. I'll say that is just a lower level categorization. At the top, it's just TDD.
In a world of no tests, a handful of high level tests on "critical path" functionality can make a huge difference. They can also demonstrate visible wins to unconvinced stakeholders.
I don't know the OP's world, but I can vouch for starting with high level tests being a good strategy in some cases.
Generally, I agree with this statement, but my experience shows me that there's a very important exception here: if a code implements any kind of parser or compiler, unit tests are a must for that part.
Yes for me. Of course I don't know every single character by heart but with a little bit practice and the help of a dictionary you can read a lot. You can even download some seal script fonts and make all the Chinese websites shown in seal script.
With some training, people can read seal script inscriptions because the structure is already fairly close to regular script which is what people use today.
The radicals are written in slightly different styles from today. It actually makes sense. Seal script is a very artistic form of calligraphy, so people use it for their seals hence the name.
An example of the "drum" character:
http://www.guoxuedashi.com/zixing/yanbian/11208mb/
The horizontal arrow is the time line, starting from oracle bone script. The 4th one of the first row is seal script and the last regular script.
The idea depicted here is hitting a decorated drum on a rack with a drum stick holding in the hand.
If you look at the picture on the upper right, you can make out "tian xia" and "wang" -- all under heaven (i.e. the world) and king (the character for emperor isn't invented yet)
Good catch. But that just adds more to my point: modern Chinese can understand seal script to a large extend because seal script is the ancestor of the modern (non-simplified) Chinese. My guess is that neither you nor I are "Indiana Jones".
He has done great work and so would not say it is not very useful since that is subjective.
Would you mind giving BookFusion a try and providing your frank feedback? :) We support FB2 and allow you to read your eBooks across iOS, Android and Web
EPUB is basically just HTML in a zipfile, with all the ugly warts that HTML comes with. (Attempts to enforce "pixel-perfect" design, broken accessibility, ugly fonts forced on you, etc.)
EPUB is good for publishers, I guess, but a crappy ebook format.
FB2 is a different beast, it's an extremely minimal XML dialect that encodes only semantic information and nothing else. (Basically, tags for chapters/sections/headings/verse and that's about it. The extent of the formatting allowed is 'em' and 'b' tags.)
You can create your own clean minimalist epubs. None of that cruft is mandated, you can simply choose to not use any of it. Don't want to enforce a font? Don't specify one. Don't want a stylesheet? Don't put one in.
Presumably the problem here is restraint? I contribute to Standard Ebooks that uses EPUB3 as a core format. That’s based on HTML5.2 but our books have clean code, minimal styling and as good accessibility as we can make (we’ve had a couple of reviews of the core accessibility functionality and fixed any problems that came up).
Adtech loses income, not money. There is a vast difference.
Additionally you can have rollbacks - strategy applied by many banks when things break.
Funny enough, safe reverts and rollbacks require specialized up front design, it does not happen on its own. Safe automatic updates with no state loss? Same.
> Adtech loses income, not money. There is a vast difference.
Placing bids is (potentially) spending money. A bug in your adtech platform can absolutely bankrupt you in the very direct way of spending more money than you have.
What bullshit. The whatsisname congressman is 100% correct, and the article author is spewing a load of autistic idiocy.
Of course "tech" isn’t the issue, nobody cares about the SERP coefficients. The values and processes behind the scenes at Google is the issue, and they are absolutely evil and partisan.
i don’t know a lot of database that you can share between any number of parties with write priviledges and yet be sure none of them can destroy, alter, falsify data or even make them unavailable , and which you don’t even need to host yourself.
There are some very peculiar properties of a dlt, that makes them special.
You have to start with integration tests, then go down the stack if you have time and resources.