ShareSmart

sharesmart

Hey, HackerNoon fam! Back in May 2024, we kicked off the #bitcoin writing contest, calling on Bitcoin maximalists, developers, thought leaders, and Web3 enthusiasts to explore the Bitcoin ecosystem—its origins, financial impact, core ethos, development stacks, Rootstock’s role in extending its capabilities and other related topics. The response has been incredible. Across the first two rounds, over 150 #bitcoin stories have been published, drawing more than 300,000 pageviews and delivering over eight days’ worth of insightful reading time! So far, 10 winners have been awarded cash prizes for their standout entries. Highlights include @nikku’s first-place article in round one, How to Build a DApp on Rootstock with Next.js, TypeScript, and Solidity, and @tomaszs’ second-round winning piece on interacting with Rootstock from a frontend developer’s perspective. Check out the full winners' list for both rounds below:

Results announcement for round 1
Results announcement for round 2 And the best part? We’re not done yet! With thousands more in cash prizes still to be won, the final round of the #bitcoin writing contest is open until November 30, 2024. If you’re 18 or older and have the skills to build on Bitcoin, a strong grasp of Rootstock’s unique features, or niche insights into the Bitcoin ecosystem, join us and compete for cash prizes in any of the following categories: Dev Stack & Tooling for Building on Bitcoin: Discuss must-know developer tools for building on Bitcoin, including SDKs, APIs, smart contract frameworks, and more. Enter Now with this writing template Tutorials for Building on Rootstock: Share step-by-step tutorials on building applications, deploying smart contracts, or implementing specific features on Rootstock. Enter Now with this writing template Other Bitcoin Topics: Explore themes like Runes, Satoshi’s writings, ordinals, Layer 2 solutions, sidechains, Bitcoin’s influence on finance, price prediction, inflation impacts, and more. Prize Breakdown for the Final Round of the #bitcoin Writing Contest Position

Prize



1st Place

$2000



2nd Place

$1500



3rd Place

$1000



Bonus Prizes

$650 a piece for two thought leadership entries The #bitcoin Writing Contest Rules & Guidelines Must be 18+ to enter.​
Story content can be any original story on #bitcoin.​
Must create a HackerNoon account, as winners will be contacted via email.​ Who Can Enter the Contest?​ Anyone over the age of 18. There are no location restrictions. Can I Write Under a Pen Name? Yes!You can either use your real name, or a pseudonym when setting up your HackerNoon profile. How are the winners selected? After the contest ends, we’ll review submitted entries and shortlist the stories that receive the most organic views.
The HackerNoon team votes on the shortlisted stories.
Top three stories are selected as winners.
Two additional stories receive bonus prizes. If I win a prize in one round, can I still submit another entry in a different round? Absolutely! Feel free to enter each round of the competition. Ready to give it a shot? Start a draft now, or enter the contest using any of these templates:

Dev Stack & Tooling for Building on Bitcoin
Deploying Smart Contracts on Rootstock
Building DApps on Rootstock Good luck! Hey, HackerNoon fam! Back in May 2024, we kicked off the #bitcoin writing contest , calling on Bitcoin maximalists, developers, thought leaders, and Web3 enthusiasts to explore the Bitcoin ecosystem—its origins, financial impact, core ethos, development stacks, Rootstock’s role in extending its capabilities and other related topics. #bitcoin writing contest #bitcoin writing contest The response has been incredible. Across the first two rounds, over 150 #bitcoin stories have been published, drawing more than 300,000 pageviews and delivering over eight days’ worth of insightful reading time ! So far, 10 winners have been awarded cash prizes for their standout entries. Highlights include @nikku ’s first-place article in round one, How to Build a DApp on Rootstock with Next.js, TypeScript, and Solidity, and @tomaszs’ second-round winning piece on interacting with Rootstock from a frontend developer’s perspective . 150 #bitcoin stories #bitcoin more than 300,000 pageviews eight days’ worth of insightful reading time @nikku @nikku How to Build a DApp on Rootstock with Next.js, TypeScript, and Solidity , How to Build a DApp on Rootstock with Next.js, TypeScript, and Solidity , @tomaszs ’ @tomaszs interacting with Rootstock from a frontend developer’s perspective Rootstock from a frontend developer’s perspective Check out the full winners' list for both rounds below: Results announcement for round 1
Results announcement for round 2 Check out the full winners' list for both rounds below: Check out the full winners' list for both rounds below: Results announcement for round 1 Results announcement for round 2 Results announcement for round 1 Results announcement for round 1 Results announcement for round 2 Results announcement for round 2 And the best part? We’re not done yet! And the best part? We’re not done yet! With thousands more in cash prizes still to be won, the final round of the #bitcoin writing contest is open until November 30, 2024. the final round of the #bitcoin writing contest is open until November 30, 2024. If you’re 18 or older and have the skills to build on Bitcoin, a strong grasp of Rootstock’s unique features, or niche insights into the Bitcoin ecosystem, join us and compete for cash prizes in any of the following categories: If you’re 18 or older and have the skills to build on Bitcoin, a strong grasp of Rootstock’s unique features, or niche insights into the Bitcoin ecosystem, join us and compete for cash prizes in any of the following categories: Dev Stack & Tooling for Building on Bitcoin: Discuss must-know developer tools for building on Bitcoin, including SDKs, APIs, smart contract frameworks, and more. Dev Stack & Tooling for Building on Bitcoin : Discuss must-know developer tools for building on Bitcoin, including SDKs, APIs, smart contract frameworks, and more. Dev Stack & Tooling for Building on Bitcoin Enter Now with this writing template Enter Now with this writing template Enter Now with this writing template Enter Now with this writing template Tutorials for Building on Rootstock: Share step-by-step tutorials on building applications, deploying smart contracts, or implementing specific features on Rootstock. Tutorials for Building on Rootstock : Share step-by-step tutorials on building applications, deploying smart contracts, or implementing specific features on Rootstock. Tutorials for Building on Rootstock Enter Now with this writing template Enter Now with this writing template Enter Now with this writing template Enter Now with this writing template Other Bitcoin Topics: Explore themes like Runes, Satoshi’s writings, ordinals, Layer 2 solutions, sidechains, Bitcoin’s influence on finance, price prediction, inflation impacts, and more. Other Bitcoin Topics : Explore themes like Runes, Satoshi’s writings, ordinals, Layer 2 solutions, sidechains, Bitcoin’s influence on finance, price prediction, inflation impacts, and more. Other Bitcoin Topics Prize Breakdown for the Final Round of the #bitcoin Writing Contest Position

Prize



1st Place

$2000



2nd Place

$1500



3rd Place

$1000



Bonus Prizes

$650 a piece for two thought leadership entries Position

Prize



1st Place

$2000



2nd Place

$1500



3rd Place

$1000



Bonus Prizes

$650 a piece for two thought leadership entries Position

Prize 1st Place

$2000 2nd Place

$1500 3rd Place

$1000 Bonus Prizes

$650 a piece for two thought leadership entries Position Prize Position Position Prize Prize 1st Place $2000 1st Place 1st Place 1st Place $2000 $2000 $2000 2nd Place $1500 2nd Place 2nd Place 2nd Place $1500 $1500 $1500 3rd Place $1000 3rd Place 3rd Place 3rd Place $1000 $1000 $1000 Bonus Prizes $650 a piece for two thought leadership entries Bonus Prizes Bonus Prizes Bonus Prizes $650 a piece for two thought leadership entries $650 a piece for two thought leadership entries $650 a piece for two thought leadership entries The #bitcoin Writing Contest Rules & Guidelines Must be 18+ to enter.​ Story content can be any original story on #bitcoin.​ Must create a HackerNoon account, as winners will be contacted via email.​ Must be 18+ to enter.​ Story content can be any original story on #bitcoin .​ #bitcoin Must create a HackerNoon account, as winners will be contacted via email.​ Who Can Enter the Contest?​ Anyone over the age of 18. There are no location restrictions. Can I Write Under a Pen Name? Yes! You can either use your real name, or a pseudonym when setting up your HackerNoon profile. How are the winners selected? After the contest ends, we’ll review submitted entries and shortlist the stories that receive the most organic views. The HackerNoon team votes on the shortlisted stories. Top three stories are selected as winners. Two additional stories receive bonus prizes. After the contest ends, we’ll review submitted entries and shortlist the stories that receive the most organic views. The HackerNoon team votes on the shortlisted stories. Top three stories are selected as winners. Two additional stories receive bonus prizes. If I win a prize in one round, can I still submit another entry in a different round? Absolutely! Feel free to enter each round of the competition. Ready to give it a shot? Ready to give it a shot? Start a draft now, or enter the contest using any of these templates: Dev Stack & Tooling for Building on Bitcoin
Deploying Smart Contracts on Rootstock
Building DApps on Rootstock Start a draft now , or enter the contest using any of these templates: Start a draft now Start a draft now Start a draft now Dev Stack & Tooling for Building on Bitcoin Deploying Smart Contracts on Rootstock Building DApps on Rootstock Dev Stack & Tooling for Building on Bitcoin Dev Stack & Tooling for Building on Bitcoin Dev Stack & Tooling for Building on Bitcoin Deploying Smart Contracts on Rootstock Deploying Smart Contracts on Rootstock Deploying Smart Contracts on Rootstock Building DApps on Rootstock Building DApps on Rootstock Building DApps on Rootstock Good luck! Good luck!

Last Call: One Month Left to Win Your Share of $17,500 in the #bitcoin Writing Contest

Smart contract development is no different than other types of software development. Code is written to perform a certain task, and there are tools that help make this process easier. The Ethereum ecosystem contains many mature tools to help build Web3 projects, but what about a newer ecosystem, such as Flow? If you’ve been following along with this series so far, you’ll know that the Flow blockchain is optimized for digital asset creation and management. Additionally, its smart contract language, Cadence, improves upon other languages’ pitfalls through its resource-based approach and a strong, static type system. In this article, we’ll take a look at the essential tools smart contract developers can use to make building on Flow easier—tools such as CLIs, IDE extensions, client libraries, local networks, and more. We’ll also contrast these to Ethereum tools you may already be familiar with, so if you’re making the switch to Flow, you’ll know exactly what to expect. Command-line Interfaces Command-line interfaces (CLI) are the bread and butter of software development. They are intuitive for most developers and integrate easily with other software. This easy integration applies to smart contract development as well. For example, if you need to quickly deploy a contract to test it or run it with different accounts, a CLI can help immensely. And later, when you want to add the deployment process to a CI/CD pipeline, you’ll be happy to have a simple CLI tool you can automate with shell scripts. On EVM-compatible networks like Ethereum, Truffle and Hardhat both offer powerful tools for these tasks. The is used for almost all actions with Hardhat, while the __ __enables developers to quickly interact with their smart contracts via JavaScript without having to write script files. Hardhat Runner Truffle Console is the primary tool for developing, testing, and deploying smart contracts written in Cadence to the Flow network. In addition, it’s the interface you use when interacting with the Flow blockchain, such as creating and checking accounts, signing transactions, or automating tasks with scripts. The Flow CLI Unlike Ethereum, where you would generate an address to interact with the blockchain, Flow requires you to have an account. This account holds your smart contracts, tokens, and keys, and is necessary for interacting with the blockchain. You can . easily create accounts using the Flow CLI IDE Extensions Next, you want to write some code, and languages like Cadence and Solidity offer static type checking that gives you some helpful information about how your code will behave in your editor. While Solidity comes with a fundamental type system that prevents you from mixing different number types, Cadence goes a few steps further and introduces the concept of ownership. You might know this from Rust, but the basic idea is that Cadence has resources, like NFTs, that can only be owned by one address. A Cadence IDE extension will notify you about issues with your NFT transactions right at the point when you’re writing the code, while also offering syntax highlighting, code completion, and type checking. Linters You might know linters from languages like JavaScript, where no static typing is available. In this context, a linter helps to prevent common errors and to aid developers in following best practices. The same is true for , a linter tool for Solidity. Again, Solidity’s static type system is very rudimentary and doesn’t prevent many errors while using the language. Solhint comes to aid here and provides tips on top of the type system to avoid misuse. Solhint The Cadence language has a much more sophisticated type system and comes with more help than Solidity. A correctly typed Cadence smart contract is more secure than a correctly typed Solidity one. The typical linter functionality is built right into the Cadence language itself through its type system, but if you want to run type checks on multiple Cadence files inside your CI/CD pipeline, the tool can help. Cadence lint Local Networks A local network, or a network emulator, is a tool that will run a blockchain network on your development computer, so you can test in a clean environment and not risk pushing unfinished smart contracts to a live blockchain. A local network also has lower latency and allows you to control the block creation, so you can step through everything that happens when your smart contract executes. When developing on the EVM, you probably know and use or Ganache for this task. Both tools simulate a blockchain environment on your local machine and allow you to fork a version of mainnet to interact with real accounts and contracts. the Hardhat Network Flow offers a similar feature called that simulates the real Flow network but gives you to interact with. It enables account storage limits, setting initial FLOW token supplies, and enabling persistent state between restarts. This powerful tool is used via the Flow CLI mentioned above and together, they provide all the features developers need to build fully functioning dapps and the environment to test them in. the Flow Emulator more options With the , all one has to do to start the emulator is type the command flow emulator in their terminal. Flow CLI installed Testnet Faucets When developing smart contracts, you typically need crypto tokens to deploy and interact with your code. Otherwise, how will you test transactions? Flow, just like Ethereum, has__ __ that comes with that drips you free testnet FLOW or FUSD for development. a testnet a faucet Additionally, Blocto Swap is a multi-use tool that makes creating an account on Flow simple for users. All one has to do is enter an email address. Blocto Swap allows users to easily exchange their tokens for different types to use in testing. This tool is also a handy way to get FUSD if that collection is not already initialized in the account. : tokens on a testnet hold no value outside of testing. Remember Automated Testing Cadence and Solidity both have test automation tools that allow you to write your tests in JavaScript. The Hardhat development tools use the Chai test runner and supply you with and for the EVM. smart contract matchers network helpers Cadence has that use as the base, but they’re framework agnostic. So if Jest isn’t your thing, you can use a different test runner. its own tools Jest Blockchain Explorers Another vital part of all blockchain networks is the block explorer—a tool that allows you to check out everything that happens on-chain. For the Ethereum network, you might know . It’s a web application that lets you browse mainnet and testnet transactions and addresses. Etherscan Flow comes with a much more powerful tool, ! Flowser Flowser (Flow Browser) is a web application, but you can run it locally. It allows you to browse both the Flow mainnet and any local network you start with the Flow Emulator. It even comes with a GUI to configure and start an emulator and manage your development wallets. However, if all you need to do is check transactions or browse on the Flow mainnet or testnet, then the traditional block explorer__ __ will suit your needs. Flowscan Additionally, the tool allows users to inspect accounts and their various attributes, such as balances, keys, and any contracts they may contain. flow-view-source Interfacing with JavaScript To build a decentralized application (dapp) for your smart contract, you need a bridge between the blockchain network and the web. Flow and Ethereum both come with Webpack integrations to solve this problem. will automatically reload your application when you change your Solidity code, so your frontend always runs with the current version of your smart contract while in development. The Solidity Loader Cadence offers similar features via its and . Webpack plugin the Cadence utilities Additionally, the (FCL) JS is one of the best ways for a developer to quickly start building on the Flow blockchain. This package makes interacting with wallets and smart contracts simple and secure, while providing all the tools necessary to create fully functioning dapps. Flow Client Library Playgrounds Being able to test your code in environments without having to invest the time in creating an entire project enables developers to quickly figure out what works and what doesn’t. To that end, Flow has the . Not only is it an excellent resource to iterate through ideas quickly, it’s also a great environment to learn in, with tutorials included to teach important concepts and how to build common projects. Flow Playground Although Ethereum doesn’t have any projects exactly like the Flow Playground, there are a few you could take advantage of to create a similar experience. The online Solidity code editor, , provides an environment to quickly build and test smart contracts. Additionally, you could follow along with the to help get you up to speed with Solidity and Remix. Remix Developer DAO Academy Summary Software development, and smart contract development in particular, is a complex process that consists of different vital steps. Planning, coding, testing, deploying, and maintenance are all important parts of the process, and having the proper tools at hand makes things easier. Although Flow has a younger ecosystem compared to Ethereum, the tools and libraries available are mature enough to help speed up the development process. From command-line interfaces and IDE extensions to local networks and block explorers, Flow has all the tools an Ethereum developer might be expecting and more. Additionally, the type system and built-in features of the Cadence smart contract language offer controls that Solidity can’t offer without additional tools such as linters. Even then, the value those Solidity tools delivers is inferior to the features Cadence provides natively. Overall, the Flow ecosystem comes with for each step of the development lifecycle. To get started building on Flow, check out their . Developers are also encouraged to share their own tools with the ecosystem, contribute to already existing tools, or to build your projects. all the tools you need Developer Portal apply for grants For a list of other great tools in the Flow ecosystem, . check out this Github repo Have a really great day!

Building Easy Workflows For Web3 Using Flow & Cadence

How To Write a Solidity Smart Contract and Deploy it on Ropsten

Cómo escribir un contrato inteligente de Solidity e implementarlo en Ropsten

Comment rédiger un contrat intelligent Solidity et le déployer sur Ropsten

सॉलिडिटी स्मार्ट कॉन्ट्रैक्ट कैसे लिखें और इसे रोपस्टेन पर कैसे लागू करें?

Solidity スマート コントラクトを作成して Ropsten にデプロイする方法

Como escrever um contrato inteligente de solidity e implantá-lo no Ropsten

Làm thế nào để viết một hợp đồng thông minh vững chắc và triển khai nó trên Ropsten

如何编写 Solidity 智能合约并将其部署在 Ropsten 上

Or — why you shouldn’t try to know everything I’ve really gotten into podcasts lately — they are accessible, they are free, and there’s a ton of them. A couple of days back caught my attention. Podcast authors spread the ideas of how to live meaningful lives with less. Just to make it clear — I’m not even close to being a minimalist. If there’s something to buy, I’m on it. However, one of their episodes, mysteriously named , sucked me in completely. I got so affected by the topic I wasn’t able to get it out of my head ever since. The Minimalists “Access” In the aforementioned episode, hosts Joshua Fields Millburn and Ryan Nicodemus discuss of things versus access to things with Ryan Delk from Omni. The basic idea behind the topic is that people of our generation are trying to own everything while losing access to what they actually need. I see this as a huge issue as well and I believe it is not limited to the items we buy. ownership We will never own everything There is no doubt that it is impossible to own everything for most of us. Yet somehow we are still trying to do that. There was a simple yet very accurate example provided in the podcast. Imagine this — you own a house with a two-car sized garage. You also own a lot of stuff you rarely use — a ladder, a drill, a drone, a DSLR, and lots more. You are obviously keeping all of these things in your garage as you do not need them most of the time. Your garage eventually gets so overloaded that there is no space left for any of your cars. What’s worse — you are about to travel to Greece, you need your DSLR but it is so deep inside of your garage you do not have enough time to unload everything for the access to the camera. This leads to the vacation without quality pictures and that sucks! This perfectly illustrates the paradox of owning more while owning less at the same time. I believe this fits well into our career lives as well. What we own and what we want to own in our jobs is knowledge. Usually, we want to get involved in our businesses as much as possible and the most straightforward way to achieve this is to try to know everything that’s going on around us. We think that by having more information, we will be able to participate in more meetings and become a part of more of the decisions being made. Well — this is not entirely true. Why? Try to re-imagine our garage situation with a few changes — replace the garage with your head and look at every single piece of information you are receiving as a separate item. You will see that we face the same issue — our minds get overloaded and the accessibility of information decreases. Our brains are not designed to remember everything as garages are not designed to fit everything in. One of today’s best-known memory researchers, Elizabeth Loftus, has identified a few reasons why people forget. One of them fits our case very well — . This theory suggests that some memories compete and interfere with other memories, especially when pieces of information are similar to each other. This is often the case if we think about the information we receive while at work. All of it is related to our company, our field, and our daily problems. Due to this, our brains cannot access the specific memory because previously learned information is blocking new information or vice versa. interference theory This and other limitations of our brains brings us back to the paradox when our knowledge increases and decreases at the same time. By knowing more, we reduce the access to our own knowledge more. This is entirely against our initial goal of becoming more involved — we actually find ourselves incapable of participating in the company’s processes because the information we had is suddenly gone. Build an infrastructure Minimalists see the one and only solution to this problem — sharing infrastructure. We can only stop buying so much stuff when there is another way to access the items we need. If there is no easy and cheap way to get DSLR for our trip to Greece, we will buy it and put it in the garage after the trip. However, if we could rent it for a week and even get it delivered to our doors, we would never even consider buying it. For all of this to become a reality, we need to build an infrastructure and it needs only two things to work — service providers or tools to enable us to get access to things and a critical mass of enthusiasts who would use these services instead of buying. And once people stop buying — their garages start to declutter. And this does not mean that people start to make trade-offs of some kind and find themselves lacking things. They actually kind of owns everything now as they have access to every possible item in the world at any time. Same applies to our . With correct infrastructure, we might start knowing more with less information in our heads. We do not become lazy and we do not start to embrace apathy and ignorance — we simply learn how to access information. Knowledge sharing infrastructure can be successfully built with the same ingredients as item sharing infrastructure — people and tools. It would never succeed without the vast majority of your colleagues understanding it and trusting it. A few pioneers might be enough for starters but the mindset has to become global eventually. knowledge I have noticed that knowledge sharing itself is a bit trickier than lending items to other people. It’s easy to get a drone from your room and carefully place it in the trunk of your friend’s car. But when it comes to our knowledge, we have to know how to effectively share not only the information itself but the full context as well. What’s making it even harder is time needed to do that. We might have been collecting information piece by piece for weeks and now trying to share it all at once during an hour-long meeting. This is where correct tooling comes. We need to build and use tools that make sharing and accessing information easier and almost effortless. Like Omni does with item sharing — they eliminate all of the struggles and effort needed to transfer items from one place to another by fully handling the delivery process. We need something like that for our knowledge. Invest in people and dedicate The very first thing you should do in order to build an infrastructure is to embrace high trust culture in your company. You have many smart people who can help you avoid overloading your head with information around you. And as I have discovered, many of them are more than happy to use their “garages” to keep part of the knowledge we own. So, we have to transfer bits of our knowledge to them or let them get the information in the first place and trust them as a reliable storage for it. Sometimes it is hard to get over ourselves and let other people know more about something than we do. But remember this — it is way better to know who knows than to not know. Some of you might ask — how do we keep track of who knows what? Well, you will need to do some experimentation. You will need to find out what kind of process helps you keep everything organized best. One way to achieve that is to dedicate like we do. We have people and/or teams dedicated to specific knowledge. We try to keep at least one person as the owner of some kind of a knowledge. Let it be a business field, an internal service, a tool or even a mindset. What this gives us is the first step for the access to knowledge. If we know who owns the most of the information, we can go to that person or team and get what we need or at least further directions. This helps us to organize knowledge sharing infrastructure and improves information accessibility. You can introduce the same thing to your companies or find your own way to do that. As long as your shared knowledge is organized, there is no wrong way. Find the right tools If you got everything figured out to this point, you have already improved your knowledge sharing process a ton. However, there is always that next step. What we have so far is knowledge spread across the whole company and well organized. But we still need at least two people when we need to access even the tiniest bits of it. And what if the information owner is on vacation? Or worse — what if he’s leaving and a new owner is being dedicated? In some cases, our access is still limited and sharing becomes difficult again. By picking the right tools and getting them used by information owners, we can solve these issues. Essentially, we have to pick a way to get our knowledge digitalized to some point. We need to get our knowledge to the cloud somehow. And there is no one right way to do that. It highly depends on how you share the knowledge, what are your workflows, etc. For example, if you are a software engineering company and most of the information is put to the Jira tasks, you might want to focus on improving your user stories, labeling tasks consistently and linking tasks to the Confluence pages that contain detailed documentation of relevant business requirements. You can also start a decision log and link decisions to the tasks as well. Another example, if your company shares new information via presentations and demos, you could put all of the slides and manuscripts, or recorded presentations to the Google Docs. In both examples, you should always tag owners and stakeholders next to the data items so others could clearly see who knows what. This actually solves both of the issues we’ve found earlier. If the knowledge owner is not available, we are not stuck. We can either find a documented answer to our inquiry, or other stakeholders who are probably available. Also, in the case of knowledge owner leaving, he does not need to transfer all of his knowledge to the new owner. Mostly, he needs to introduce the structure of his documentation and teach new owner how to use it. This process could become extremely fast if every team and every individual in the company would use the same patterns when documenting. However, it should not be forced as separate teams might find unique ways to digitalize their knowledge better than other teams do. Flowchart diagrams are an excellent way to document information for developer teams. But marketing teams will most likely find them useless. So, let every team their own tools as long as they use them. Conclusion Knowledge sharing has always been an important aspect of a modern company. However, people make a mistake and try to keep as much information as possible in their heads. You do not need to know everything, you only need to know how to access information. You also need to know how to keep your knowledge easily accessible. And, the minimalistic approach might be a good way to start.

Forget ownership, focus on access

Stories, News & Mentions about SHARESMART

Sharesmart’s Stories on HackerNoon