| OSDev.org https://forum.osdev.org/ |
|
| About Thunder 0.1 https://forum.osdev.org/viewtopic.php?f=2&t=31908 |
Page 1 of 1 |
| Author: | Thunderbirds747 [ Fri May 12, 2017 1:21 pm ] |
| Post subject: | About Thunder 0.1 |
Hello, I am sorry, but due to the fact that I am not really a programmer, Thunder 0.1 is temporarily on hold. Please respect my opinion. When I will find it interesting to continue coding it further, I will tell you all. Sincerely, Tim from Russia. Thunder (12/05/2017-21/04/2018). |
|
| Author: | dozniak [ Fri May 12, 2017 3:12 pm ] |
| Post subject: | Re: About Thunder 0.1 |
That's a serious announcement and you should follow up with a detailed post-mortem so others could learn from your mistakes. |
|
| Author: | Thunderbirds747 [ Fri May 12, 2017 3:22 pm ] |
| Post subject: | Re: About Thunder 0.1 |
dozniak wrote: That's a serious announcement and you should follow up with a detailed post-mortem so others could learn from your mistakes. Please note that the project isn't actually dead. The code will not be torn up. |
|
| Author: | Schol-R-LEA [ Sat May 13, 2017 11:03 am ] |
| Post subject: | Re: About Thunder 0.1 |
While that term comes from an analogy to an autopsy, it doesn't necessarily imply a total end of something or a defeat of some kind. In this context, the term 'post-mortem' refers to a detailed discussion laying out the results of a project, including both mistakes and good ideas, with a final summation of the project as a whole. It is meant to provide a summary of the lessons learned and sketch out possible paths forward. In project management, it is normal to do this sort of debriefing at the end of any extended project stage, not necessarily just when a project ends - though it is usually called something like a 'process stage summary', 'interim report', or 'milestone debriefing' when it is in the middle rather than the end. Since this is the start of an extended hiatus in an early point in the process, 'post-mortem' is appropriate, as you would be effectively starting over when you come back to it. Speaking of which, this is all the more reason to make sure the code you have now is in a repo on an off-site host, so that you know it will be safe until you come back to it. While backing up code is not the primary function of version control, and should not be uses as a substitute for regular backups, it does have that as a side benefit. |
|
| Author: | matt11235 [ Sat May 13, 2017 1:06 pm ] |
| Post subject: | Re: About Thunder 0.1 |
Thanks for informing us. I was beginning to feel very worried about the status of your project. |
|
| Author: | Thunderbirds747 [ Sat Apr 21, 2018 4:01 pm ] |
| Post subject: | Re: About Thunder 0.1 |
After so long, Thunder has been scrapped and its planned components will be used in Orion. The post mortem concluded that the IDE was very very very unreliable. As of now, I'm using GCC instead of VS2017. Thank you. Tim from Russia |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |
|