Starting with some news about apple and started skimming this: https://appleinsider.com/articles/19/03/27/alongside-efforts-to-drive-coding-competency-apple-releases-swift-5-with-abi-compatibility-new-features
It moved me to check what is happen at https://swift.org
Started checking their blog and while going through the posts, this was
// Interesting to see these examples and use them, can be used to make students understand REST APIs client.
Then gone to see the author twitter account: https://twitter.com/aciidb0mb3r/
His twitter ID, is encountered earlier, but don't remember the context.
Got to his website: http://ankit.im
Code of conduct for open-source-projects:
Read and explain what you have understood, assignment:
Then found ninja article in AOSA BOOK for The Performance of Open Source Applications
Exploring other names which I don't know.
While reading this https://www.aosabook.org/en/posa/zotonic.html
While see this section:
Requirements for a Modern Web Framework
Felt like writing something so started writing...
Morning I was listening to https://www.youtube.com/watch?v=JjV7r48zBKo
I liked is cognitive-environment word. so started writing like this...
Requirements for a Modern Developer Congnitive Environment
Typically deals with these requests:
First is expert in building in a specific environment. Second is generalist who can understand end to end, and deal with uncertain/new things and solve the problems. Third is a potential to become inclusive leader and communicate well.
The constrains and desired activities.
Language independent
Patterns and models
Analyse and synthesis Open-Source-Content
Dig deeper into a domain and be capable of building
I don't know, let's collaborate
Understanding the internal workings of the software they encounter using tools
Non-Linear activity model
.....
You must be comfortable to say
I don't know and let us collaberate.
This was picked from recently watching https://www.youtube.com/watch?v=kY0RdN8BMC8
I felt the spelling collaberate was wrong, so wanted to check the correct spelling...
opened spotlight search at typed, was showing this file...
oldDocuments/PonderThis/JSApp/node-v8.4.0-darwin-x64/lib/node_modules/npm/node_modules/mississippi/node_modules/stream-each/collaborators.md
I happen to open the second link https://github.com/mafintosh
from here the exploration continues....
to understand callbacks and DB
useful to experiment with torrents
// will enable the underlying understanding of how torrents work.
// intersting to expose them to FUSE and file system concepts
// can play youtube as well like quicktime on macOS
// to understand DNS, can play with these
// can make to implement it to see how you can create your own, ways of maintaining a small DNS inside the private network
// you can have your own git repo to push to deploy.
// simple servers in C
// useful to explore the JSON contents from the server.
// to see in the browser
// this also can be viewed in Chrome browser
// to learn different encoding
// This is the best part, we can include in the cognitive environment, for people to see in real the possibilities that lie in them dormantly.
A note from the above blog post:
So to sum up my experience
Find a project that motivates you.
Writing bad code is better than not writing any code. Learn from your mistakes.
Read other people's code.
Don't listen too much to other devs / books / blogs. Do things your own way. Again, learn from your mistakes.
Don't be afraid to reinvent the wheel. You'll learn a lot doing so.
Always publish your code to Github. It doesn't matter if you think it's bad. It gives you a notion of finishing things