In software development you reach the 90% mark quite quickly. But the next 5% can easily take weeks.
Addition:
@TARS and his Likers: Just by wishing everything will work our doesn’t help. Somebody actually has to implement it and Flavien is a good example for a good developer who reinvents himself every year or so (which is not a bad thing). Good code can never replace a documentation. This works only for small projects.
@inoX Authentication and access rights isn’t done in a few days, we’ve been working on it for a while now. What I mentionned in my last report was the tip of the iceberg. I won’t be doing a report today, because yesterday I spent most of my time on finalizing access rights, and after a meeting with Keith we realized that we overlooked a few wanted features, so we had to tweak the database design.
The “good code documents itself” remark was tongue in cheek 
Although its true to some degree, and with todays tools creating documentation is easy anyway.
I also didn’t say that I only wish that they succeed, I’m confident that they do because I have played the prototype. Having faith is not the same as wishful thinking…
This is practically a report and sometimes all that is needed
fight on
Edit: Just noticed the grammar 
That’s what I get for posting in the morning pre-coffee again.
No worries, don’t want you bogged down in reports so this brief statement is good and still gives us a sense of forward momentum. The first two were pretty long to be honest - half would have been sufficient, in my opinion. Anyway, keep up the great work Flavien and anytime we hear from you or Keith is a good day. 
Agreed. We only need more detailed updates every once and awhile.
Yeah, even just a ‘Hi guys, all is well. Going to be super busy today. But things are looking good. Later…’ would be so much better than silence. In fact a more personable approach would go a long way. Of course some are all business - but that’s ok too.
Okay, this sounds more realistic 
Also to be honest, if the patchingsystem doesn’t have to patch itself to work at all everything will be fine
Well, you could also say “The code compiles… we can deliver now!”… and its so damn true for so many developers 
The tools only help for API Reference Documentation. And developers need another guy with a shotgun behind them which make sure they don’t document the function getUser() with the text “Returns the User.”
Thanks for Friday’s update Flavien. Sorry to hear about the humidity in your apartment. Wondering which country you live in that is so humid.
I kind of feel bad that people made Flavien feel like he has to write updates every few days. It’s not really like him. That’s probably just my bashful personality speaking out for him, but still.
@Zen Belgium
Deafening silence on the other side isn’t good either. Hard to find the balance, no question.
Love Belgium! Lived with a friend there for a while but so long ago.
Thanks for the update @InovaeFlavien.
Although I do agree with Ovrki1 that no-one should be holding your arm behind your back to write the progress reports, I’m sure it will also double as a motivation factor too as well as serving to quench this community’s thirst for details!
Thanks again.
I agree. That’s silly.
Here’s a balance point:
At the end of each week, write a short paragraph of highlights. In web terms, two or tweets’ worth of text. There’s no need for anything more frequent or larger than that. That’s one paragraph of highlights, from across the team.
High poly Trafalgar should be finished on Monday next week. User authentication about half-done.
When the team reaches a milestone or encounters an exceptional situation that they believe involves some information that backers would find interesting or fun, write a blog article. That might be technical, administrative, business or anything else. Not a paragraph from each team member, but just a description of highlights from the week. If nothing of consequence happened, then just say so. “Still working diligently on the same stuff”
If Flavien finds writing those longer updates to be a cathartic release, then keep at it, but there’s no need to keep a running diary of his life as an INS engineer.
I like daily short updates.
Honestly I’m fine with a weekly or even a monthly update.
Short daily blogs would be fantastic, of course, and I’m not complaining about the current rate. However I wouldn’t be surprised if it became a chore after a while to make a sizable multi-paragraph update every single day. Even if it’s a short blurb, like "Fixed X bug that cause Y problem, have a nice day! 
", that would be stellar. After all, the sole purpose of these updates is just to let us know that you’re A) still alive, and B) still working on the project. Technical details are fun, but it’s not as if by reading the update, the readers are going to somehow fix the problem by osmosis. 
But seriously, IMO, just post something when you feel like you have something worthwhile to post, even if it’s a month apart.
I think that Flavien is an adult, not a poor child affraid by others. He decided (with Keith I imagine) to make daily updates, where everybody was hoping for weekly ones. So it’s a conscious decision.
Why could everybody not simply enjoy the awesome capacity of this team to react… do not abuse their listening and let them decide how to react to our complaints… it’s juste a pov
He did state he was going to start off doing them daily and reduce the rate of them if it was too much.
I’ve liked all the updates so far, on the other hand I wouldn’t have a problem at all if it was only one general summary per week.
But one of the good things that came out of this was Flavien and Keith explaining why the auth stuff was causing such an issue.
If each DEV wrote something once a week, that would be more than enough. So each DEV would only need to write something once a week and we get a variety of updates. 
Well, it is rather trap-door functions. And on an internet, were you cannot trust any party, it is not possible to identify the other end. The NSA makes sure that every data can be read (or attacked) by them. And as they hold the door open, other people can do it too.
(Sorry for that. I just can’t stop hating the NSA for breaking the Internet!)
I’m pretty sure that SQL Management Studio is still a 32bit application. That being the case it will only be able to address 2GB of RAM. It may be running out of addressable memory despite there being plenty available.