Edit on the Spot offers remote video editing in real-time as the video being recorded or live-streamed to help content creators eliminate traditional costs and complexities of video production and editing with ‘done-it-for-you’ remote editing on demand. \n\n

Edit on the Spot

The wait is over! - it’s time to celebrate the champion startups of the world. Shout out to all of the participants in our ! You did a wonderful job showcasing your incredible startups and powering through another year. 2023 Startups of the Year is a community-driven voting platform brought to you by HackerNoon that recognizes and celebrates tech startups changing technology and the world for the better. The award started on May 8th, 2023, where the internet nominated and voted for 30k startups around the world. The voting period remained open until December 31, 2023, and now we are here with the winner announcement after a comprehensive evaluation by the HackerNoon team. Startups of the Year 2023 To see the top 3 startups in each respective city, visit and pick a city. hackernoon.com/startups You’ll get a little surprise 😉 Here are the Startups of the Year Regional Announcements: North America Europe Asia Africa South America Oceania Misc/Remote From all of us at HackerNoon, thank YOU for your excellent campaign perseverance 🥺 This year has been awesome! Startups of the Year 2023 is concluded with 623k+ total votes, up from 215k+ votes in the inaugural startup competition. We look forward to seeing you again in the next campaign (stay tuned 😉)! Without further ado, let us kick off the announcement by celebrating the cities with top votes per region for 2023 🎉 North America (11,697 votes): Winner: Bloomfilter Cleveland, Ohio (8,835 votes) - Winner: SerpApi Austin, Texas , California (5,564 votes) - Winner: Finch San Francisco (4,258 votes) - Winner: RELAYTO SoMa, California - (3339 votes) Winner: Windscribe Toronto, Canada, North America (3304 votes) - Winner: Vouched Seattle (2716 votes) - Winner: Seccuri Palo Alto, CA, North America (2671 votes) - Winner: Salsa Valley Miami, FL, North America (2,613 votes) - Winner: Majhi Group Manhattan, New York (2423 votes) - Winner: Flieber, Inc. New York City, NY, North America See the complete announcement for the . Startups of the Year, North America, here Europe (45,612 votes) - Winner: Algomo London, UK (2,344votes) - Winner: Data Lake Warsaw, Poland (1,955 votes) - Winner: Hoken Tech Bari, Italy (1716 votes) - Winner: Not8 Amsterdam, Netherlands (1657 votes) - Winner: KYVE Frankfurt Am Main, Germany (1566 votes) - Winner: BazaIT Kyiv, Ukraine (1496 votes) - Winner:  Unity Network Tallinn, Estonia (1,478 votes) - Winner: Volcaino Ghent, Belgium (1,288 votes) - Winner: Owl Me Dublin, Ireland (1198 votes) - Winner: Groover Paris, France See the complete announcement for the . Startups of the Year, Europe, here Oceania (3,350 votes) - Winner: Sharepass Melbourne (2,107 votes) - Winner: The Catfisher Project Perth, Australia (220 votes) - Winner: Gemini AI Solutions Auckland, New Zealand, Oceania (213 votes) - Winner: Nexustorage Wellington, New Zealand, Oceania (138 votes) - Winner: Coviu Sydney (124 votes) - Winner: Bopple Brisbane, Australia, Oceania (124 votes) - Winner: Regional CFO New South Wales, Australia, Oceania (106 votes) - Winner: Edit on the Spot Gold Coast, Australia, Oceania (93 votes) - Winner: Knowledge Satnav Canbera, Australia, Oceania , Australia, Oceania (48 votes) - Winner: Peptalk360 North Melbourne, Melbourne See the complete announcement for the . Startups of the Year, Oceania, here Asia (16,345 votes) - Winner: Serenity Shield Singapore (13,588 votes) - Winners: QUIXY Telangana, India (10,168 votes) - Winner: HealthySure Mumbai, India (3,865 votes) - Winner: InterviewBuddy Visakhapatnam, India (3,733 votes) - Winner: Omniflo Bengaluru, India (4589 votes) - Winner: MeNow Tel Aviv (3877 votes) - Winner: ForestVPN Dubai (2478 votes) - Winner: TechGraph Powai, Mumbai, India (1004 votes) - Winner: Reelo Ahmedabad, GJ, India (875 votes) - Winner: Debt Hunter Hong Kong, China See the complete announcement for the . Startups of the Year, Asia, here Africa (8,179 votes) - Winner: GO PLATFORM Algiers, Algeria (767 votes) - Winner: Tudu Accra, Ghana (415 votes) - Winner: Treford Lagos, Nigeria (265 votes) - Winner: Phalconwise Ogbomosho, Nigeria (157 votes) - Winner: AbuErdan Cairo (151 votes) - Winner: Eazipay Lekki (144 votes) - Winner: KaziConnect Dar es Salaam, Tanzania (101 votes) - Winner: faceATT Gauteng, South Africa (79 votes) - Winner: Dimagi Cape Town (71 votes) - Winner: Sabi Addis Ababa See the complete announcement for the . Startups of the Year, Africa, here South America (376 votes ) - Winner: UpGirl Santiago, Chile (217 votes) - Winner: Klever Sao Paulo, Brazil (191 votes) - Winner: Tributo Simple Buenos Aires, Argentina (127 votes) - Winner: Light-it Montevideo, Uruguay (87 votes) -Winner: Thousand Antioquia, Colombia (108 votes) - Winner: GetLavado Lima (101 votes) - Winner: Cogniflow Medellin (73 votes) - Winner: TPAGA Bogota (73 votes) - Winner: Reliv Quito (47 votes) - WInner: Quantex Cordoba See the complete announcement for the . Startups of the Year, South America, here Misc/Remote: Featured Startups (1500 votes) - Winner: CIC Chain Remote, Earth (1193 votes) - Winner: Reship Colony US Misc (146 Votes) - Winner: Partful UK, Misc (116 votes) - Winner: GoMining British Virgin Islands Misc (283 Votes) - Winner: tomorrowSpace Germany Misc (225 votes) - Winner: Dtravel Cayman Islands See the complete announcement for Misc/Remote startups . here Once again, HUGE CONGRATULATIONS and BIG PROPS to all of the top Startups of each region this year! The whole team at HackerNoon would like to thank you for your perseverance in the campaign, and we look forward to seeing you in the next campaign. About HackerNoon’s Startups Of The Year Startups of The Year is HackerNoon’s Flagship community-driven event celebrating startups that survived and thrived in 2023. 30,000 startups across 4200+ cities and six continents participated this year to be crowned the best startup in their city. Visit our page to learn more. FAQ Companies that blog more get 67% more leads - Jumpstart your company’s blogging journey by purchasing our . Business Blogging Package The 2023 Startups Of The Year is sponsored by: . . The winners get a free .Tech Domain, a HackerNoon NFT, and a Tech Company News Page. TECH Domains

Stand Up for the Champion Startups of the Year! 

বছরের চ্যাম্পিয়ন স্টার্টআপের জন্য দাঁড়ান!

Setzen Sie sich für die Champion-Startups des Jahres ein!

¡Defiende a las startups campeonas del año!

Défendez les startups championnes de l’année !

वर्ष के चैंपियन स्टार्टअप के लिए खड़े रहें!

今年のチャンピオンスタートアップのために立ち上がろう!

올해의 챔피언 스타트업을 위해 일어서세요!

Defenda as startups campeãs do ano!

Встаньте на защиту стартапов-чемпионов года!

Yılın Şampiyon Startup'ları için Ayağa Kalkın!

Hãy ủng hộ các công ty khởi nghiệp vô địch của năm!

为年度冠军初创企业挺身而出！

As a beginner programmer, you can be surprised to see that people care so much about what goes into the git repository. Or worst, you can be wholly unaware & do your thing full of: * fix the bug
* another attempt
* another attempt * another attempt * ! 2 2 finally while being judged on it from behind. I check repo history whenever there is a job applicant, and they share a GitHub profile or some example work. My main question is - do they already know to keep the repository neat, or it's something we will have to work on when they join the team. Why so much Fuss? There is a big difference between the Git repository of a mature project and a repository created by an inexperienced developer. In a mature project, you can: Write a changelog or release notes based on the git history alone Revert some changes if necessary, with only the conflicts that couldn't be avoided Get the idea of what was merged by just seeing the git log Those uses case appear days or weeks after you merged the changes. If the commit history is a mess, you won't get much out of it anyway. As a beginner programmer working on a small project, you won't see much value on your own. Most likely, you will need someone more experienced to point it out to you. Focus your Commit on one Thing Alone A good commit does one thing alone. It's tempting to mix different changes, for example: Update coding style Implement a change Implement an unrelated change that happens to be in the same file Doing this makes two things more complicated than necessary: Writing short & accurate commit message Reverting only one of those changes Write Meaningful Commit Messages Think about the reader of your commit message. Even if you work alone, in a few months: You can forget everything about the change You can have a new colleague join the team Write a short commit message that quickly summarizes what's in the commit. If you did an excellent job following the previous advice, this should be pretty easy. Reference Ticket or Issue Reference tickets from the commit message if you have an issue tracking system set up for the project (for example, Jira). In this way, whoever wants to understand your changes better will have something to follow. If your project has no such system yet, you can consider setting up some. Both GitHub & GitLab have some available. Keep your Commit Messages Consistent When you scan or search through the git log, any inconsistency gets annoying pretty quickly. If some commits are capitalized differently than the rest - they get your attention for the wrong reason. If sometimes the verbs are in the past tense - your search should include both versions. If you want to make a changelog or release info - the inconsistencies will need to be edited before sending it out, and it's just simpler to do it on the commit time. How to do all of that? You want to commit locally as often as you see fit. Luckily, you don't have to write a perfect commit message in the first go. Write the commit messages for your work in progress so you can understand on the spot, and later edit them to get the final version. It's best to learn , as it's the most flexible method for editing your commits. It can be very difficult at first but knowing it is a good investment in the long term. git rebase As a more straightforward tool, when you have only one commit & want to rephrase the message, you could do it with . git commit --amend Learning resource All this is a step up from the basic pull-commit-push workflow you learn first. Resources I recommend for learning more: good explanation - both text & visuals 7 rules for good commit message Summary I hope I convinced you to put some effort into creating meaningful commits. Now, good luck learning how to do it! First Published here

The Right Way to Use Git

Over the past 2 years, I have published over 200 interviews for amazing founders, operators, and investors across industries ranging from social to healthcare to enterprise to fashion and more. I work on content full time at Zageno (a Series B, General Catalyst backed startup), head content for Elpha (community of 45K+ women in tech), direct content for Harvard in Tech and Techstars Boston, and write for TechCrunch, Pinduoduo, and BIOS. Here, I share my biggest learnings about how to create interview based content from doing effective cold outreach to having great interview conversations to writing tactical interviews to building your brand through content. Cold outreach Instead of framing it as a favor they would be doing for you, frame the interview as an opportunity for them to build their brand, get free media coverage, and generate awareness for their company and work. Present the interview as an opportunity. Show your give first mentality through listing a few ways you can support them, such as sharing product feedback, introducing them to investors or talented candidates, or connecting them with customers or partners. Even if they do not take you up on your intro offers, you show your deep understanding of their needs and show that you genuinely care. People are much more likely to engage with others with a give first mentality. List 2-3 ways you can help. Name other people you have interviewed, especially high profile ones, or interesting companies you have worked for. By leveraging social capital, you establish your legitimacy, build trust, and catch people’s eye, incentivizing them to even open and read through your cold email. Leverage social capital. Share examples of past interviews and be explicit about how much time you need from them and in what time frame. People are hesitant to sign up for ambiguous asks and ambiguous projects. Remove all the uncertainty upfront. Be clear. Beyond referencing their role or generally stating how incredible they are, be specific. Mention a project they did several years ago unrelated to their current role that they may be especially proud of. Allude to a personal passion they have, such as running or baking. Refer to a less well known platform they were featured on months ago. Show that you took the time to get to know them. People want to feel special. Add personalization. Interviewing Go beyond big name people and companies that have already been heavily covered by other media. For example, one of my favorite interviews to cover was with a solo, nontechnical, female founder in the travel tech space in the midst of COVID. While her company did not yet have a massive brand reach, the unique challenges she faced and overcame led to incredibly tactical advice relevant for many founders and operators. Similarly, when you see a company with an exciting growth story, look beyond the founders to silent operators in the company who may have driven the growth, such as their head of growth, director of marketing, VP of sales, or early business development hire. By unsurfacing under appreciated stories, you can fill a content white space and approach a story from a genuinely novel and unique angle. Find under appreciated stories. It can be awkward to have the first interaction be the interview itself. If time allows, have an initial call to answer logistical questions, get comfortable with each other, know what to expect of the other person’s communication style, and better understand their superpowers to craft more relevant questions for them to marinate on. Have a get to know each other call. You should *not* stick to a script of questions during the interview itself because the follow up questions are oftentimes most important, but you should share some topics and overarching questions for the interviewee to marinate on. Even if your questions are centered around their experience and other topics they are familiar with, many memories and insights are buried deep inside people’s minds. If they read your questions and topics in advance, they can mull them over in the back of their minds for a week or two before your conversation, which helps them make connections they would otherwise not be able to make on the spot. Share questions in advance. Interviewees think we only want the big picture, but the most actionable advice is the most micro. Instead of high level taglines like “hire great engineers” (which no one would disagree with and hardly represents novel insight), ask *how* they hired great engineers. What interview questions did they use? What channels did they leverage to source the talent? How did they pitch their company and the role to close the top talent? What types of training and onboarding practices did they implement to grow great talent in their companies? Ask *how* 3 more times than you think you need to. Put yourself in the shoes of your readership. Is this advice they could immediately use without external support? Get to the atomic unit of advice. Writing Instead of having to innovate on structure each time you write an article, remove that obstacle for yourself upfront. Find a structure that fits your style and stick with it. For example, my typical structure is a summary of the interviewee’s story followed by paragraph long highlights of their key insights. Find the structure that works best for you. For example, when I interview people, I do *not* write down every word they say. Rather, I listen first and think about what insight I can draw from the stories and messages they share. I then take notes from that perspective to help streamline my writing process. Take notes with your structure in mind. . I do not record my interviews because people open up more that way, and I more effectively actively listen when I take notes. But as a result, it is easy to forget the nuances from the interview, such as which stories the interviewee emphasized, which stories they shared with excitement or regret or sadness, or the tone of their voice or the subtle changes in their facial expression when they relayed certain messages. So I usually write the same day the interview takes place. I may edit later on, but getting the full story on paper even in draft form helps in preserving all of these nuances. Write as soon as possible Branding It can be easy to lose track of everything you publish. Even a chronological list of your publications is insufficient because it has no meaning. I have aggregated my interviews in 2 ways: on organized by tactical category (categories include things like doing user research, finding co founders, learning about new spaces, scaling companies, and leading large teams) to make it incredibly actionable and on which doubles as my main website where I categorize things by role type (operator, investor, founder) and industry so people can navigate based on their own goals and interests. Aggregate all your interviews. my Coda page my Notion page I use both LinkedIn and Twitter but have found LinkedIn to be the most fitting social network for me. I am less able to come up with pithy, witty phrases throughout the day and like to share more long form content, so LinkedIn has been more aligned than Twitter as a platform to share my content. After publishing my article on Medium or Substack or elsewhere, I share via LinkedIn (aiming to share 3-4 pieces per week to stay active but not overwhelm my audience). By doubling down on 1 main social platform, I reap compounding benefits in growing my audience and cultivating my relationship with them. Find a social channel. I respond to every (nonspam) social comment on my articles natively and via the social platforms I share them on. Doing so incentivizes more people to engage since they know they will be heard and helps to bump your post up in social feeds after your initial posting. Respond to every social comment. Ask your interviewees questions that let them shout out people they admire, appreciate, or work with. Ask about their portfolio companies, board members they enjoyed serving with, role models they look up to, and mentors they are grateful for. The people and companies they shout out are also incentivized to share your content, thereby further amplifying your articles. Empower more brand ambassadors. What one word do you want to be associated with? If you are the 20th person associated with 10 topics, you are effectively not the go to person for any topic. Go for depth instead of breadth. Have a clear end goal in mind so you can optimize your decisions along your journey more precisely to build your brand in a focused way. Have a clear end goal. Can you create a community around your readers? Can you do a meta analysis of the content you have created? How can you get more mileage out of your content through strategic resharing and developing multimedia content? Spend 30 minutes each week to think about how you can go above and beyond. Think about how to build further.

How Publishing 200+ Interviews Changed My Approach To Interview-Based Content

A is a part of the development process in which a developer and their colleagues work together and look for bugs within some code that may be ready for release. At such a moment, you can be either the code developer or one of the reviewers. CODE REVIEW On one side of this process, you might not be sure of what you are looking for. On the other side, when submitting a code review, you might not know what to expect. This lack of empathy and wrong expectations between the two sides can trigger unfortunate situations and rush the process until it ends in an unpleasant experience for both sides. Code reviews can be a powerful means to achieve higher quality code, establish best practices, and to spread experience and knowledge. It also lets developers learn from their peers, practice mentorship, and engage in open dialog and discussion about what they build. However, when done wrong, code reviews can come to nothing or harm the interpersonal relationships of a team. Therefore, it is important to pay attention to the human aspects of code reviews. To be most successful, code reviews require a certain mindset and phrasing. Here's how I have this organized: My Code Review Experiences. General Code Review Guidelines. Code Reviews as a developer. Code Reviews as a reviewer. Who Should Review? Positive Code Review Culture The Subconscious Implications of a Code Review My Experiences ... End-User Code Review (no process) When I started working as a developer, I remember having no code review process.  In fact, the only review I got was a notification that some bit of code was not working correctly when a customer reported the issue.  I learned very quickly that console.log did some nasty things with earlier versions of IE. Everyone Stare At Me (weekly target practice) From this, our team began an informal weekly process where we took some code and reviewed it while crammed into my boss's office.  What a painful process ... having to explain design decisions on the spot in front of the entire development team; or even worse, trying to come up with intelligent questions about code in a language I had little familiarity with. Everyone Reviews (learning to accept criticism) The next team I worked with had a review process that was embedded into the commit and push toward the production process.  Everyone on the team was included in the process, by default.  The tooling in actually made the process much simpler and quite intuitive; in fact, we were able to get a group put into Gerrit that allowed us to simplify the process of adding people as reviewers. Gerrit The first few times my code was pushed, the code reviews were painful (not having a clue what to expect) ... and I firmly believe I was learning almost as much about code reviews as I was generating code for the project itself. How Is One Individual So Good At This? We had an exceptional reviewer on this team that not only came up with exceptional insights into the code, he managed this in a way that made it feel painless.  Because of this interaction, I have taken the time to investigate how I can duplicate this type of effort (the painless part ... the insights I know will come with time). Code Review Guidelines These guidelines stem from what a code review should accomplish. It is impossible to lay out guidelines that can be applied to every situation. Keeping these goals in mind will help achieve "the spirit" of code reviews even when a situation comes about that these guidelines don't cover. Code reviews should: Verify that the code is a correct and effective solution for the requirements at hand. Ensure that the code is maintainable. Increase shared knowledge of the codebase. Sharpen the skill of the team through regular feedback. Not be an onerous overhead on developer time. As a Developer For you, as the developer (or “author”, “submitter”), it is important to have an open and humble mindset about the feedback you will receive. Anyone can do a code review, and everyone must receive a code review; no matter the seniority level. Receive any feedback gratefully as an opportunity to learn and to share knowledge. Look at any feedback as an open discussion rather than a defensive reaction. We are human. And, humans make mistakes. This is completely normal. As long as the software is written by people, it will contain mistakes. This does not mean that you should write code carelessly or stop writing tests. But this mindset will take away the fear of mistakes and create an atmosphere where making mistakes is accepted. This, in turn, is important for criticism during a code review to be accepted. Exchange of Experience During a code review, the developer and reviewer are exchanging best practices, experiences, tips, and tricks. The developer and the reviewer are not only talking about the code ... they are exchanging best practices and experiences. Code reviews are a great means to establish and internalize good coding styles and best practices. And the exchange works in both directions. So consider code reviews as a valuable source of knowledge and an opportunity to learn. As a Reviewer Locating code to improve is a small part of a successful code review. Just as important is to communicate that feedback in a healthy way by showing empathy towards your colleagues. As a reviewer, it is extremely important to pay attention to the specific language of the feedback. The phrasing is crucial for your feedback to be accepted. : “It’s hard for me to see what this code is doing.” Right Wrong: “You are writing cryptic code.” Always formulate the feedback from a personal point of view by expressing personal thoughts, feelings, and impressions. It is difficult for the code developer to argue against personal feelings since they are subjective. Before submitting a comment, remember to put yourself in the other person’s shoes. It is too easy to be misunderstood, so review the comment, always staying respectful ... speaking well to others is never a bad decision. Take the Developer Out of the Feedback Take the developer out of the feedback; only talk about the code that the developer is submitting for review. Criticism of the code is much harder to take personally because you are simply talking about the code, an objective thing, and not the developer. Again, this will improve the acceptance (as long as the developer understands that they are not their code). Non-Judgmental Collaboration The whole team's attitude and behavior should embrace , with the common goal of learning and sharing; regardless of experience level. non-judgmental collaboration Accept There Are Different Solutions Keep in mind that there are always different solutions to a problem. Most likely you have a favorite solution, but the developer's solution may also be valid. Distinguish between common best practices and personal taste. Remember that skepticism may just reflect personal taste and not incorrect code. Remember Praise It is totally acceptable to say: “Everything is good!”. is a valid outcome for a code review. Do not feel forced to find something wrong with the code. No code changes And last, but not least: do not forget to express appreciation if the code is good. Praising never hurts and may motivate the developer. Who Should Review It is my humble opinion that everyone on the team should be included on the code reviews.  Simply from a learning perspective, every team member gets to see the release descriptions at a minimum. I got to the point when in a hurry where I would simply check the comments made across reviews throughout the day.  By watching I was able to see what changes were occurring.  When I had more time, I was an active reviewer trying to help make the codebase better, one comment at a time. Foster a Positive Code Review Culture Code reviews done by peers can put a strain on interpersonal team relationships. It is difficult to have work critiqued by peers. Therefore, in order for a peer code review to be successful, it's extremely important that managers create a culture of collaboration and learning in the code review process. While it's easy to see an identified defect as purely negative, each bug found is actually an opportunity for the team to improve code quality. Code reviews also allow junior team members to learn from senior leaders and for even the most experienced programmers to break bad habits. Defects found in a code review should not be used to evaluate team members. If review metrics become a basis for compensation or promotion, developers will become hostile toward the process and naturally focus on improving personal metrics rather than writing better overall code. Embrace the Subconscious Implications of a Code Review The knowledge that someone else will be examining their work naturally drives people to produce a better product. This "Ego Effect" naturally incentivizes developers to write cleaner code because their peers will certainly see it. If your code is going to be reviewed, that is quite simply an incentive to double-check your work. Conclusions Code reviews are a powerful means to achieve higher quality code, establish best practices, and spread experience and knowledge. It also lets developers learn from their peers, practice mentorship, and engage in open dialog and discussion about what they build. To be most successful, code reviews require a certain mindset and phrasing. Thus, it is supremely important to pay attention to the human aspects of a code review. About Leading EDJE Also published at https://dev.to/leading-edje/better-code-review-practices-15nb/edit

A Practical Guide to Better Code Reviews

This November, 105 selected teams will co-create new solutions to complex global challenges using blockchain, AI and other emergent technology. The best ones will get €200.000 in total cash rewards as well as pilot opportunities with governmental, corporate and non-profit challenge partners, to scale their solution after the event. EDIT: Odyssey Hackathon was moved online and rebranded as Odyssey Momentum . Your portal to the future Odyssey provides a new space where everyone (and everything) can become part of a new solution to the challenges we face in the 21st century. These complex problems won't be solved by a single company, industry, or state. To address these issues, we need to build a new digital infrastructure and engage in mass collaboration. The challenges have a global societal and economic impact, each of them tied directly to one or more UN Sustainable Development Goals. Teams will be able to impact a variety of industries and make their mark on the energy transition, conscious cities, critical infrastructure, logistics, public safety, nature conservation, real estate, healthcare, and digital identity. The 2020 Odyssey challenges were contributed (among others) by: Vattenfall, VMware, DAML, City of The Hague, Enexis, KLM Cargo, TVM Insurance, the Dutch National Police, the Dutch Blockchain Coalition, the Dutch Ministry of the Interior and Kingdom Relations, Grid Singularity, Engie, City of Groningen, UMCG, the Dutch Land Registry (Kadaster), the International Union for Conservation of Nature, the International Council for Environmental Law, and the Dutch Ministry of Defence. Highlights - Odyssey Hackathon (4th edition) Collaborate with governments, corporations, and non-profits, their stakeholders and end-users, and build a prototype solution in 48 hours. Get support from more than 300 experts (aka Jedi) on the spot, including legal advisers Loyens & Loeff and financial regulators: Dutch Central Bank and the Netherlands' Authority for the Financial Markets. Continue developing your solution after Momentum: all teams get access to ecosystems related to their challenge for further prototype development and pilot launch. To see which pilot opportunities are prepared for the teams, navigate to "What Happens with the Winner" section of each challenge page. Since 2016, more than 230 prototypes have emerged from the program addressing the challenges of over 40 partners. Here's what some of the 2019 alumni teams have achieved: contract with the challenge lead to help protect 170.000 hectares of rainforest on Kalimantan; with the Dutch Chamber of Commerce to help it fight fake invoices with open data; by the Dutch Kadaster to develop the mock-up of the Dutch national real estate database. Space4Good signed a three-year project ChainMix continues working VX Company was hired The challenges of Odyssey 2020 (Vattenfall). Incentivize consumers to communicate energy demand and production to allow all stakeholders to balance the power grid. Co-create a fast and efficient digital power market commons to power an awesome fossil-free future within one generation. Balance the Grid . Create a smart meter energy data exchange protocol, incentivizing all consumers and mandated stakeholders to contribute and use smart meter data, to support the future EU prosumer-driven energy market. Future-proof Infrastructure for Smart Meter Data (Vattenfall) . Build the admission system (onboarding mechanism) that automates access to a public digital ecosystem of The Hague. Scale the Hague’s Living Lab to the rest of the city, region and (eventually) the world. Scalable and Inclusive Living Labs (City of The Hague) . Create a data commons and marketplace mechanism through which different actors will interact with each other in The Hague’s Living Lab, and where citizens are empowered to own, share and earn from their data. Incentivize all citizens and companies to interact with the public digital ecosystem of the city. Driving the Adoption of Living Labs (City of The Hague) . Each day of your life, you eat, you drink, you move, you breathe and live as part of an ecosystem, the earth our planet. All species need food, water, places to move and live. They make it work (in an emergent way). Today, man lives and does business. What would happen if you created critical infrastructures purely purpose-driven? What would a beneficial critical infrastructure look like? Building New Critical Infrastructures, Beneficial for the World (Nature 2.0) . Provide transparency on shipping characteristics from and for collaborating supply chain parties to ensure a compliant air cargo flow. Your solution will bridge the gap in trust in the air cargo market by enabling all parties in the supply chain to give and get relevant and compliant data. Compliant Air Cargo Flow (KLM Cargo) . How do we ensure better reuse of freight packaging in a world without incentives and transparency? Create a logistics protocol so anyone can localize, identify, certify, return, reuse, and repair freight packaging. Circular Economy for Freight Packaging (TVM) Create a data exchange infrastructure for public safety and security in communities, incentivizing everyone to share and exchange relevant data on incidents and crises, and allowing civilians to work with professionals to resolve emergency situations. Inclusive Safety Communities (Dutch National Police, Dutch Public Safety Alliance). . Create a new type of an automated dispatch center for digital crime (“the 911 for digital space”), allowing any organization to improve its reporting, warning and response mechanisms. Enable everyone to share relevant information about incidents and solutions so we all can fight digital crime. Open-Source 911 for Digital Space (Province of Groningen, Cybersecurity Noord-Nederland) . Demonstrate the value of Self-Sovereign Identity for business and society, by enabling all other Odyssey Hackathon teams benefit from an operational SSI framework and infrastructure. Collaborate on delivering an SSI ecosystem and framework to prove the identity of people, organizations and things in other hackathon tracks. Self-Sovereign Digital Identity in Action (Dutch Blockchain Coalition, Dutch Ministry of the Interior and Kingdom Relations) . Build an application using to simulate the bottom-up energy market of the future. Enable consumers to become active market prosumers, and find the new technical, regulatory and business roles of energy companies, DSOs, TSOs, and regulators. Interact with Digital Twin Simulations of Multiple Transactive Grids (Grid Singularity, Engie) www.D3A.io Build a solution that incentivizes corporations to source used plastic from communities in developing countries in order to create a socially inclusive and beneficial plastic sourcing process. From Plastic Pollution to Upcycling Economy (VMware, DAML). . Make C02 accountability as normal as paying taxes. Co-create an inclusive global CO2 accounting framework and infrastructure to accelerate the consumer-driven decarbonization of our global economy. Consumer and Organization-Driven Decarbonization (VMware, DAML) Create a coordinating infrastructure that supports all entry points to the acute care system to enable every patient to receive the best acute care path at the right time and in the right place from the right caregiver, taking into account the available resources. The Future of Acute Healthcare (City of Groningen, UMCG, Hanze UAS, University of Groningen, Province of Groningen, Odyssey). How can we aggregate and bundle a real-estate object’s distributed data through a Unique Object Identifier, demonstrating the benefits to real-estate developers, home-owners and regulatory bodies? The Unique Object Identifier should function like the familiar barcode used in many fields. Give Buildings a Personality (Ministry of the Interior and Kingdom Relations, FIBREE and Kadaster). https://bit.ly/2rgq8yn . Build a decentralized sovereign nature-data exchange infrastructure for anyone and anything to contribute and use its data on the High Seas. Enabling nature’s data to speak for itself and therefore enabling everyone to act on behalf of nature. Protecting Marine Biodiversity in International Waters (International Union for Conservation of Nature, International Council of Environmental Law) Use existing methodologies and tools to take away the violent approach to conflicts by co-creating an inclusive protocol empowering anyone to connect, contribute, act and learn the skills to prevent the violent escalation of conflicts. A Digital Architecture for Peace (Business Plan for Peace, Dutch Ministry of Defence, Innovation Centre FRONT). Generation Now doesn’t wait until tomorrow to take action. These 10-18 year-olds want to make an impact beyond school and beyond protest. Bring your (class)mates and start building the solutions the world needs, together with big companies and governments at the Odyssey Hackathon 2020. Who should apply? Generation Now (Odyssey). Momentum is optimized for startups, established startups, scale-ups, SMEs, corporate teams, as well as community and student teams who want to work on one of the challenges outlined. *Update: The Odyssey Hackathon 2020, originally scheduled for April 3-5, has been rescheduled and will now take place completely online. Read the message from Odyssey Founder & CEO Rutger van Zuidam, to find out more about the updated program, the new online Odyssey experience, and the open-source development of the new digital infrastructure to support the online hackathon.

Hack for UN Sustainable Development Goals in Odyssey 2020

Reading your article over and over, scrutinizing for even a minor mistake and then sending it to the editor, is what writers find the most tedious part of writing. And, this long process can make you hate your writing skills. But, this process can be cut short. Various writing tools will not only make your editing process easy or say on-the-spot but will also help you in improving your skills. Below is the list of editing tools that bloggers use to improve their writing and edit their articles. Have a look. 1. Grammarly The majority of the writers use Grammarly for editing their articles. It can be easily integrated on WordPress, Google Chrome, and can also be installed as the keyboard in the mobile phones. So, no matter what you are using to write your blog, Grammarly will be there for your assistance. It helps in correcting grammatical mistakes, spelling errors, passive voice, and many other minors and major grammar errors. You can choose the tone of your article as per your domain of the website. However, if you are worried about the cost of Grammarly, then you can just use it for free for the lifetime. Though, if you want to use its all options then it’s worth to purchase it. If you are confused about investing in the Grammarly, read the article – – is it worth the hype or not? Grammarly Review 2. ProWritingAid It is one of the most famous style editors. Like other editing tools, ProWritingAid also checks for the grammar errors, misuse of punctuations, overuse words, spelling mistakes, passive voice, etc. but it also looks for the writing styles. This editing software is the best for improving your writing skills. It gives an in-depth report of all the errors they have made. This helps them in learning grammar techniques while writing blogs. Also, its features like finding the right words, remove repetitive words, point out the clichés, and many others which you can read from the . ProWritingAid review 3. Hemingway Editor Hemingway Editor is another editing tool that bloggers use to learn quickly and it edits fast. The best part about this editing tool is it has different color codes for types of error writers make. For example, a wordy sentence is highlighted with the yellow color and other errors are highlighted by red color. It gives more clarity and power to write up by eliminating errors like adverbs, passive voice, and complicated words. 4. Ginger Software Ginger Software also ranks among the top editing tools that can help bloggers in improving their writing skills. It has an inbuilt sentence rephraser that helps in simplifying the complicated or long sentences. It has its own dictionary and a translator that can translate the text onto 50 other languages. Ginger software is more like a personal trainer who pinpoints your every grammatical mistake and helps you in writing a more effective article. 5. WebSpellChecker The best thing about WebSpellChecker is it gives you two options to edit your content. Either you can correct your content while writing or you can choose another option that allows you to correct in another window without making changes in your writing. The software indicates the mistake by underlining it and when you over the cursor then you can correct it. This way you can correct and publish an impeccable article on your blog site. 6. Ninja Essays Ninja Essays is an online editing services company. It hires writers with post-graduation degrees, PhDs so that they can edit the content of their customers. If you do not believe in robots and technology which claims to edit your content accurately then this service is only for you. The real editors and proofreaders will check your content before making it public. They edit content for mistakes like wordiness, grammar errors, complicated sentences and other minor mistakes like typos, punctuations, and spelling errors. Final Words All of the above-mentioned editing tools will definitely make your editing process easier. They will make you learn from your mistakes and help you in . improving your writing skills Being a blogger you need to be quick with your content and have so many tasks to do at a time that it becomes necessary to minimize some tasks. Using editing tools can help you in focusing on other works.

Six Free Editing Tools to Improve Writing for Bloggers

Done right, GIST keeps the team, management and stakeholders aligned on the why (goals), what (ideas) and how (steps and tasks), and every task we execute is connected to a business goal. A full quarterly plan creates a GIST tree per goal: Choosing a tool to manage GIST Most teams I meet already have system in place to manage tasks, typically using Jira, Trello, or Kanban boards. So we’re looking for something to let us manage goals, ideas and steps, while still “playing nice” with the existing task management systems and workflows — Scrum, Kanban or other. I’ll discuss three options: Spreadsheets / lightweight databases Project tracking / Workflow management tools The GIST board Upcoming Workshops — Lean Product Management In this workshop I will walk you through the principles and tools of lean product management — how modern-day PMs drive business results and optimize for high impact. Early-bird tickets are available now. : Barcelona — July 17 https://ti.to/itamar-gilad-events/lean-PM-BCN-July-2019 : Other dates and locations itamargilad.com/workshops Using spreadsheets or lightweight databases As an ex-engineer my inclination was to see GIST as set of linked tables: Consequently all early implementation of GIST used spreadsheets (most often Google sheets), or lightweight databases — Airtable, Trello, etc. These tools are usually free, simple to use and they let you to do everything you need with GIST artifacts — edit, search, sort, filter, color-code… Just as important, they natively support sharing and collaboration — important because GIST artifacts should be shared broadly and used in communication with management, stakeholders and other teams. Where spreadsheets and databases fall short is in showing the full picture. If goals, ideas and steps live in seperate sheets or views, there’s a risk of falling back to focusing on big projects, small tasks, and HiPPO ideas, the things GIST goes against. This is less of a problem for product managers, who are used to keeping the full planning stack in their head, but for team members, managers and stakeholders, it’s good to have a way to show how Goals, Ideas, steps and tasks interconnect. To receive posts like these by email sign up to my newsletter . Project tracking / Workflow management tools There days there’s no shortage of products to help you manage projects and workflows. Jira is the Agile dev teams’ favorite, but there are also Kissflow, Asana and dozens more. The good news is that many of these tools are flexible enough to manage GIST artifacts (OKRs, Idea banks, Step plans) and to create composite views. There are many ways to do this — a team I’m working with recently showed me how they combine collapsible Step plans and a Task kanban board in one view. I expect to see more and more of these types of adaptations. Eventually though, if GIST goes mainstream, we’ll see native GIST support out of the box. Here’s one very early example — Fiberi.io, now in beta, has implemented GIST as an app in their work management platform. The GIST Board Digital tools are cool, but for true ad-hoc collaboration and shared understanding, nothing beats sticky notes on a whiteboard. Enter the GIST board: The board shows the part of your quarterly GIST plan that you’re working on now: Goals on the left — typically these will be key results you set at the beginning of the quarter. It’s a good practice to write the target value as well as the current one. Ideas in the middle — Put here the ideas you chose for this quarter — the rest should live in an idea bank. If you use ICE, it’s good to write the up-to-date ICE score as well. Steps on the right — leave room because typically you’ll have 2–5 steps per idea. It’s good practice to put on the post-it the name of the person that is most responsible to make the step happen — can be a designer, engineer, PM, data analyst, product marketing manager etc. You use the GIST board in weekly/bi-weekly team meetings, working left-to-right. As GIST is designed to be agile at all levels, changes take place on the spot — ICE scores are updated based on experiment results, failed ideas are removed (with their steps), new ideas are added in their place. Even goals can be updated (up to a point). By the way, in the diagram above I’m showing steps arranged linearly, but that’s not always the case. Steps can occur in parallel as well. You can probably see how the board helps in creating shared understanding and sense of ownership. It’s much harder for the team to miss that they are behind on their goals, or that some ideas are not working, or that we’re over-spending on pure engineering work. The team can also be more involved: contribute ideas and help score them, load-balance steps, evaluate results. As physical boards tend to hang around, the status is always visible to anyone, even outside team meeting. If you use a physical Kanban board, as many teams do, just place it to the right of the GIST board and tasks will flow naturally left-to-right between the boards. The board creates a useful view for managers and stakeholders too — a substitute for roadmaps and project Gantts. You should make sure to that they see the board regularly — send them photos weekly if needed. The challenge in using the board is that it is harder to do the things that spreadsheets are good at: edit, sort, re-order, share. It’s also not practical to keep your idea bank entirely on the board — there are usually far too many ideas to fit, and it will not help anyone to see them all the time. Finally your org probably expects (justifiably) that your OKRs will be saved in a digital format. So there’s going to be some duplication and copying from one medium to the other. So which tool Should I use? The decision largely depends on the style and preference of the product team. Keeping everything in a spreadsheet/database or in a project/workflow tool works fine, but requires the product manager to remind everyone of the why, what and how. Adding a GIST board can make a big difference in team involvement, but adds some duplication. Ultimately the benefits of extra visibility, shared context, and team collaboration are high, and I suspect you’ll find they justify the extra work. As always it’s a matter of trying things out, adapting, and building the system that works best for you and your org. Are you a GIST Practitioner? Are you using GIST planning your company? If yes, I’d love to hear about your experiences as part of the research for my future book. I’d appreciate it very much if you could . fill out this survey Upcoming Workshops — Lean Product Management In this workshop I will walk you through the principles and tools of lean product management — how modern-day PMs drive business results and optimize for high impact. Early-bird tickets are available now. : Barcelona — July 17 https://ti.to/itamar-gilad-events/lean-PM-BCN-July-2019 : Other dates and locations itamargilad.com/workshops To receive posts like these by email . sign up to my newsletter

The GIST Board — A New Way to Do Planning and Execution

Samurai Wallet, Ledger Nano, OpenDime and an Azteco Voucher Predicting the future accurately is difficult to do but with working tools in your hands, it’s easy to come up with possible workflows and then extrapolate freely. There are now several powerful, inexpensive and simple Bitcoin tools available that we can use to sketch out a speculative workflow for an ordinary Bitcoin user. This imaginary Bitcoin user gets paid in Bitcoin, and does not ever use a bank. These are some of the things she does as a part of her “Bitcoin Routine”. Martha works at a Coffee roaster’s office in London. She uses only Bitcoin as a 1 for 1 replacement for all her money purposes. At the end of the week, Martha is paid by her boss, Amanda. She receives her weekly wages into her long term Bitcoin storage by flashing her Long term storage QR code to Amanda. This QR code is stored on her . She can keep an eye on all the Bitcoin going into her addresses from this device, which if it is stolen, has no access to her motherlode of Bitcoin. Martha never goes into banks, has vanishingly small fees and is in total control of her money. “watch only” wallet Sentinel Amanda runs her large coffee importing, and roasting business that has international scope. Her company uses Bitcoin instead of money. All her Bitcoin is managed on a and she doesn't use banks. Amanda pays all her staff, bills and expenses in Bitcoin, receives payment for her ground and roasted beans and pays her foreign suppliers in Bitcoin also. When she makes an order for a shipment of raw beans from new suppliers (for example in Kenya), she pays into a Multi Signature Escrow account service, and the Bitcoin is released to the Kenyan grower when the containers clear customs. Amanda’s accounting procedures are a breeze thanks to Thanks to ’s work on standardized PostgreSQL tables for Bitcoin Businesses. Every week during payroll, Amanda asks her employees to flash a QR to her so she can pay them. The records keep themselves and everyone is paid instantly. Ledger Nano-s Pierre Rochard _Completed Phase 1 - Prototype Completed Phase 2 - Schema In Progress Phase 3 - Client Phase 4 - Calls Future..._enterprisebitcoin.org Enterprise Bitcoin When Amanda’s buyers are out in the field, contracting for new supplies of raw coffee in remote areas of foreign countries, her buyers can pay growers on the spot. Once the deal and price has been fixed with a handshake, the growers are handed an OpenDime. Amanda receives a text from her buyer in the field saying, “Push £10,000 to QR 33 we did the deal!!”, she scans the address into her Ledger app, and seconds later, the OpenDime has £10,000 on it. The grower uses Samurai wallet to verify the Bitcoin is on the OpenDime. The grower uses OpenDime as a form of cash. He can take it to local business who will pay him local currency for it on the spot. OpenDimes are in wide circulation because they are infallible, indestructible and can carry from nothing to millions. They are accepted everywhere globally at face value. _When we first read about OpenDime, the hardware Bitcoin Wallet, we were excited by what they appeared to have built; a…_hackernoon.com Exquisite OpenDime Finally, Biodun is a student in Hamburg. He does part time work in a beer guarden while he studies for his management degree. The beer garden doesn’t pay him Bitcoin; they pay him in cash. Biodun sends his sister Bola money in Accra every week. He can only send a little bit, but her other brothers also send her Bitcoin, and this keeps her going nicely. Biodun goes to his local supermarket and buys an with Euros on his way home. He redeems his voucher direct to his sister’s address from his phone every Friday like clockwork. The fees to send this money are very small, and Bola gets the ability to buy anything from anywhere on earth through services like Purse, who never reject her orders because she is from Ghana. She uses Samurai Wallet to store, manage and spend her Bitcoin. Azteco Voucher _Edit description_purse.io Purse With these scenarios as a starting point, you can imagine an infinite number of variations where the tools above fit in perfectly. Everyone saves time, money and hassle. Everyone is in total control of their own money, and they can do it from wherever they are, at any time. All payments are guaranteed, and never go wrong. Everyone can prove they paid, prove they were paid, and do many complex functions where trust needs to be secured, as in the case of international shipping of goods secured by Multi Sig. Bitcoin is used for small amounts between families, and large amounts between companies. It is everywhere, all the time, and there only needs to be Bitcoin; all alt-coins (what some people call “cryptos”) are . Since everyone is on Bitcoin, you always know you will be able to spend it and work with it with other people. redundant These four tools are just the beginning, but with them, many billions of fiat compressed into Bitcoin will be managed, moved and accounted for, changing the way business is done for millions of people. As more of these tools and the processes they make possible become normal, we will begin to see a large and very robust Bitcoin ecosystem emerge. Everyone will ask themselvs… How did we live without Bitcoin? Biodun sometimes tips Beautyon. He made it easy for him to use Bitcoin!

Edit on the Spot

editonthespot.com

-- employees

Since n.d.

COMPANY RANKING

EDIT ON THE SPOT

EVERGREEN INDEX #4067

Edit on the Spot WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

Edit on the Spot

editonthespot.com

-- employees

Since n.d.

COMPANY RANKING

EDIT ON THE SPOT

EVERGREEN INDEX #4067

RELATED COMPANIESRANK

STORIES ABOUT EDIT ON THE SPOT

Edit on the Spot WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!