avighnay
Joined 13 years ago
Joined 13 years ago
This is also why most 'vibe' coding projects fail as the model is always going to give this optimum ('lazy') result by default.
I have fun goading Gemini to break this ceiling when I work on my AI project - https://github.com/gingerhome/gingee
I used Gemini AI studio for this and I was very pleased at the result and decided to open source it. I have completely captured and documented the development transcript. Personally it has give me considerable productivity boost. My only irritation was the unnecessarily over politeness that AI adopts in My take is
AI yields good ROI when you know exactly what you want at the end of the process and when you want to compare and contrast decision choices during the process.
I have used it for all artifacts of the project: - Core code base - Test cases - Build scripts - Documentation - Sample apps - Utilities
Transcript - https://gingerhome.github.io/gingee-docs/docs/ai-transcript/... Project - https://github.com/gingerhome/gingee
Since AI code is inherently bound to face a critical review, we have kept the goal of security at the top. We have taken the following steps for it.
- 1. Code execution is sandboxed
- 2. Access to all built in modules of NodeJS is prevented, with option to whitelist using the server configuration
- 3. Platform APIs which access system (within the sandbox) also need to be whitelisted with explicit permission grants
Yes, we would like to make it ever more secure, with the help of the community and feedback from our customers. Like with any code human or ai there is bound to be bugs, the issue list of even the most popular, major projects out there is a testament to it. We intend to ever make it better for ourselves and for our customers.
The freedom to choose, not the entitlement to demand was the original promise of OSS
https://www.zoho.com/blog/general/the-real-cost-of-acquisiti...
Even though such software are the core of an enterprise today. Many technologies that they pioneered did not gain mainstream adoption after the entry of Internet software companies such as Google/Facebook/Amazon.
Take for example what is now a buzz "Low code No code", it is a poor ghost of Model Driven Architecture (MDA) - https://www.omg.org/mda/ . Enterprise software always wants to push software to the realm of standard components and modules. That cycle was broken around 2010 due distraction from the smart phone wave.
Other techs of that era - ESB, WSDL, SOAP, SOA, UDDI, BPM, Business Rules, EDI, Data Mapping (all are almost but forgotten). Many of them are getting re-bottled e.g. Microservices
Enterprise software has not had any major breakthroughs since. Glamour of new tech from Internet giants who invent it for their specific purpose is pushed more often than not, on to enterprise systems by other software vendors/consultants pouting it as the new and best. This has made standardization almost impossible and hence kept software always in the "handicraft" mode.
https://www.britannica.com/biography/Suryavarman-II
There are tamil inscriptions in Angor Wat and the architecture is highly influenced by Chola/Pandya architecture.
https://www.quora.com/How-did-Tamil-Kingdoms-influence-Angko...
Some examples of what the Cholas and Pandyas accomplished which stands to today are
Tanjore Temple (Cholas) https://www.youtube.com/watch?v=XX9-__GWHnA (Edit: Unfortunately, this video also has a lot of old western cliched ideas of Hinduism, hope I had a better documentary to share...) (for scale, this can fit 200 Taj Mahals)
Madurai Meenakshi (Pandyas) https://www.youtube.com/watch?v=iQjI3DPt9Tk
You can see that the architectural pattern of 4 directional gateways with a central temple complex is basically the same as Angor Wat.
My go to test for my QA team is to have them add a zero internet test case. Test your product in localhost with the network switched off.
However, personally I have got very good results by taking the approach of using the AI with continuous interaction and also allowing implementation only after a good amount of time deliberating on design/architecture. I almost always append 'do not implement before we discuss and finalize the design' or 'clarify your assumptions, doubts or queries before implementation'.
When I asked Gemini to give a name for such an interaction it suggested 'Dialog Driven Development' also contrasted it against 'vide coding'. Transcript summary and AI disclaimer written by Gemini below
https://gingerhome.github.io/gingee-docs/docs/ai-disclaimer.... https://gingerhome.github.io/gingee-docs/docs/ai-transcript/...