There is something about yourself that you don’t know. Something that you will deny even exists, until it’s too late to do anything about it. It’s the only reason you get up in the morning. The only reason you suffer the shitty puss, the blood, the sweat and the tears. This is because you want people to know how good, attractive, generous, funny, wild and clever you really are. Fear or revere me, but please, think I’m special. We share an addiction. We’re approval junkies. We’re all in it for the slap on the back and the gold watch. The hip-hip-hoo-fuckin’ rah. Look at the clever boy with the badge, polishing his trophy. Shine on you crazy diamond, because we’re just monkeys wrapped in suits, begging for the approval of others. /Jake Green/
Let’s try to segregate some of these concerns into specific architecture domains:
- Business Architecture: How does a customer apply for a loan online?
- Data Architecture: What information is needed to enable loan risk assessment and processing? How to manage customer info with maximum security, integrity and optimal cost, performance, reliability, consistency?
- Application Architecture: What UX, process management, and functional system components/services are needed to enable customer loan application via mobile and web devices?
- Integration Architecture: How will the distributed application component and services talk to each other?
- Security Architecture: How to properly verify and authenticate customer identity? How to ensure that customer data is secure in a distributed environment? How to prevent unauthorized data access and data theft over the wire?
- Technology Architecture: How to configure supporting infrastructure for high availability and recoverability in case of system or facility failure?
- DevOps Architecture: How to enable rapid product delivery and continuous maintenance?
“To be more specific—at this moment there is a lack of research from the sell side, meaning that current major crypto exchanges are swarming with inexperienced crypto investors who are too easily influenced into making rash decisions which in fact acts as catalyst to these sudden price movements. So, in conclusion, in most cases the price of tokens (USD equivalent) should not be considered an indicative sign of success or failure a project.”
Amen to that. A whole slew of noobs following hype trains (c)
Professor William G. Ouchi is known for his book “Theory Z: How American Business Can Meet the Japanese Challenge”. It introducing the principles of Japanese management to Western business audiences and stayed at US bestseller list for 15 weeks.
Ouchi also studied mechanisms of controlling work in large organisations. He focused on two simple questions:
What are the mechanisms through which an organisation can be managed so that it moves towards its objectives?
How can the design of these mechanisms be improved, and what are the limits of each basic design?
Solidity Documentation (solidity.readthedocs.io)
Solidity Cheat Sheet And Best Practices (https://github.com/manojpramesh/solidity-cheatsheet)
Building a production-ready Ethereum DApp from idea to final product – Part 1 (https://blog.amr-gawish.com/building-a-production-ready-ethereum-dapp-from-idea-to-final-product-first-section-the-3b9975a226c)
CryptoZombies (interactive. +++++) (cryptozombies.io)
EthList: The Crowdsourced Ethereum Reading List (https://github.com/Scanate/EthList)
Coursetro (beginner) (https://coursetro.com/courses/20/Developing-Ethereum-Smart-Contracts-for-Beginners)
CRUD Part 1 (+++++) (https://medium.com/@robhitchens/solidity-crud-part-1-824ffa69509a)
CRUD Part 2 (+++++) (https://medium.com/@robhitchens/solidity-crud-part-2-ed8d8b4f74ec)
Learning Solidity (beginner → advanced. +++++) (https://www.youtube.com/channel/UCaWes1eWQ9TbzA695gl_PtA/videos)
One-To-Many CRUD (+++++) (https://medium.com/@robhitchens/enforcing-referential-integrity-in-ethereum-smart-contracts-a9ab1427ff42)
The Patient Smart Contract – Part 1 (beginner) (https://medium.com/@tejnikumbh/solidity-tutorial-1-the-skeleton-c311f1ea96b7)
Can you provide examples of experiments carried out in respect of each of your registered core activities? You will need to include the hypothesis the experiment was employed to test, the results and the conclusions reached.
Do you have documents to demonstrate this systematic progression from hypothesis to experiment, observation and analysis, leading to conclusions for each registered core activity.
In order to establish that your experiments for the registered core activity employed the scientific method, please answer the following questions:
Which of the following scientific principles was your project based on (please tick all that apply):
– Scientific Principles
– Engineering Principles
– ‘Know How’
Can you explain how you established that the outcome of each experiment could not be determined in advance? (you will need to comment on the knowledge gap that existed when the registered core activity was undertaken.)
Do you have documents to demonstrate that a knowledge gap existed at the commencement of the project?
Can you explain how the new knowledge is more than a simple progression from what is already known or how it is more than applying existing knowledge in a different context or location?
If software development was claimed as a core activity, can you describe the hypothesis, experimentation, observation, evaluation and conclusions?
Can you provide documentation which support your core and supporting activities? For example, if this involved the development of unique algorithms, the records should show how the company researched and established that no existing algorithms offered a suitable solution and the reasons why.