4 ms·
True. Well in this case an MVP would be considered something that already processes transactions. I would think that is the minimal functionality a currency exc
by easy_rider 13y ago
True. Well in this case an MVP would be considered something that already processes transactions. I would think that is the minimal functionality a currency exchange would have to have. So for all reasons stated above (minus the security problems, which were not stated in above post), this could work for an MVP.
(Although again I would expect the quality of the code to be initially way better in quality in regards to security )
When I start something from scratch, unlike a framework, I usually blast away in a single file, this just makes it easier for me in the prototyping phase. I will write a lot of "crappy" code, will not separate concerns but keep them close to the source for now and refactor it later.
It helps me see some bigger pictures in my design, and allows for quick revision.
- dev360 13y agoWhat language do you program in?
- easy_rider 13y agoPHP, Ruby, JS.
- easy_rider 13y agoThe example given is PHP (and also my forte), and do have to elaborate again. This is not my style if I start an entire project from scratch. I would probably pick Symfony2 if the need would require. But I sometimes get these tasks where a client is hosted on shared host, my only option is PHP. I don't even get a shell to run console commands. I might not even have the budget to setup GIt/deployment strategies and have to work on FTP.... This means I will probably cowboy everything in to one file, and test it on there, instead of messing around with folders and files in a GUI. I've had occasions where i'd just want to open something something borked and gone were some important other production files.. Luckily in these cases you will often find improvised version control systems in place (e.g. /site_old site_old123 /site_new2 /site :D)