8
lxmcf
67d

Might start asking monthly or weekly questions just for the hell of it so heres number 1...

If you have a prototyping/code naming convention, what is it and why?

Comments
  • 5
    For me I name everything in generations by names of tree's.

    So currently I'm working on a scripting language and it's currently called Maple Language, I'm working on a game framework and it goes by Maple Engine, etc...

    So everything that is built as a first generation/revision is called Maple, the next revision of anything will go by Birch and so on.

    I did it as a takeaway from google Pixel codenames all being big fish ¯\_(ツ)_/¯
  • 1
    I generally keep the names simple enuf based on the reason why they were defined in the first place. And put appropriate comments if necessary.
  • 0
    @lxmcf I expected it was coming from Pokemon Professors... Oak, Elm, Birch (dont know the newer ones)
  • 0
    @Codex404 no that's just a really really really weird coincidence
  • 1
    I think about what I'm planning to build and base the name on it. For example a prototype of my IoC container was called "gulag" 😅
Your Job Suck?
Get a Better Job
Add Comment