There are a load of methodologies out there, do you follow any or just jump in and do a bit of cod, a bit of UI, a bit of whatever..?
I will, in fact, claim that the difference between a bad programmer and a good one is whether he considers his code or his data structures more important. Bad programmers worry about the code. Good programmers worry about data structures and their relationships. - Linus Torvalds
A big big big big big big big big big big GOOD LUCK ?my cancer permitting
Sorry to read that. Hope to have your pedantics for years to come, not just 1 or 2.my cancer permitting
Sub IncRecordView(SearchText as string) as String
'validate parameters
'open database
'search for specified string
'abort and return error if nothing found
'if more then one record found, abort and return error
'load full found record
'increment the "viewed" field by +1
'save record
'close database
'return null string to indicate no error
End SubSub IncRecordView(SearchText as string) as String
'validate parameters
If SearchText.Length = 0 then
Return "Search Value Null"
end if
'open database
'search for specified string
'abort and return error if nothing found
'if more then one record found, abort and return error
'load full found record
'increment the "viewed" field by +1
'save record
'close database
'return null string to indicate no error
End SubSub IncRecordView(SearchText as string) as String
'TODO validate parameters
'TODO open database
'TODO search for specified string
'TODO abort and return error if nothing found
'TODO if more then one record found, abort and return error
'TODO load full found record
'TODO increment the "viewed" field by +1
'TODO save record
'TODO close database
'TODO return null string to indicate no error
End SubAbsolutely, and that comes out above invention: the latter can really get one into trouble at times. Innovation is beyond most of us. To creativity I would add Imagination.To me Creativity is key !!
database design and data structures.
pay attention to data structures
Documentation, after all these years; my great Nemasis........as I code I often document what I am doing
DITTOHope to have your pedantics for years to come,
That's a great addition: one of the few bits of documentation I do is TODO lines.searching for TODO you will find everything
Then add on 30 to 40% for testing and a around 20% for documentation, installation, and end user training.
I take it the first quote is when in the workplace and the second relates to "new" directions using B4x outside of a workplace? If you were to make the same estimation for a B4x project, do you think it would amount to the same "time-estimate" (even taking into account the noob nature of the experience)? What I am getting at is this : would a person looking at starting to use B4x get a useful sense of the difference in speed of development from such a comparison or not? Because, one of the considerations must be about methodology and the (theme of the thread) software development as a process. There is, of course, @Peter Simpson 's Famous two-part competition with his mate (both of which he won on speed of development process using (then) B4A). The question assumes that the workplace situation is not team based, and that individuals take projects from start to end - which latter seems to be the majority of forum members' format.My estimates are a bit light not having the previous experience,
Thought for a moment there that you were admitting that you work for MacroHard the Infamous. . . .1. I dont normally test my code, but when I do, I do it by relasing it to end users.
Both one and two relate to work. I am building a small team but most are starting from scratch and I am introducing to B4X first offI take it the first quote is when in the workplace and the second relates to "new" directions using B4x outside of a workplace? If you were to make the same estimation for a B4x project, do you think it would amount to the same "time-estimate" (even taking into account the noob nature of the experience)? What I am getting at is this : would a person looking at starting to use B4x get a useful sense of the difference in speed of development from such a comparison or not? Because, one of the considerations must be about methodology and the (theme of the thread) software development as a process. There is, of course, @Peter Simpson 's Famous two-part competition with his mate (both of which he won on speed of development process using (then) B4A). The question assumes that the workplace situation is not team based, and that individuals take projects from start to end - which latter seems to be the majority of forum members' format.
Thought for a moment there that you were admitting that you work for MacroHard the Infamous. . . .or, maybe I just made a lucky guess - you're in their secret NZ lair.....
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?