3 ms·
> My current Q "algo" or whatever we call it (it's a ensemble of multiple "algos") actually has almost every layer you describe (although not using the same met
by spitfire 10y ago
> My current Q "algo" or whatever we call it (it's a ensemble of multiple "algos") actually has almost every layer you describe (although not using the same methods you describe) and some extra layers you don't describe so it's quite strange for me to read how hard or impossible creating something like what I already have in place is.
HN won't let me respond directly to this comment. This approach works fine in the small, but as you grow, do research and try new things out it becomes an unmanageable mess.
Same reason we have modularity in software development - to separate differing concerns.
- mikkom 10y ago> This approach works fine in the small, but as you grow, do research and try new things out it becomes an unmanageable mess I have quite a long history in creating complex systems so I think my code is quite clean and easy to work with (I have already removed and added methods multiple times). however there are the things that really suck: 1) I'm not able to package the framework to a library 2) copy-paste because of 1. 3) version management hell because of 1.