News for hackers. Stuff that matters.
Re:Lessons learned from creating a real-time collaborative r... by fabricexpert on Tuesday October 16, 2018 @01:43PM (#18231440)
> The number of tests: 12500

> Code coverage: 100%

> Development team: 25+

> Estimated number of man-days: 42 man-years (until September 2018), including time spent on writing tools to support the project like mgit and Umberto (the documentation generator used to build the project documentation)

Software is expensive

Re:Lessons learned from creating a real-time collaborative r... by pault on Tuesday October 16, 2018 @06:40PM (#18233923)
I showed the demo to a passing PM and asked him how long he would expect a team of five developers to spend on it and he said "a couple of weeks... no wait, maybe two months." :)
Re:Lessons learned from creating a real-time collaborative r... by _mrmnmly on Tuesday October 16, 2018 @05:14PM (#18233332)
show this stats next time the junior dev will say that she/he will develop own WYSIWYG editor in like 1-2 weeks for the project needs ;)
Re:Lessons learned from creating a real-time collaborative r... by fabricexpert on Tuesday October 16, 2018 @05:42PM (#18233558)
`import editor from CKEditor`

or something like that ;-)

Re:Lessons learned from creating a real-time collaborative r... by cco on Wednesday October 17, 2018 @12:52AM (#18236213)
That's an interesting opinion that differs from my item. My impression to all software costs, not just this one, is, "Wow, software is just so damn cheap!"

Compared to any physical project or product software is by comparison so cheap!