Thirdwork

thirdwork

Anyone who has even a passing has probably heard the word ‘blockchain’ branded about. And no doubt many of those who know the term also know that blockchain technology is behind Bitcoin and many other cryptocurrencies. interest in cryptocurrency But what else do you know about blockchain? How does it work? What uses does it have? And what about blockchain’s prospects in the future? All is revealed in this article. What is Blockchain Technology? Blockchain technology can be defined as a system of decentralized public ledgers that store transactions. This transactional information is stored in chains of blocks – hence the name ‘blockchain.’ These computers on the network share this information through cryptography. is used for a variety of functions. In addition to cryptocurrency, it is also used for things such as healthcare, , supply chains, and electronics. Firstly, let’s look at how blockchain works. Blockchain smart contracts How Does Blockchain Work? All information on the blockchain is stored in blocks. These blocks don’t have any central entity owning them, they are decentralized. Several elements make up the workings of the technology behind blockchain. Decentralized Authority The whole premise of blockchain is focused on its decentralized nature. It is this idea that gave birth to Bitcoin in 2009. Preceding this, on October 31, 2008, was the publication of the Bitcoin , entitled , by its pseudonymous creator, Satoshi Nakamoto. whitepaper Bitcoin: A Peer-to-Peer Electronic Cash System In the whitepaper, it lays out how Nakamoto envisaged blockchain technology would work and his vision for a monetary system away from the reaches of banks; a system for the people. Nakamoto proposed a ‘purely a peer-to-peer version of electronic cash that would allow online payments to be sent directly from one party to another without going through a financial institution.’ On January 3rd, 2009, the genesis block on the Bitcoin blockchain was created. This was the first step in revolutionizing the traditional, centralized, bank-focused financial systems as we knew them. Nodes – What are they? Nodes are computers that connect to each other through the public ledger that is a blockchain network to share information. Each node stores a copy of the blockchain and verifies every transaction made on it. As every node on the blockchain would need to change their records of the information stored, the tampering of information is a rare occurrence. These nodes play an important part in the because, in the absence of any central entity, it is the job of these nodes to align in agreement to confirm the validity of a transaction on the network. Bitcoin mining process Only when this verification happens can a block be added to the blockchain, and miners can get their rewards (on the Bitcoin blockchain, this is currently 6.25 BTC after the most recent .) Bitcoin halving How these nodes form a consensus is through consensus mechanisms. The ones mostly used in cryptocurrencies are Proof of Work (PoW) and (PoS). The most commonly used out of these two is PoW, which Bitcoin uses, and other cryptocurrencies such as Litecoin. Proof of Stake Consensus Mechanisms PoW and PoS are the main two consensus mechanisms in crypto, but others exist as well. PoW: This involves miners competing against one another in order to solve a complex mathematical problem known as a hash. By doing so, a miner validates a new block on the blockchain and receives a reward in the form of a new Bitcoin. PoS: Opposed to PoW, the ‘winning’ miner in PoS is chosen at random. However, the higher the stake a miner has, the more chance they have of being chosen. This will be implemented on the upgrade. Ethereum 2.0 Delegated Proof of Stake: This is different from POS in that delegates are effectively elected to mine new blocks and ensure consensus rules are maintained. If they fail to do their jobs properly, they can be voted out just in the same way politicians can be. Cryptocurrencies such as EOS use this consensus mechanism. Cryptographic Hashing The process of cryptographic hashing is fundamental to ensuring the security of a blockchain. It involves one-way encryption of data to a unique piece of text and is a process that cannot be reversed. On the Bitcoin blockchain, the result of the hashing process is a 64 character piece of text called a hash. Can Blockchain Be Hacked? As the unique piece of text cannot be reversed to decipher the original data, blockchain is seen as being very safe from hackers. On cryptocurrency blockchains, hackers can launch something called a 51% attack, where they attempt to gain more than half the hash rate (computer power) of a blockchain’s network. If they are successful at doing this, they can block or even reverse previously confirmed transactions, meaning they can ‘double spend’ coins (spending a coin twice). Although the Bitcoin network has never been subjected to a successful 51% attack, other cryptocurrencies have fallen to one. One such example was in May 2018, when the Bitcoin Gold network fell victim to a 51% attack, resulting in the loss of $18 million worth of the currency. Thankfully such events are very rare, due to the sheer amount of hash power needed to conduct an attack. So the hacking of a blockchain isn’t impossible, but it’s very unlikely. How is Blockchain Used? We all know cryptocurrencies use blockchain, but what else in the world benefits from the wonders of blockchain technology? Cryptocurrencies As already explored, the blockchain forms the fundamental underpinning of what defines a : a decentralized asset free from the shackles of a central entity. Bitcoin may be the most popular cryptocurrency, but really it is just the tip of the iceberg. cryptocurrency A multitude of coins, from , to , to tokens, today are in existence thanks to the technology invented by Satoshi Nakamoto. altcoins stablecoins DeFi Healthcare Sensitive medical data of patients has been the target of from electronic health records (EHRs) and used to steal or impersonate identities or sold on to third parties. hacking Through advanced cryptography, blockchain can put an end to this. Records can be added to a trusted and secure blockchain, becoming longer over time, and when new ones are added, a consensus is needed, thus making it very difficult to break, and hence be hacked into. is one company that is using blockchain to give patients complete control of their medical data. A decentralized mobile platform, it allows patients to manage their health information and sell to third parties if they wish, in return for tokens. Health Wizz There have also been shortcomings in EHRs in terms of doctors accessing patient information that comes from another institution. This is because in some countries, different manufacturers often provide different EHR software for different institutions, and there isn’t interoperability between them. Although a single, comprehensive system would be beneficial to doctors and patients, this would reduce the ability for the companies to charge extortionate fees. Attempts have been made to bring together EHRs under one system in many countries, but this has proven often to be a doomed process. In the UK, an attempt to create a linked patient data system for the whole of the was abandoned in 2011, costing nearly £10bn. National Health Service Blockchain could allow for a singular patient-owned system, where their information is transmitted safely and securely to different financial institutions, and be accessed as soon as new data is added to it. EHR Although it should be remembered that blockchain won’t replace the EHR itself – it has seven transactions a second, compared to an EHR which can have up to 12,000. It will, however, be able to act as an extra layer for additional functions, and prove that records are complete and unmodified, and record patient consent when it comes to data sharing. Smart Contracts A smart contract works in the same way any contact would work but through a blockchain, which takes away the need for any third-party intermediaries. Only when pre-set conditions (that have been set in the computer code of the blockchain) are met, does a transaction within the contract take place. Smart contracts were first established on the Ethereum blockchain in 2015. Today, they have many uses including: Insurance Smart contracts can make insurance claims a quicker and cheaper process because their use can help to clearly define when objective criteria are met. This may not be the case when it is the decision of lawyers if criteria have been met, as this may make the process more subjective. This in turn could lead to a longer and more expensive claim process. Supply Chains Supply chains can become easier to manage through the use of smart contracts. As with insurance claims, they can take away any subjectivity and make it easy to verify if set targets are being met within the blockchain. Again in healthcare, smart contracts have the potential to revolutionize the complicated in the US by cutting out middlemen, thus considerably cutting costs for consumers. prescription drug supply market Real Estate Smart contracts can make the ordeal of buying and selling a house a lot less stressful. By cutting out the need for a middleman such as a housing agent, buyers can now handle transactions with a potential seller all by themselves. Once the conditions of selling a house are met, the purchasing of the property can be done solely through the use of a smart contract. Video Games Believe it or not, the wonders of blockchain technology have even infiltrated the video game industry. In 2017, a game was released called CryptoKitties. The premise of the game was you breed, buy, and sell virtual cats. It may not be everyone’s cup of tea but what made this game so eye-opening was that it operated on the Ethereum blockchain. Since then, blockchain technology has become increasingly adopted in the video game industry, albeit this adoption is still in its early days. Collectible card games, such as Gods Unchained, have led the way in adopting the technology. In this game, gamers can trade collectible cards online by using an Ethereum wallet such as . MetaMask Blockchain Use in the Future The exciting reality is that the potential of blockchain technology has only just begun to be untapped. It really is just the beginning of the journey. Let’s look at some ways in which blockchain technology may develop and affect our lives in the future. Improving Global Living Standards Blockchain technology can help to alleviate poverty and corruption, and give financial inclusion to those who are unbanked. Besides, blockchain technology also provides tremendous growth potential for small businesses in developing countries. And with the decentralized nature of cryptocurrency allowing many of them for the first time to truly operate on a global scale. Blockchain Identities This is something that has already been started to be implemented, but it is likely that in the future, the move towards maintaining online identities through blockchain technology will excel. By storing personal database information on a public, distributed ledger, the risk of identity fraud will be greatly reduced. As already explored, blockchain has massive potential in changing the way healthcare records are met, but it is likely to extend to government records, employment records, tax records, and even voter records. In the 2020 US Presidential Election, were made. Blockchain could put such claims to bed in the future. Binance CEO CZ argued on Twitter that using a blockchain-based voting system would not only eliminate any doubts over fraud, but also enhance the privacy of voters: allegations of voting fraud Increased Transparency As we know, at the heart of blockchain technology is its decentralized and transparent nature. As the technology becomes more widely adopted, this is likely to be reflected in the way companies operate. It will become harder and harder to conceal information, which can only be good news for the consumer. Music The internet has of course changed the way we listen to music, and from the artist’s point of view, not necessarily for the better. Since Napster burst onto the scene in the late 90s, music piracy has been rife. Even with the advent of legitimate streaming services such as Spotify, income for artists has paled into significance compared to the days when fans bought CDs (and going further back) tapes in their droves. But could blockchain shift the pendulum back? The transparent nature of a blockchain could show for all to see what royalties artists are owed. Steaming services would no longer be able to short change them. Also, blockchain technology could help any intellectual property rights issues artists may have, by clearly indicating without any ambiguity who owns the rights to songs. The Bottom Line Simply put, blockchain is a revolution that is only just getting started. It is changing traditional ways we’re living our lives and has already revolutionized the way we think about money as digital assets, but in the years to come, it will revolutionize the way we think and act in many areas of our lives. Not only does its anonymity offer an extra level of protection for information, it also offers convenience for accessing information like never before. Blockchains give the access of information freely available to everyone. Disclaimer This article is intended for and only to be used for reference purposes only. No such information provided through Bybit constitutes advice or a recommendation that any investment or trading strategy is suitable for any specific person. These forecasts are based on industry trends, circumstances involving clients, and other factors, and they involve risks, variables, and uncertainties. There is no guarantee presented or implied as to the accuracy of specific forecasts, projections, or predictive statements contained herein. Users of this article agree that Bybit does not take responsibility for any of your investment decisions. Please seek professional advice before trading.

A Beginners Guide to Blockchain: Basic Terms and FAQs

One of the most interesting and potentially far-reaching art market developments to emerge from the tumult of 2020 was Sotheby's launch of a new online e-commerce venture called "Buy Now". The platform allows consumers to purchase fine art and other luxury items directly at fixed prices, with no intermediate auction bidding process necessary. It's a good example of how traditionally staid brick-and-mortar art businesses are rethinking and reinventing their business models with a "digital-first" approach to be more resilient in the face of ongoing social distancing measures and potential viral resurgences and more attentive to the expectations of today's digitally native consumer. The decision by the 277-year-old auction house to adopt a fully-fledged e-commerce model could mark the beginning of a new chapter in their long history and have an outsized influence on the future direction of the art trade. "Buy Now" Signifies a Broader Market Shift The embrace of the e-commerce business model on Sotheby's part has multiple layers to unpack. It's a conscious decision by the auction house to move from a seasonal auction sales cycle to a year-round, always available sales model, thus being more in tune with the more immediate gratification needs of the digital consumer.  It features a range of luxury goods, from fine art to jewelry and fine wines to classic cars, giving collectors many more choices, a more "complete luxury experience," and offering broader audience appeal to bring in potential new buyers. The strategy appears to be paying quick dividends; in December 2020, it was reported that 56% of buyers on the platform were brand new to Sotheby's. Less obvious perhaps, but no less significant, is the opportunity "Buy Now" affords Sotheby's to become better acquainted with its clientele by gathering and leveraging customer data from their online footprint. From a strategic standpoint, the last aspect has long-term implications beyond revenue figures and audience growth. It's part of a broader shift from the more customary in-person sales model used by galleries, art fairs, artists, and glitzy evening auctions to a more dynamic, data-driven digital sales model and to the way consumer trust operates within that digital model. Traditionally, art galleries, dealers, auction houses, and artists have developed relationships with collectors and earned their trust largely through face-to-face, social interactions, and these relationships have always been at the root of the in-person sales model. How well these parties know a collector – their background, tastes, interests, past buying habits, and typical spending range – and the strength of their relationship plays an important part in their ability to strike a successful art deal with them. The success and dependability of this in-person sales model, however, has plummeted under the twin pressures of pandemic curbs and ever more time spent online in a digital era. Physical encounters between art purveyors and collectors have been few and far between over the past year, sapping a key source of how trust and relationships with collectors are typically developed and nurtured. In the absence of physicality, a data-informed digital sales model offers opportunities to learn about customers from their data and online interactions, fosters deeper client engagement through more personalized digital experiences, and ultimately earns their trust. This strikes me as one of the most important value propositions of the "Buy Now" platform to Sotheby's and why it could be a game-changer for the art industry.  What are some of the ways that digital marketplaces for art like "Buy Now" can be designed and leveraged to earn the trust of collectors? Trust Through Transparency, Inclusivity, and Accountability Renowned trust expert Rachel Botsman in her book "Who Can You Trust", argues that we're entering a new era of "distributed trust", whereby trust flows horizontally to people, programs, and bots via digital platforms and networks rather than vertically to institutions. In this era, systems must become more "transparent, inclusive, and accountable" and be designed to "put people first." Online marketplaces for art that are designed and implemented to follow these guiding principles are more likely to earn the trust of collectors. One of the ways to put people first is to focus on giving them more control over their preferences and data, engaging them in how their data will be used in specific ways, and how that use will accrue benefits to them. This can be achieved through onboarding flows for first-time users that offer collectors various ways to personalize their experience by, for example, specifying the types of collectibles, fine art genres, artists, or brands they like. Options to scale the amount of contextual information a user will see while browsing for artworks or the amount and kinds of personalized content they see upon entering their home screen (e.g., news feeds, recommended works, upcoming flash sales, etc.) help communicate to consumers how their data will be used to improve their experience and situate them as co-creators in the customer journey. Another way in which systems can be designed to put people first is with the help of what Botsman refers to as "trust pauses." Trust pauses introduce intentional friction into systems so that users are forced to make a conscious decision when signing up for a service or handing over personal information. Introducing a spinning circle to slow users down when signing up for things or a pop-up prompt when a user clicked through a long 'terms and conditions' statement too quickly are examples of trust pauses that Botsman believes make people more mindful and more conscious of their actions and choices within an online system. Building transparency into online marketplaces for art means being clear and open about what data is taken from collectors and what happens to that data after it's taken. Hence why privacy policies explaining how data is used, and openness about the use of data to benefit consumers, by providing more personalized experiences, for example, is so important. Selling it to third parties without user consent, on the other hand, diminishes transparency and is a violation of privacy rights. Respecting consumer data privacy expectations and complying with data privacy regulations like GDPR, designed to give users more choice and control over their data, improves people's belief in the platform being trustworthy. Aside from transparency, what people are looking for in all sorts of institutions and informational systems is inclusivity. In the art world context, inclusivity means ensuring platforms for art are open and equally accessible to everyone and that the work of female and minority artists is given adequate representation. Calls for under-represented classes of artists to be included in art market events like art fairs apply just as well to online marketplaces for art and how their work is surfaced on those platforms. Online marketplaces that bring strangers together in frictionless ways have at times suffered from a lack of accountability when things go wrong. On this front, online marketplaces for art should consider using forms of third-party verification to endorse works for sale (a role art advisors, dealers, and auction houses have typically played in the traditional art market). Interestingly, since Sotheby's typically sells artworks largely through a consignment process, there is a de facto level of accountability built into their Buy Now platform since it means Sotheby's acts as a third party responsible for selling the work, and thus also responsible if the sale goes wrong. This might help to give the platform an edge in the trustworthiness factor over other online marketplaces for art. Conclusion The need for companies to develop close relationships and cultivate trust with their customers is important in many corridors of commerce but is especially true for the art trade, where enormous sums of money can trade hands and where wealthy collectors will often rely on the guidance and expertise of advisors before deciding to buy or sell a work of art. As the art business continues to evolve digitally and the art market moves online, and as we enter a new era of "distributed trust," it's critical for art companies to develop online solutions consumers consider trustworthy. Designing online art marketplaces to put people first, respect consumer privacy expectations and be more transparent, inclusive, and accountable are ways to demonstrate trustworthiness and earn consumer trust. In a time when institutional trust is waning, having such a focus is a clear competitive advantage. Originally published on blog.dataart.com By Doron Fagelson, VP Media & Entertainment at DataArt

The eCommerce Turn of The Art Market: Trust, Transparency, And Trustworthiness

Work management software is boring. Innovations are rare and you may think that no cool new vendors appeared in the last 5 years. Indeed, Asana is 10 years old, JIRA is everywhere and Trello was released in 2011. Are there any new tools coming? Can we expect a new paradigm shift? I believe it is happening right now. There are few promising vendors that trying to disrupt work management market 🌊. Vendors: Airtable, Zenkit, Notion, Coda Drivers Let’s try to generalize what drives this new wave. These drivers sorted by importance, so first one is the most important. . There are no specific entities like Tasks and Projects anymore. Specialization is gone. Everything is very fluid and you can define your own semantic. It means you can relatively easy use a tool to track Leads in simplistic CRM or User Stories in software development project. Domain Generalization . There are various ways to see information: Tables, Lists, Timelines, Kanban Boards, etc. All vendors try to generalize UI this way. Old vendors try to keep up with this trend as well, see how Asana and JIRA added . Interestingly, the first implementation of UI Generalization . UI Generalization Timelines recently appeared in Targetprocess in 2013 . Users are becoming more savvy and want to automate boring actions. Even in l . No wonder work management software should keep up. Coda gets Automation very seriously, Airtable less seriously and other vendors rely on (so far). Automation atest iOS release there are automation rules Zapier Most new vendors rely on documents or spreadsheet to handle work. Documents are becoming really rich with visual widgets, interactivity and subsections. Coda takes this approach to extreme claiming that “Document is an App”, Notion tries to do almost the same. Document-oriented approach. None of the ideas above are very new (well, maybe UI Generalization is the most fresh). For example, has Domain Generalization and Automation a decade ago. However, QuickBase is old, it’s UI is terrible and technological platform is outdated. New players will beat it eventually. QuickBase Work management software market entrance barrier is relatively high. To join the race, you need at least 2 years and 6–8 people team with tons of experience. It is time to dive into new vendors. They sorted chronologically, and Airtable is riding the wave with its first release in 2014. Airtable First Release: 2014Motto: Relational spreadsheets on steroids _Airtable works like a spreadsheet but gives you the power of a database to organize anything. Sign up for free._airtable.com Airtable: Organize anything you can imagine Why use Airtable when there are free alternatives like Google Spreadsheets? 30,000 companies found the reason. Airtable is somewhat-relational database with a very good UI and think-through user experience. It is flexible enough to support common and unusual cases, like track farm inventory, plan a trip to Japan or organize a wedding. You can start from scratch with a spreadsheet and quickly design your own app by adding columns and connecting several spreadsheets together. Strong things People are familiar with spreadsheets, they have years of experience in Excel, Numbers and Google Docs. It means Airtable is very easy to grasp and conceptualize. You can quickly build a mental model of the system and create your own things. Three main concepts are , and . Fields are very easy to understand and use, relations and blocks are harder. But you can start with fields only, solve some of your problem and then dig into more complex concepts. fields relations blocks Tables in Airtable are almost perfect. No wonder. The real thing is that you create not abstract rows in a spreadsheet, but entities with a custom entity type. You can see a row differently: as a card, as a popup, as a calendar element, etc. Row is an Entity in fact. However, you can’t customize this screen. Basically, you are designing your own database. This is a core of all new wave tools. The simplicity of this process is the core strength of Airtable. . It doesn’t have custom Blocks creation yet, but it will come eventually. Airtable has open API Weak things . It means you can build data islands, but with no connections. These islands are isolated. Imagine, you have a list of Customers. You want to use the same list in two Bases: CRM and Ideas Tracking. You just can’t do it. All you have is manual replication of Customers list in two Bases, which is labor intensive and error prone. Somehow relational part of Airtable breaks here. You can’t connect Bases together While Grids and Calendars are great, Kanban Board is not so good and there are no Timelines. It all means UI Generalization is not the strongest part of Airtable. It is quite hard to use Airtable for projects management, especially for software development projects. It starts to feel cumbersome when you have several teams and dozens of user stories in progress. Kanban Board in Airtable is loosing to Tables. The last serious limitation is lack of Documents. It is even . You have to store all unstructured information outside Airtable, and it makes Airtable weaker as a single source of data management. not possible to have a rich edit field inside an entity More information: Forbes: Move Slow and Make Things: Airtable’s Howie Liu Built A $1B Software Giant Emphasizing Substance Over Speed Zenkit First Release: 2016Motto: Simplicity, Choice, Growth _Different tools suit different tasks, just like different people feel comfortable with different tools. Whether you're…_zenkit.com Zenkit | Online Project Management Zenkit is quite weird beast. It seems it has a good engine under the hood, but everything becomes not so good on UI layer. In 2018 development stalled. There were few new features and nothing major released. It is not clear what’s going on. Maybe they are cooking something important, maybe product will be abandoned soon. In Zenkit you operate with Teams and Collections. This terminology is quite weird. Basically, Team unites several Collection, while Collection is a separate entity type. On the image below HR is a Team, while Applicants and Positions are collections. You can link Collections together, this creating your own Domain. Teams and Collections in Zenkit. You can visualize Collection as a List, Kanban, Table, Calendar and Mind Map. It works, but overall perception is that some of these visualizations are not finished. For example, you can’t have hierarchical Lists, you can’t set other Collection as a lane on a Kanban, you can’t group rows in a Table, etc. Different Views for the same data in Zenkit. Strong things Zenkit works relatively well for individual users or for small teams. You can create your own Apps via Collections and visualize data using List, Kanban, Table, Calendar and Mind Map views. Zenkit is fast and easy to use. Weak things You can’t connect Collections from different Teams. It means you will face exactly the same problem as with Airtable. If you have Customers in CRM Team, you can’t reference Customer in Ideas Team, for example. Zenkit has no public API, no custom UI extensions and poor integration with third-party software (only Zapier is supported). It looks very strange, since when you have flexible domain, integration becomes paramount. Zenkit has no Documents as well. It means Document-oriented work management is not there. Frankly speaking, Zenkit is quite close to Airtable and can solve very similar set of problems, but Airtable is more deeper application with similar limitations. is the only unique feature, but it doesn’t compensate all Zenkit weaknesses. It is hard to recommend Zenkit when you have Airtable. Mind Maps More information: Zenkit, First Take: A usable and customisable task management tool Why this former Trello user has moved to (and is loving) Zenkit Notion First Release: 2016Motto: All-in-one workspace _A new tool that blends your everyday work apps into one. It's the all-in-one workspace for you and your team_www.notion.so Notion - The all-in-one workspace for your notes, tasks, wikis, and databases. The last two apps (Notion and Coda) are closer to each other than the rest. Let’s start with Notion. In its first release Notion was just a Wiki, it became a work management software with . Notion 2.0 release in March 2018 In all honesty, the 2.0 is the real 1.0 for us. We added tables, Kanban boards, and calendars. Along with the existing notes and wiki features, Notion can finally deliver on the “all-in-one workspace” promise. We think you’ll love it! Indeed you can , transforming documents into apps. In fact App is a Workspace in Notion. For example, this is a Workspace for Tasks tracking. insert “Database” blocks into documents Tasks Kanban Board inside a Notion document. You can install many Workspaces, they visible in left menu. Each Workspace can have several visual representations of information. There are three Workspaces here: Roadmap, Meeting Notes, Tasks & Issues. Documents are really powerful in Notion. Strong things Notion is Document-oriented from day one. It is a powerful Wiki with all bells and whistles you need. You can create complex nested documents really fast and share them easily. is an example what you can do document-wise. Notion user guide You can connect databases from different Workspaces together. So far this functionality does not give you much, but at least you can have fully connected domain (improvement in comparison with Airtable and Zenkit). There is a hope that later it will be possible to utilize connected domain better, like group by reference in Kanban Board and create nested hierarchical tables. Notion is fast, it has slick design, great usability and it’s joy to use. The flow of creation is almost fun. Notion powers creative individuals. Weak things Notion is for usage, but not so great for teams. Small teams can survive the flexibility, but it seems larger teams are having troubles with the structure, it is hard to keeping everything together. When you have a lot of data and a lot of cases, Notion explodes. great individual What makes it hard for teams and companies? The are several things that matter: Notion designers break familiar semantic. Databases in Notion are Tables in fact. It is quite weird to have a relation to CRM, when you just need a reference to a Customer. Database represents just one entity type. It means you can solve a basic problem inside a single Workspace (like track tasks or plan blog posts publications), but more complex problem demands several Workspaces. For example, you need Features and User Stories inside. You just can’t have them in a single Workspace in a usable way, so it becomes cumbersome when complexity grows. You can’t see all required entities in a single place. Basically, you can’t create views that shows entities from several Databases. It all makes Workspaces shallow and inconvenient for complex problems, like product management or . software development management Notion has no open API at the moment and no custom UI extensions. It means integration abilities are poor. , however. API is coming More information: Notion for Notes and Project Management The Beginner’s Guide to Notion Coda First Release: 2017Motto: Document is an App _Coda is a new doc that grows with your ideas. We built it so the next generation of makers can build docs as powerful…_coda.io Coda. A doc for makers. Coda is strange. You want to love the product due to innovation, but just can’t. Main entity in Coda is a Document. But make no mistake, , it is an App. Below is an example of a single Document that allows you to run iterative software development project: this is not your familiar Document Coda has powerful tables, but they are more complex than in Airtable and less polished. Every Document can have several Sections inside. On the image above Sections are on the left and they are grouped into Folders. To me Section is a usual old document, so terminology in Coda is unnecessary weird (common pattern in all vendors, only Airtable get it right). Running work management project inside a document sounds insane, but it works to some degree when you accept that “Coda Document” is a group of Documents in fact. You can create as many Sections as you want inside a Document and visualize data using Kanban Boards, Tables, Charts, Calendars and Detail Views. Kanban Board in Coda needs some love… Notion and Coda concepts are very similar, but the devil is in the details. Strong things Document-orientation helps to connect data and text in a similar way as Notion does. These two apps almost on-par here. Coda has . You can automate many things, like assign a new task to a developer, send notification to Slack, etc. Automation is really powerful and it makes Coda unique, since all other vendors rely on Zapier and don’t have good automation rules. automated actions . You can connect Document to various external applications and do interesting things, like import data from Trello, create Pull Requests in GitHub with a button in a Document, etc. Integrations in Coda are Packs , which is always good. Coda has API already Overall, Coda provides great automation and integration abilities, but not everything is shiny. Weak things Coda UI is too fluid. When you move the mouse, you see popups, highlights, new controls appearing everywhere. It just feels like it’s too easy to break something and you don’t feel in control. So many things are happening. It feels crazy. On the first sight, document-orientation is taken to extreme in Coda. However, it has serious unexpected limitations. Documents in Coda are not connected. Yes, you can have many Sections inside a single Document, but you will have hard time implementing Wiki for the company using Coda. List of Documents. Just a List. It is close to Google Docs. Coda is complex. demands high level of cognitive effort. Automation rules, Integration Packs, Formulas (especially formulas), Document concept — everything is hard. Very often you know that you can solve a problem and build a solution with Coda, but you just give up. Everything So yes, Coda is for creators. But. With Notion creation feels like a game, while with Code it feels like a war. More information: Coda is a next-generation spreadsheet designed to make Excel a thing of the past To turn docs into apps, Coda had to rethink productivity from scratch Conclusion Paradigm shift in work management software market is happening. The change is driven by flexibility, unification and automation. People demands fewer well-integrated tools. My personal ranking of new wave work management software is this: Top tier: and Notion Airtable Second tier: Coda Outsider: Zenkit Summary table is always good to have: This table compares tools by main drivers (created in Airtable). We are creating . what it means 🦋. Fibery — process agnostic work management platform Go see

The Next Wave of Work Management Software

and its ecosystem are awesome and makes using it a pleasure. If you are writing a javascript application today I can’t stress enough how much simpler these two technologies will make that process. GraphQL Apollo A has recently and released there own mechanism to help you store local state in their cache. I’m really excited about this move and believe that this will further simplify the process of frontend development. However it does add complexity in the fact that there not many resources or third party library support out there for yet. This tutorial aims to help change that. 😀 pollo moved away from Redux apollo-link-state By the end of this tutorial you will have: Setup a React project using create-react-app Used to store and query for information apollo-link-state Written some stateless components with help from recompose Special thanks to Peggy Rayzis and the Apollo team for all the awesome work and communication that has been going out around this product. See her Future of State Management post to see what initially brought we over to this technology Getting Setup Before you start Please make sure you have the following installed and/or ready to go: Node Npm Yarn Initialize the project First before we can dive into Apollo we need a React App to use it with so lets create a React project called using . link_state_demo create-react-app # Download Create React Appyarn global add create-react-app # Use it to create a React Projectcreate-react-app # Navigate to the projectcd link_state_demo Add Additional Dependencies Next we want to add , , and among other supporting libraries. apollo apollo-link-state recompose lodash yarn add apollo-boost apollo-link-state react-apollo graphql-tag graphql lodash apollo-client-preset recompose Kick it off! It’s that simple, now we can just start our dev server and go! yarn start You should now be able to navigate to _localhost:3000_ and see your application running. create-react-app running out of the box Modify App.js to be Stateless Optional! I prefer to write my components using React’s stateless components because I It helps to simplify my code by: believe Reducing boilerplate Increasing Readability Discouraging lifecycle methods Encouraging a healthy separation between UI and Application Logic Though these are opinions and not required for using this demo! To change over to using stateless components is as easy as copying the code below to your file: app.js Setup the Apollo Client To begin we will have to set up our Apollo client. This is fairly simple and will involve the modification of one existing file and the creation on another. Setup the ApolloProvider Open and wrap in Apollo’s . index.js <App/> ApolloProvider Setup the ApolloClient Create a new file named and initialize the cache and the Client.js ApolloClient Setup State logic that will support a To-Do List (A To-Do List Demo! How Original!) Now that we have the Apollo Client setup it’s time to begin adding the methods, queries and components that will allow us store and modify local state in the Apollo Cache. Add apollo-link-state to Client.js Below you’ll find an updated which fully implements all the necessary tools to use to handle Todo list state. However before you dive into it you should understand what the sections do: Client.js apollo-link-state Defaults The default values that our local cache falls back to when the application loads. GraphQL This section houses the GraphQL queries which are used in the following ways: Finding data from the cache Finding where to insert data into the cache There are a few differences to pay attention to: The **_@client_** decorator This is what tells Apollo that these queries target the local cache. Query vs Mutation The keyword in the context does exactly what you expect, it looks for the data in the cache and returns it. query @client However the keyword tells us that it needs to modify something in the cache. To do this the mutation looks for an identically named function in the resolvers object we pass into which we define further down. mutation CreateClientStore Cache Mutations These are the functions that are called by our mutation queries. They are given the parameters sent to the query and an instance of the cache with the intention that we use these to update the state held inside. Store This is where we tie together our cache, client state, defaults, resolvers and the Apollo Client to give the ApolloProvider the ability to store state using . apollo-link-state Helpers Here we’ve created a Higher Order Component to help give a child component access to the functions needed to interact with the state mechanism we’ve just setup. What this all looks like Setup the TodoList Component Next we need to actually use the queries we defined above. To do this we are going to create a basic To Do List that lets us add items to a list and clear the list. Create TodoList.js Add TodoList to our App We then just need to add the to our container and it should be good to go. TodoList App What it should look like Navigating back to you should see: localhost:3000 And thats it! You’re now storing state locally using apollo-link-state Wrap up Simple solutions and simple architectures lead to a better and more stable systems in the long run. While GraphQL has helped to simplify query logic the Apollo Team has been doing an equal amount of work to simplify the rest. Because of this I’m happy to include these two technologies where ever I can. In this specific case has proved to be a valid alternative to Redux and has saved me from: apollo-link-state Adding another technology and paradigm Splitting my state into multiple locations Adding more that one method to get application state. The only caveat so far is that Link State lacks some tooling and third party library support that the Redux community enjoys, but I believe that is a very small and very temporary issue. Coming up next We dive into how to set up for success when handling additional stores. apollo-link-state N _Overview_medium.com Setting up apollo-link-state for Multiple Stores This is open source! you can 🧞‍ find it here on Github ❤️ I only write about programming and remote work. If you I won’t waste your time. follow me on Twitter

Storing Local State in React with apollo-link-state

How to Speed up Your Angular App With Web Workers

ওয়েব ওয়ার্কারদের সাথে আপনার কৌণিক অ্যাপের গতি বাড়ানোর উপায়

So beschleunigen Sie Ihre Angular-App mit Web Workern

Cómo acelerar su aplicación Angular con Web Workers

Comment accélérer votre application angulaire avec les Web Workers

वेब वर्कर्स के साथ अपने एंगुलर ऐप की गति कैसे बढ़ाएं

Web Workers で Angular アプリを高速化する方法

Web Worker를 사용하여 Angular 앱 속도를 높이는 방법

Como acelerar seu aplicativo Angular com Web Workers

Как ускорить ваше приложение Angular с помощью веб-воркеров

Angular Uygulamanızı Web Çalışanlarıyla Nasıl Hızlandırabilirsiniz?

Cách tăng tốc ứng dụng góc của bạn với nhân viên web

如何使用 Web Workers 加速你的 Angular 应用

Let's be honest, what other use is there for generative AI than working with cats? If you read my on Google's Gemini AI launch, you may have seen my test prompts asking it to identify the kind of cat shown in a picture. previous post I decided to turn this into a proper web application as a real example of the API in action. Here's what I came up with. The Front End For the front end, I decided to make use of a native web platform feature to access the user's camera via a simple HTML form field. By using on an tag, you directly get access to the device camera. capture="camera" input There are more advanced ways of doing this, but for quick and simple, it works fine. Even better, on a desktop, it simply acts as a file selector. My thinking was - to provide a way to get an image (either via camera or file selection), display the image, and send it off to the back end. While incredibly simple and vanilla JS would have been fine, I went ahead and used for the interactivity. Alpine.js First, the HTML needs to provide the UI for the image, a place to display the image, and another place to display the result. <!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<link rel="stylesheet" href="app.css">
	<title></title>
</head>
<body>

<h2>🐈 Detector</h2>
<div x-data="catDetector">
	<input type="file" capture="camera" accept="image/*" @change="gotPic" :disabled="working">
	<template x-if="imageSrc">
		<p>
		<img :src="imageSrc">
		</p>
	</template>
	<div x-html="status"></div>
</div>


<script defer src="https://unpkg.com/alpinejs@3.x.x/dist/cdn.min.js"></script>
<script src="app.js"></script>
</body>
</html> Now, let's turn to JavaScript. I'm going to begin by sharing the initial version as it's simpler than explaining how it failed. All I needed to do, initially, was notice when a file was selected, or a picture taken, and render it out to the DOM. (I used a bit of CSS not shared here to keep the visible size in check. More on that in a bit.) I also needed to send a base64 version of the file to the server-side code. Here's the initial version: //const IMG_FUNC = 'http://localhost:8787/';
const IMG_FUNC = 'https://catdetector.raymondcamden.workers.dev';

document.addEventListener('alpine:init', () => {
  Alpine.data('catDetector', () => ({
	imageSrc:null,
	working:false,
	status:'',
    async init() {
		console.log('init');
    },
	async gotPic(e) {
		let file = e.target.files[0];
		if(!file) return;
		
		let reader = new FileReader();
		reader.readAsDataURL(file);
		reader.onload = async e => {
			this.imageSrc = e.target.result;
			this.working = true;
			this.status = '<i>Sending image data to Google Gemini...</i>';

			let body = {
				imgdata:this.imageSrc
			}

			let resp = await fetch(IMG_FUNC, {
				method:'POST', 
				body: JSON.stringify(body)
			});

			let result = await resp.json();
			this.working = false;
			this.status = result.text;

		}

	}
  }))
}); The method is fired whenever the field fires an event. I take the file/image used, read it as a data URL (base64), and then assign it to the image in the DOM and send it to the server. Nice and simple, right? gotPic input onchange Well, everything worked fine on the desktop, but when I switched to my camera, the Samsung S22 Ultra Magnus Extreme 200 Camera Lens Edition (not the real name), I ran into issues where Google's API complained that I was sending too much data. I then remembered that my camera takes detailed pictures, and I needed to resize the image before sending it on. really I was already resizing in CSS, but obviously, that's not the same as resizing. I found this excellent article on ImageKit's site: In this article, they describe using an HTML element to do the resizing. really How to resize images in Javascript? canvas I had not used Canvas in probably close to a decade, but I was able to repurpose their code into my front end well enough: //const IMG_FUNC = 'http://localhost:8787/';
const IMG_FUNC = 'https://catdetector.raymondcamden.workers.dev';

// Resize logic: https://imagekit.io/blog/how-to-resize-image-in-javascript/
const MAX_WIDTH = 400;
const MAX_HEIGHT = 400;

document.addEventListener('alpine:init', () => {
  Alpine.data('catDetector', () => ({
	imageSrc:null,
	working:false,
	status:'',
    async init() {
		console.log('init');
    },
	async gotPic(e) {

		let file = e.target.files[0];
		if(!file) return;
		
		let reader = new FileReader();
		reader.readAsDataURL(file);
		reader.onload = async e => {
			let img = document.createElement('img');
			img.onload = async e => {
				let width = img.width;
				let height = img.height;

				if(width > height) {
					if(width > MAX_WIDTH) {
						height = height * (MAX_WIDTH / width);
						width = MAX_WIDTH;
					}
				} else {
					if (height > MAX_HEIGHT) {
						width = width * (MAX_HEIGHT / height);
						height = MAX_HEIGHT;
					}
				}

				let canvas = document.createElement('canvas');
				canvas.width = width;
				canvas.height = height;
				let ctx = canvas.getContext('2d');
				ctx.drawImage(img, 0, 0, width, height);

				this.imageSrc = canvas.toDataURL(file.type);

				this.working = true;
				this.status = '<i>Sending image data to Google Gemini...</i>';

				let body = {
					imgdata:this.imageSrc
				}

				let resp = await fetch(IMG_FUNC, {
					method:'POST', 
					body: JSON.stringify(body)
				});

				let result = await resp.json();
				this.working = false;
				this.status = result.text;

			};
			img.src = e.target.result;

		}

	}
  }))
}); You'll notice the code uses a max dimension for both width and height and correctly handles resizing while keeping the same aspect ratio. Again, I can't take credit for any of that, thanks to for his blog post. Manu Chaudhary The net result of this change is that now I'm sending a much smaller image to the back end service, and it's finally time to take a look at that. The Back End For my back end, I decided to use again. I was a bit hesitant as it's had some issues with NPM packages and my demos before, but it didn't have any issues this time. If you remember from my , Google's AI Studio lets you easily output sample code from your prompts, so all I had to do was incorporate that into the Cloudflare Worker. Cloudflare Workers last post Here's the entirety of the code: const {
  GoogleGenerativeAI,
  HarmCategory,
  HarmBlockThreshold,
} = require("@google/generative-ai");

const MODEL_NAME = "gemini-pro-vision";


export default {
	async fetch(request, env, ctx) {

		const API_KEY = env.GEMINI_KEY;

		console.log('begin serverless logic');

		const corsHeaders = {
			"Access-Control-Allow-Origin": "*",
			"Access-Control-Allow-Methods": "GET,HEAD,POST,OPTIONS",
			"Access-Control-Max-Age": "86400",
	    };

		let { imgdata } = await request.json();
		imgdata = imgdata.replace(/data:.*?;base64,/, '');

		const genAI = new GoogleGenerativeAI(API_KEY);
		const model = genAI.getGenerativeModel({ model: MODEL_NAME });

		const generationConfig = {
			temperature: 0.4,
			topK: 32,
			topP: 1,
			maxOutputTokens: 4096,
		};

		const safetySettings = [
			{
			category: HarmCategory.HARM_CATEGORY_HARASSMENT,
			threshold: HarmBlockThreshold.BLOCK_MEDIUM_AND_ABOVE,
			},
			{
			category: HarmCategory.HARM_CATEGORY_HATE_SPEECH,
			threshold: HarmBlockThreshold.BLOCK_MEDIUM_AND_ABOVE,
			},
			{
			category: HarmCategory.HARM_CATEGORY_SEXUALLY_EXPLICIT,
			threshold: HarmBlockThreshold.BLOCK_MEDIUM_AND_ABOVE,
			},
			{
			category: HarmCategory.HARM_CATEGORY_DANGEROUS_CONTENT,
			threshold: HarmBlockThreshold.BLOCK_MEDIUM_AND_ABOVE,
			},
		];

		const parts = [
			{text: "Look at this picture and if you see a cat, return the breed of the cat."},
			{
			inlineData: {
				mimeType: "image/jpeg",
				data: imgdata
			}
			}			
		];

		console.log('calling google');
		const result = await model.generateContent({
			contents: [{ role: "user", parts }],
			generationConfig,
			safetySettings,
		});

		const response = result.response;
		let finalResult = { text: response.text() };

		return new Response(JSON.stringify(finalResult), { headers: {...corsHeaders}});

	},
}; The majority of the code is boilerplate from the AI Studio export, except now, I get my image data from the information POSTed to the worker. I want to especially call out the prompt: Look at this picture and if you see a cat, return the breed of the cat. Initially, I tried hard to get a result in JSON and have it return a blank string if the picture wasn't a cat. But then I noticed something cool - Gemini did a good job of handling pictures that weren't of cats. Like... shockingly good. really I actually really appreciated that the app wouldn't just say "Not a Cat", but explained what it was instead. Obviously, there's room for both styles for an application like this, but I went and kept Google's verbose and helpful responses. Now, for the fun part... the results. The Results Let's start with a few pictures of cats. First up is Pig, my favorite cat who is not fat and doesn't look like Jabba the Hut at all: Next, a picture of Luna. In this case, the breed is incorrect - but at least close. Now, let's throw Google a curveball: This surprised me. The description is 100% accurate, and honestly, if I had seen this picture and didn't know, I would have recognized it as a sculpture of a cat, not as a watering can. I mean, I guess it's of obvious, but I honestly don't think I would have noticed that myself. really kind Now, let's go totally crazy: Yep, that's right Google. How about AI-generated cat images? I think it handled that pretty well. Next... Yep, that's Bigfoot alright. Just think, all those Bigfoot "researchers" could retire and simply connect their trail cams to AI! I've got to say - I'm impressed Google not only recognized the franchise but the actual character as well, but to be fair, Skeletor has a pretty distinct look to him. And finally, since I (unfairly of course) compared my cat to Jabba, let's see how it's handled: Oh, I know I said I was done, but of course, I had to test a dog: Dang good job, Gemini. Unfortunately, I won't be hosting this demo live (the Cloudflare 'live' URL earlier in the code won't work), but I can share the code.

I Used Generative AI to Detect Cat Breeds: Here's How It Went

আমি বিড়ালের জাত সনাক্ত করতে জেনারেটিভ এআই ব্যবহার করেছি: এটি কীভাবে হয়েছিল তা এখানে

Ich habe generative KI verwendet, um Katzenrassen zu erkennen: So lief es

Utilicé IA generativa para detectar razas de gatos: así fue como fue

J'ai utilisé l'IA générative pour détecter les races de chats : voici comment cela s'est passé

मैंने बिल्ली की नस्लों का पता लगाने के लिए जेनरेटिव एआई का उपयोग किया: यहां बताया गया है कि यह कैसे हुआ

生成 AI を使用して猫の品種を検出してみた: その様子は次のとおりです

고양이 품종을 감지하기 위해 생성 AI를 사용했습니다. 진행 과정은 다음과 같습니다.

Usei IA generativa para detectar raças de gatos: foi assim que aconteceu

Я использовал генеративный искусственный интеллект для определения пород кошек: вот как все прошло

Kedi Irklarını Tespit Etmek İçin Üretken Yapay Zeka Kullandım: İşte Nasıl Oldu

Tôi đã sử dụng AI sáng tạo để phát hiện các giống mèo: Đây là cách nó diễn ra

我使用生成式人工智能来检测猫的品种：它是这样的

In this article, I will show you how you can write a lambda function that can convert JSON data into a .xlsx file using nodeJS and typescript. This function is built using serverless framework. You can find more about there here - https://www.serverless.com/ Install serverless globally npm install -g serverless Create a typescript template project mkdir json-to-xlsx
cd json-to-xlsx
serverless create --template aws-nodejs-typescript Install required npm packages npm install --save exceljs @types/exceljs serverless-offline aws-sdk for creating a spreadsheet excelJS for running lambda function locally serverless-offline from interacting with AWS services aws-sdk Define serverless function and add offline package to serverless.ts import type { AWS } from '@serverless/typescript';

const serverlessConfiguration: AWS = {
  service: 'jsontoxlsx',
  frameworkVersion: '2',
  custom: {
    webpack: {
      webpackConfig: './webpack.config.js',
      includeModules: true
    },
    
    //'${ssm:/jsontoxlsx/api/BUCKET_NAME}' ssm is not supported yet, I have 
    //raised an issue here - https://github.com/serverless/typescript/issues/59. 
    //Once this is fixed, we don't have to hardcode bucket names on this file 
    //and can be access from AWS system manager's parameter store

    AWS_BUCKET_NAME: 'Your bucket name'

  },
  // Add the serverless-webpack plugin
  plugins: ['serverless-webpack', 'serverless-offline'],
  provider: {
    name: 'aws',
    runtime: 'nodejs14.x',
    apiGateway: {
      minimumCompressionSize: 1024,
    },
    environment: {
      AWS_NODEJS_CONNECTION_REUSE_ENABLED: '1',
      AWS_BUCKET_NAME: '${self:custom.AWS_BUCKET_NAME}'
    },
  },
  functions: {
    jsontoxlsx: {
      handler: 'handler.jsontoxlsx',
      events: [
        {
          http: {
            method: 'get',
            path: 'jsontoxlsx',
          }
        }
      ]
    }
  }
}

module.exports = serverlessConfiguration; Convert JSON data into excel format using excel node package async function saveDataAsExcel(sample: ingredients[]) {
  const workbook:excel = new excel({ headerRowFillColor: '046917', defaultFillColor: 'FFFFFF' });
  let worksheet = await workbook.addWorkSheet({ title: 'Scrapped data' });
  workbook.addHeaderRow(worksheet, [
    "ID",
    "Type",
    "Name",
    "PPU",
    "Batter ID",
    "Batter Name",
    "Topping ID",
    "Topping Name"
  ]);

   for (let ingredient of sample) {
    workbook.addRow(
      worksheet,
      [
        ingredient.id.toString(),
        ingredient.type,
        ingredient.name,
        ingredient.ppu.toString()
      ],
      { bold: false, fillColor: "ffffff" }
    );
  
     let size:number = ingredient.batters.length > ingredient.toppings.length ? ingredient.batters.length : ingredient.toppings.length;  
     
     for (let i = 0; i < size; i++)  {
      workbook.addRow(
        worksheet,
        [
          '', '', '', '',
          ingredient.batters[i]?.id.toString(),
          ingredient.batters[i]?.type,
          ingredient.toppings[i]?.id.toString(),
          ingredient.toppings[i]?.type
        ],
        { bold: false, fillColor: "ffffff" }
      );
    }
  }

  return workbook; 
} Excel class implementation import * as ExcelJS from "exceljs";

export interface worksheetOptions {
    title: string;
}

export interface rowOptions {
    fillColor: string;
    bold: boolean;
}

export interface workBookOptions{
    headerRowFillColor: string;
    defaultFillColor: string;
}

export class excel {
    
  workbook: ExcelJS.Workbook;
  defaultFillColor: string;
  headerRowFillColor: string;

  constructor(options: workBookOptions) {
    this.workbook = new ExcelJS.Workbook();
    this.workbook.created = new Date();
    this.workbook.modified = new Date();
    this.headerRowFillColor = options.headerRowFillColor || "FFF242";
    this.defaultFillColor = options.defaultFillColor || "FFFFFF";
  }

  async addWorkSheet(options: worksheetOptions) {
    return this.workbook.addWorksheet(options.title, {
      pageSetup: {
        horizontalCentered: true,
        verticalCentered: true,
        margins: {
          left: 2,
          right: 2,
          top: 4,
          bottom: 4,
          header: 2,
          footer: 2,
        },
      }
    });
  }

  async addHeaderRow(
    worksheet: ExcelJS.Worksheet,
    headerRowData: Array<string>
  ) {
    worksheet.addRow(headerRowData.map(row => row));
    worksheet.getRow(1).fill = {
      type: "pattern",
      pattern: "solid",
      fgColor: { argb: this.headerRowFillColor },
    };
    worksheet.getRow(1).font = { size: 12, bold: true, name: 'Arial', family:2, color: {argb: 'FFFFFF', theme: 2} };
    worksheet.getRow(1).border = {
      top:    { style: "thin", color: { argb: "E8E8E8"} },
      bottom: { style: "thin" ,color: { argb: "E8E8E8"} },
      left:   { style: "thin" ,color: { argb: "E8E8E8"} },
      right:  { style: "thin" ,color: { argb: "E8E8E8"} },
    };
  }

  async addRow(
    worksheet: ExcelJS.Worksheet,
    data: Array<string>,
    options: rowOptions
  ) {
    worksheet.addRow(data);
    worksheet.getRow(worksheet.rowCount).font = {
      size: 13,
      bold: options.bold || false,
    };
    worksheet.getRow(worksheet.rowCount).fill = {
      type: "pattern",
      pattern: "solid",
      fgColor: { argb: options.fillColor || this.defaultFillColor },
    };
    worksheet.getRow(worksheet.rowCount).alignment = {
      vertical: "bottom",
      horizontal: "left",
    };
    worksheet.getRow(worksheet.rowCount).border = {
      top:    { style: "thin", color: { argb: "E8E8E8" } },
      bottom: { style: "thin", color: { argb: "E8E8E8" } },
      left:   { style: "thin", color: { argb: "E8E8E8" } },
      right:  { style: "thin", color: { argb: "E8E8E8" } },
    };

    this.adjustColumnWidth(worksheet);
  }

  async adjustColumnWidth(worksheet: ExcelJS.Worksheet) {
    worksheet.columns.forEach( column => {
      var dataMax = 0;
      column.eachCell({ includeEmpty: true }, cell => {
        dataMax = cell.value ? cell.value.toString().length : 0;
      });
      column.width = dataMax < 15 ? 15 : dataMax;
    });
  }
} Upload excel sheet to s3 await uploadToS3({
      Bucket: process.env.AWS_BUCKET_NAME,
      Key: `${objectKey}.xlsx`,
      ContentType:
        'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet',
      Body: await excelSheet.workbook.xlsx.writeBuffer()
    });
    
    //Get signed url with an expiry date
    let downloadURL = await getS3SignedUrl({
      Bucket: process.env.AWS_BUCKET_NAME,
      Key: `${objectKey}.xlsx`,
      Expires: 3600 //this is 60 minutes, change as per your requirements
    });

    return okResponse({
      message: 'JSON to XLSX is complete, you can download your file now',
      downloadURL
    }) AWS Wrapper functions - Note: You will need to have your and in your environment AWS access keys AWS secret import { S3 } from "aws-sdk";

const s3 = new S3({
  accessKeyId: process.env.AWS_ACCESS_KEY,
  secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY,
});

export async function uploadToS3(s3Data: S3.PutObjectRequest) {
    console.info(
      "---- UPLODAING TO S3",
      JSON.stringify(`${s3Data.Bucket} ${s3Data.Key}`, null, 2)
    );
  
    try {
      return await s3.upload(s3Data).promise();
    } catch (error) {
      console.log(error);
      return error;
    }
}


export async function getS3SignedUrl(params: any): Promise<any> {
    console.info(
      "---- GETTING SIGNED URL FROM S3",
      JSON.stringify(params, null, 2)
    );
    try {
      return s3.getSignedUrl("getObject", {
        Bucket: params.Bucket,
        Key: params.Key,
        Expires: params.Expires,
      });
    } catch (error) {
      console.log(error);
      throw error;
    }
} Test locally sls offline --stage local Deploy to AWS sls deploy --stage dev You can clone this to see a working example - repo git clone https://github.com/appletreeat56/json-to-xlsx.git

The Lambda Function That Creates xlsx Files From JSON Data to Store On S3 Using NodeJS/Typescript

The followings are the steps to integrate Socket.io in Chrome extension. We wanted to allow message passing in our Chrome application, and socket.io is the best option to do so. Chrome extension doesn’t allow its native socket connection due to security issues. But we can achieve this via JavaScript socket connection. On the server side, we have used Node JS. The following is the architecture of Node JS, Chrome extension, and Socket.io integration. SERVER SIDE CODE (NODE JS) Step 1: In your express application, add socket.io via installing socket.io npm install socket.io Step 2: Now add this dependency in your app. js file. var express = require('express');
var app = express();

// Socket connection

/* Creates new HTTP server for socket */
var socketServer = require('http').createServer(app);
var io = require('socket.io')(socketServer);

/* Listen for socket connection on port 3002 */
socketServer.listen(3002, function(){
  console.log('Socket server listening on : 3002');
});

/* This event will emit when client connects to the socket server */
io.on('connection', function(socket){
  console.log('Socket connection established');
});

/* Create HTTP server for node application */
var server = http.createServer(app);

/* Node application will be running on 3000 port */
server.listen(3000); CLIENT SIDE CODE Step 1: In your chrome extension add socket.io.js in your index.html you can find it on: https://cdnjs.cloudflare.com/ajax/libs/socket.io/1.7.3/socket.io.js Step 2: Now add the following script in your js file where you want to establish your connection. /* Connects to the socket server */
var socket = io.connect('http://localhost:3002');
socket.on('connect', function() {
  console.log('Client connected');
}); Hope Shared code would be helpful. For Facebook, Google and Slack integration stay tune. We will be back soon. Follow us on @thirdrocktechkno on twitter and on Facebook. fb.com/ThirdRockTechkno Do share your feedback. :)

Node JS + Socket.IO + Chrome Extension Integration

is a regular time to take a look at what experienced industry experts think might be the next wave of tools, practices, and technologies to consider or stop using. Thoughtworks’ Technology Radar I always look forward to adding many new “blips” to my list, or seeing which are growing in adoption since you last took a look. Version 27 is out now, and it continues some trends that the radar has been following for a while, such as “platform as a service” or forms of group programming. This round-up is far from comprehensive, but just the blips that appealed to me or that, I thought, might appeal to you. If any of them take your interest, or you have an opinion on anything I’ve featured, ! head over to your profile and let our readers know Mainstreaming of Machine Learning It really does feel like that in the past 6 months or so, machine learning went from something that mostly only developers and data scientists interacted with to something that the public had awareness of. There was announcement after announcement of another ML or AI-based tool that spat out some sort of media after you fed something into it, and we were swamped with thousands of strange-looking images and videos of celebrities. This also means that developers interested in experimenting with ML also have a lot more resources available to them in the shape of data sets and frameworks to use those data sets. Of relevance to experimenting developers is , a field of machine learning enabling a variety of always-on use-cases and targeting battery-operated devices. TinyML Another is , a method for creating ML pipelines that might be more familiar to developers from other backgrounds. feature stores This radar also covered ML-related tools for improving the developer experience of building and training models, for example, the practice of “federated machine learning” for aggregating model data across machines for processing or synthetic data for initial model testing. Continuous Observability Despite being a relatively new term, “observability” has rapidly grown from a loose collection of practices and standards for building a better picture of a running system to become a broader term to mean, well, to mean all sorts of things. The latest area of the developer workflow to receive insights is one that I am surprised took so long, observability for continuous integration and delivery pipelines. While CI and CD certainly bring benefits, processes frequently go wrong with very little insight into what until you try, try again. Now, a handful of existing observability vendors and open-source projects are bringing tracing-style visualizations of continuous processes to hopefully help you debug quite what was going on. Software Bill of Materials As developers lean increasingly on semi-anonymous containers and packages for their work, those focused on security and legalities looked on and wondered, “do we trust this?”. This concern has led to a rush to standardize and normalize (in enterprise, especially) a “software bill of materials”, often referred to by the comical acronym, SBOMs. While, in theory, “anyone” can dig into an open-source project and see what its components are, this is generally easier said than done and isn’t possible with closed-source projects at all. Recent high-profile vulnerabilities in software revealed how small dependencies can bring such large problems. While SBOMs could go a long way to help, I wonder how many companies will want to reveal their inner workings and be honest about them. Sustainable Coding This is a topic that I was inspired to cover myself after speaking with someone from Thoughtworks about their Carbon cloud footprint tool. The tendency to endlessly throw new frameworks, tools, and cloud frameworks at a problem has led to many of us forgetting that all of these lines of code actually run somewhere on something. And that leads to carbon emissions. Water motivated by altruistic reasons or financial, and an ecumenic downturn leads to cost savings, this is a topic more are talking and thinking about. Closely related to the environmental cost of projects and their infrastructure, and an option I’ve seen used by production teams is which estimates the cost impact of changes you make to Terraform definitions. infracost Responsibilities as Code Any SaaS company defines service-level indicators (SLIs) and service-level objectives (SLOs) that their clients can expect. However, how companies defined these have often been a bit haphazard and non-standard, and with so much else defined in codified pipelines, why not this fundamental component too? Several Observability providers now offer this option and of course, a group of people started a standard, . OpenSLO A No to Node I dabble in JavaScript and TypeScript and have noticed a handful of emerging runtime alternatives to Node recently. I am not sure what is wrong with Node, aside from being fairly old now, to warrant alternatives, but I guess competition is good 🤷‍♂️? is one newer alternative that I tried a few months ago, and I’ll admit I wasn’t really sure what benefits it brought me, but it uses WebKit’s JavaScriptCore instead of Chrome’s V8 engine. Bun Again, variety isn’t a bad thing. Bun is written in , which I had never heard of before, and it claims to be a “drop-in” C/C++ replacement. Zig Which leads nicely to… C+++ If Zig, Rust, and other languages are anything to go by, numerous people feel that C++ needs a more modern replacement. Google has thrown another option into the list of contenders with . Carbon The language is still in experimental stages but claims to be easier to understand and onboard with. Google has a tendency to spin up many experimental projects and then dump them again, so Thoughtworks’ suggestion is currently “wait and see”.

Developer Trends from Thoughtworks’ Technology Radar 27

Tendencias de desarrolladores del Radar de tecnología de Thoughtworks 27

Tendances des développeurs du radar technologique de Thoughtworks 27

थॉटवर्क्स के टेक्नोलॉजी रडार 27 से डेवलपर रुझान

ソートワークスのテクノロジー レーダー 27 からの開発者トレンド

Tendências de desenvolvedores do Technology Radar 27 da Thoughtworks

Xu hướng dành cho nhà phát triển từ Radar công nghệ của Thoughtworks 27

Thoughtworks 技术雷达的开发者趋势 27

Stories, News & Mentions about THIRDWORK

Thirdwork’s Stories on HackerNoon