 Hi everyone, yesterday we were listing tools management about craft fuel and red foods so today I've only shared about my craft fuel experience and my expectation. Now I'm a developer for the open source software, the famous commercial in Japan which will be explained for the next session. At first why I chose craft fuel for my plugin. Two years ago I received requirements, they want me make an ABI system to connect with the CRM system. First have some issue. The CRM system is so late for the deadline and I don't have time to make the detailed site or detailed specification and I have to release the same desk with the CRM system and the last other systems can reuse my ABI after I relive. As yes at that time in my mind only have red foods but I recognize the project is impossible because with red foods I could not coding without specification and release on the same time with the CRM to late for change any requirement or change or fixing anything else. I'm not sure the other system can using my ABI smoothly so I found the craft fuel and reached us and found the craft fuel and it saved my project. All concept of craft fuel was explained in the yesterday so I just mentioned about the most important, the most impression features of craft fuel is we can ask anything we want and get predictable region in a single crewe. That means I don't need almost specification of the CRM system or the system and I don't care about the release time because we have to release time the same with the CRM system and my problems is over. Yes at that time I think craft fuel is very cool. Yes here is a symbols comparison between craft fuel and red foods. Recently I called the ECQ plug-in for demonstration. Yes but at first we overview the structures of is plug-ins of ECQ right follows MVC model and noting special and on the left in the craft fuel plug-ins a little different with ordinary plug-ins we can see the type worry and mutation. So what is type of craft fuel? It may amazing we can declare structure elements and some action on the type look like the model or the entity. For example in the database I have for the basis table and I also make a four type flag. Oh what's your worries? The name is so of the average meaning and you see I also make a four class for worry. Yes but now I think I will they were chasing about a rough wheel how it's working. Here is sample. Yes this is a symbol query. Yes we can a symbol query. We can ask anything we want and get the reasons as we want also and yes yeah sorry yes a we can see I can make a moon tea query in a one single request and it's sorry and it's also gets predictable reasons but when iteration I also have a problem. Okay what else yes yes another concept I think because we have limit times and I spend a waste a lot of time so we can read in small in the official site. Yes when iteration I have also some problem the first problem is two years ago rough SQL is so new concept for my customer even of me so we're not sure 100% we with a setful and when iteration rough SQL I have to define re-define a lot of type last and some business model or some ordinary or module of plugin where it's difficult when we iteration with rough SQL maybe we have to refactor our renews so now my expectation I imagine if we have a system like this rough SQL is now a chance for the models we can easy connection with rough real by small ball and other system even front end and back end right another problems with rough SQL we have redefine a lot of type I think it should is very bad as if type it can reuse or in Harrison owns deliberations of the module or the database schema at least we can generate codes automatically but anyway I think rough SQL also has problem but I think if we have already iteration with the system it will more popular more easy for faster developments a website thank you