# Risk A measure of how extensively an entity is threatened by a potential circumstance or event, based on adverse impact and likelihood of occurrence. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## When the team plays, Pix pauses: what the World Cup teaches us about outliers DevFeed: [When the team plays, Pix pauses: what the World Cup teaches us about outliers]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-17T15:17:19Z Content type: article Language: en Sources: [Nubank]() Topics: [data](), [context](), [Transactions](), [Risk](), [reliability]() Tags: [ai-research](), [context](), [data](), [data-science-machine-learning](), [patterns](), [payment](), [transactions]() ### AI overview The article uses World Cup matches as an example of how coordinated changes in everyday behavior can create outliers in payment data. It explains that instant-transfer volume drops during a match, returns after the final whistle, and may show a halftime pattern, emphasizing that anomalies must be assessed against the normal rhythm of transactions and their context. ### Source excerpt How World Cup matches turn everyday payment patterns into outliers and what those anomalies can teach us about data, risk, and reliability The post When the team plays, Pix pauses: what the World Cup teaches us about outliers appeared first on Building Nubank. ## Match Software Quality Controls to Customer Impact and Technical Risk DevFeed: [Match Software Quality Controls to Customer Impact and Technical Risk]() Original publisher: [Read original article]() Author: Luca Rossi Published: 2026-09-07T07:03:38Z Content type: opinion Language: en Sources: [Refactoring]() Topics: [Risk](), [Software](), [Architecture & Design]() Tags: [essay](), [risk](), [software]() ### AI overview This commentary argues that software quality controls should reflect a change's customer impact and technical risk. It describes a maturity path from individual quality advocacy to team-wide principles and processes. ### Source excerpt Monday Ideas -- Edition #224 ## NFR Brain: challenging the status quo of risk management with data DevFeed: [NFR Brain: challenging the status quo of risk management with data]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-04T14:18:41Z Content type: opinion Language: en Sources: [Nubank]() Topics: [risk-management](), [data](), [Risk](), [Resilience]() Tags: [critical](), [data](), [data-analytics](), [data-modelling](), [data-science-machine-learning](), [governance](), [models](), [risk-management]() ### AI overview Nubank describes NFR Brain, a platform for combining data, modelling, and expert judgement to make non-financial risk signals comparable and actionable. The article presents it as a way to support more consistent, transparent risk prioritization in business decisions without automating judgement. ### Source excerpt Author : Mayara Zenati At Nubank, we believe the most meaningful problems for customers and for the business rarely come with ready-made answers. That is why we challenge the status quo: not to innovate for innovation's sake, but to remove complexity and build solutions that make important decisions simpler, faster and better. This mindset also [...] The post NFR Brain: challenging the status quo of risk management with data appeared first on Building Nubank. ## A Model for Understanding AI Success in Organizations DevFeed: [A Model for Understanding AI Success in Organizations]() Original publisher: [Read original article]() Author: John Cutler Published: 2026-07-19T15:21:27Z Content type: opinion Language: en Sources: [The Beautiful Mess]() Topics: [Artificial Intelligence](), [context](), [domain](), [iteration](), [Risk]() Tags: [ai](), [context](), [domain](), [iteration](), [risk]() ### AI overview The article presents a multiplicative model for AI success based on technology understanding, problem understanding, practice evolution, and an organizational social contract. It argues that missing any essential factor can undermine the outcome, while resistance to AI mandates may reflect rational self-preservation and insufficient evidence. ### Source excerpt Here's a simple model for thinking about AI success in organizations. ## NCMC design and technical limitations DevFeed: [NCMC design and technical limitations]() Original publisher: [Read original article]() Published: 2026-01-03T18:46:00Z Content type: opinion Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [Internet](), [Transactions](), [Risk](), [systems]() Tags: [card](), [dmrc](), [internet](), [ncmc](), [npci](), [payment-systems](), [payments]() ### AI overview The article examines India's National Common Mobility Card (NCMC), focusing on its offline-wallet design and how it differs from online UPI and card payments used in other transit systems. ### Source excerpt I was in Mumbai a few months ago for the Equinix India Peering forum. The event happened to be very near the airport & I found that the airport, conference venue, hotel, and a few other locations I was visiting were all near the newly built Mumbai Line 3 (Aqua Line). To save on hassle with regular tickets, I went for an NCMC (National Common Mobility Card). Most people travelling in the Delhi metro would be aware of it by now, thanks to a bit of marketing push inside the metro train with announcements. Mumbai line 3 has a tie-up with SBI for the card, and thus, I got the SBI card. Ended up using it in Mumbai, Delhi and Chennai over the last few months. Lately, I have been reading about way NCMC works, the limitations of the Indian NCMC design compared to other mass transit systems. In many countries, mass transit systems simply use MasterCard/Visa/Apple Pay tap and charge directly from the respective card (credit/debit card, etc.), like the London tube, Stockholm metro, HK airport express, Singapore, etc. Indian deployment is bit different. Indian NCMC offline wallet concept The whole idea of NCMC is to have a single card which can make payment for public transport, including metro, buses etc across the country digitally. It has to be fast and reliable, and this is where the whole tech differs from systems like UPI or Visa/MasterCard/Rupay POS payments. In case of UPI as well as credit/debit card payments on POS machines - entire transaction runs online. Money goes from the person paying the amount to the receiver as part of a settlement facilitated by NPCI. I don't need to go in detailed steps involved there, but the key idea is that there's an active involvement of 1) Payer's APP 2) Payer's bank 3) Receiver's PSP 4) Receiver's bank 5) NPCI UPI switch, etc. All these have to work and most important - internet has to work. 😀 All this largely works well for casual payments across the vendors, but not for transit payments, especially at metro stations. It easily takes ## Introducing our new QR Friend app DevFeed: [Introducing our new QR Friend app]() Original publisher: [Read original article]() Author: Sérgio Published: 2024-10-17T16:33:21Z Content type: release Language: en Sources: [Blog - Bloco]() Topics: [QR Code](), [App](), [Android](), [Google Play](), [Risk]() Tags: [android](), [app](), [dark-mode](), [google-play](), [projects](), [qr-code](), [risk]() ### AI overview Bloco released QR Friend, an Android app for scanning QR codes without ads or accounts. It supports WiFi, contact, GPS location, and barcode scans, with scan history, favorites, optional premium features, and link safety checks using Google's Web Risk service. ### Source excerpt We released a new app for scanning QR codes: QR Friend. ## Developer Experience at Risk: Red Flags for Engineering Leaders DevFeed: [Developer Experience at Risk: Red Flags for Engineering Leaders]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-06-17T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [devex](), [Developer experience](), [Risk](), [Tech Lead]() Tags: [culture-developer-experience-developer-productivity-engineering-excellence](), [developer-experience](), [devex](), [risk](), [tech-lead](), [tooling]() ### AI overview The article identifies warning signs that engineering leaders may be neglecting developer experience, focusing on engineers' behavior and coping strategies. It discusses job crafting and the risk that excessive work outside assigned roles can delay product evolution and create delivery pressure. ### Source excerpt Developer Experience at Risk: Red Flags for Engineering Leaders Developer Experience is the most important driver behind productivity, engagement, and job satisfaction. Therefore, improving the perceived experience of their engineers should be the top priority for engineering leaders at all levels. ## Is "Not deploying on Fridays" an outdated practice? DevFeed: [Is "Not deploying on Fridays" an outdated practice?]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2022-07-09T13:25:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Deployment](), [Development](), [Software Engineering](), [Risk]() Tags: [changes](), [continuous-deployment-culture-practices-developer-productivity-engineering-excellence-software](), [deployment](), [development](), [risk]() ### AI overview The article argues that avoiding Friday deployments is an outdated practice for teams using continuous deployments, feature toggles, and instant rollbacks. Small, frequent deployments reduce the risk and effort of fixing problems, while postponing releases can create larger batch deployments on Monday. ### Source excerpt Is "Not deploying on Fridays" an outdated practice? Every person working in a field somehow related to software development probably has heard the term "Don't deploy on Fridays". For years, I considered this as a wise recommendation. ## Managing Employees During the Invasion of Ukraine DevFeed: [Managing Employees During the Invasion of Ukraine]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2022-02-25T10:32:45Z Content type: opinion Language: en Sources: [Pedro Gil Carvalho]() Topics: [Support](), [Risk]() Tags: [berlin](), [company](), [employees](), [money](), [support](), [ukraine]() ### AI overview The article advises managers to support employees affected by the invasion of Ukraine, including by checking in, providing needed assistance, considering financial help and extraordinary time off, preventing hostility toward Russian employees, and adjusting expectations. ### Source excerpt A message for managers of people who are affected by the invasion of Ukraine by Russian forces ## Crucial developer practices: Decoupling deployments and releases DevFeed: [Crucial developer practices: Decoupling deployments and releases]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2021-11-27T12:02:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [feature flags](), [Deployment](), [releases](), [systems](), [Risk](), [Testing]() Tags: [continuous](), [continuous-deployment-software-development-software-craft](), [decoupling](), [deployments](), [developer](), [feature-flags](), [practices](), [risk](), [test](), [testing]() ### AI overview The article explains why growing systems should decouple deployments from releases. It focuses on release toggles, a type of transient feature flag that lets developers change application behavior at runtime, gradually roll out changes, roll them back, and test in production without breaking the system. ### Source excerpt Crucial developer practices: Decoupling deployments and releases When systems are small and the risk of introducing defects when changing its behaviour is low, these changes can happen during deployment. However, when systems grow, the behaviour becomes more complex and more people are working on the system, it is essential to decouple behaviour changes, the releases, from deployments. ## You can use SwiftUI today DevFeed: [You can use SwiftUI today]() Original publisher: [Read original article]() Published: 2020-01-04T02:50:00Z Content type: opinion Language: en Sources: [Rambo Codes]() Topics: [SwiftUI](), [iOS](), [Low-Code / Internal Tools](), [macOS](), [Risk]() Tags: [internal-tools](), [ios](), [macos](), [risk](), [swift](), [swiftui]() ### AI overview The author argues that using SwiftUI immediately for App Store production apps is risky because the technology is new, has rough edges, and may change significantly. They nevertheless recommend that iOS developers learn SwiftUI through substantial hands-on projects, including internal tools, rather than only tutorials or small test projects. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures. ## Equity Allocation in Startups DevFeed: [Equity Allocation in Startups]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-11-10T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Risk](), [RSS Feed]() Tags: [equity](), [funding](), [startup](), [startups](), [vp-of-engineering]() ### AI overview An opinionated guide to allocating startup equity, arguing that ownership should reflect the risk and timing of each contributor's involvement. It recommends reserving equity for an employee option plan, using options rather than stock, and applying a long vesting schedule. The author illustrates these points with personal experience from Feedster. ### Source excerpt Once upon a time, I was speaking with a company founder and they mentioned that they had a VP of Engineering to whom they have given a 1/3 stake in the company. I immediately commented that was too much and then said "I'll write this down in a blog post" - and then I never did. Last night, oddly, I woke up from a deep sleep with the desire to write this down. And that brings us to this post. Here's what I can remember from that conversation: Company Stage: Pre Funding Company Type: Medical Equity Split with the VP of Engineering: 1/3 Founder Title: Yes Did VP of Engineering Put in Cash: No You Need to Understand This One of the basic rules of the startup world is that on Day 1, you, the founder, own 100% of something that is worth absolutely nothing. The goal, by the end, is that you own a much smaller percentage of something actually worth something. As an example, owning 10% of something worth $10 million is actually much, much better. The Basic Rules of Thumb for Equity Allocations Here are my rules of thumb to use for equity allocation: The more risk you take, the more you get The earlier you join, the more you get Putting time in is one type of risk Putting cash in is a greater type of risk If you, the founder, give too much equity to someone else then you can be pushed out by simply having that other person align with the investor or investors You only have 80% of the equity to play with - 20% generally goes to an ESOP (employee stock option plan) Make damn sure that you give out options not stock and a long vesting schedule (incremental over say 4 years) The bottom line is that equity, in whatever form, is a reward for taking risk. And the earlier you are involved in a startup, the more risk there is. My Personal Experience from Feedster A long, long time ago, I founded a blog search engine named Feedster. I merged with another RSS search engine shortly after coming to market to address some technical limitations in my architecture. We did the typical nerd fo ## Talking to Technical People DevFeed: [Talking to Technical People]() Original publisher: [Read original article]() Published: 2017-07-07T18:35:35Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [Job](), [Risk](), [Website]() Tags: [business](), [job](), [risk](), [technical]() ### AI overview The article argues that communication with technical people should clearly state the desired outcome, constraints, timeline, and motivation instead of relying on hints or indirect stories. It also advises avoiding micromanagement while acknowledging that technical specialists may resist or misunderstand implicit instructions. ### Source excerpt (Don't) drop the hint: communicating with technical people This post is a subset of the presentation "Escaping the data center -- tales from a recovering manager". Video, slides. When we communicate at the office, we frequently do not directly say what we mean. A common conversation might go like this "Hey John, we did a survey and it turns out people can't find what they are looking for on our website". ## Why businesses need a longer-term focus than quarterly goals DevFeed: [Why businesses need a longer-term focus than quarterly goals]() Original publisher: [Read original article]() Author: Map Published: 2008-06-06T01:26:27Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Risk](), [ibm]() Tags: [business](), [ceo](), [company](), [employees](), [focus](), [growth](), [hiring](), [ibm](), [limits](), [risk]() ### AI overview The article argues that businesses often prioritize quarterly or yearly targets over long-term goals, leading to poorly timed hiring freezes and rushed recruitment. It contrasts this with smaller companies' more constrained spending decisions and questions whether private ownership enables a longer-term focus. ### Source excerpt Adobe's former CEO, Bruce Chizen, when asked 'What advice do you have for new/young public companies?', gave a response of 'Go private'. While partially a joke he went on to elaborate something that many businesses seem to miss on. The main idea is that businesses are very nearsighted in their focus, they look at quarterly goals and in some cases yearly, but not where they want to be in 10 years. When companies become worried that head count is high they simply freeze hiring across the board without thinking of its ramifications. Good people, well great people are truly hard to find, and when a company enforces a blanket hiring freeze they miss out on those few great people that they truly need to grow. Meanwhile when they decide they have bandwidth for 1000 new employees they open the flood gates and let the first 1000 that can spell their name correctly in, because they can. This short term focus in the long run greatly limits the ability of what a company can achieve. In contrast a smaller company that is actually much more at risk of dying seems to have a better understanding of what their approach should be. While they may be understaffed and overworked, they firmly understand that they only have so many funds and therefore make wiser decisions when using them. The characteristics of the larger business and their short sighted focus leads to the cyclical performance that many experience over a few years, rather than a very steady growth they would like to maintain, and often leads to their end. A prime example would be IBM that laid off so many of their more talented people to lower their numbers years ago. As a result they lost their best workers and had many unexperienced individuals in there when they began hiring again. They are still working to catch back up to where they once were in the IT industry... In part I wonder if being a private entity is really the only way to have the long term focus and not worry about quarterly earnings. Personally I have never ## How Public Online Complaints Are Changing Business Etiquette DevFeed: [How Public Online Complaints Are Changing Business Etiquette]() Original publisher: [Read original article]() Author: Map Published: 2008-06-02T13:16:31Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Publishing](), [Website](), [Users](), [Risk]() Tags: [publishing](), [rant](), [risk](), [users](), [web]() ### AI overview This opinion article argues that business etiquette is changing as employees and former employees increasingly publish complaints and workplace experiences online. It also notes that employers may examine applicants' social media profiles, blurring boundaries between personal and professional conduct. ### Source excerpt A recent conversation of someone that was offended when the were introduced to someone new, then was not greeted first since they were a female brought what follows to mind. The above is a train of thought that came from a 70 year old military wife. I do not believe this is common practice today and is quite rarely found as the common etiquette, but nonetheless I think what is proper etiquette in business is changing quite rapidly. Though I'm not sure if all of the older ideas and principles have gone away. I take as a first example zuckerburg, whom is a notoriously difficult interview. Not because he keeps things hidden, or is sealed tight about the company, but rather that his soft skills are not his strength. His strength is building a web product that millions of people find worthwhile to divulge hours of their day into it. Even two years ago when you were disgruntled with a company you may have gotten a few drinks in you and talked to a friend about your displeasure. But it certainly was not made fully public for anyone to see. At best you could only hope you were simply privy to things that would be brought to the publics eye from a larger misdoing either legally or that a mass-crowd found a problem with. But for simply being overworked, underpaid, or in some other odd way mistreated there was no politically correct outlet to speak through. However in the past years it has become extremely common for those that are still employed, or were employed to voice their complaints and bring to light the details that were once hidden. I think of Zed Shaw's rant on rails which calls out specific companies, or an older blog the diary of a mac genius, who gave detailed behind the scenes information of an apple customer support genius bar. While I'll concede for the mass majority if it's published it's doesn't mean its consumed, so it's not a dramatic effect on any single business, I still find it hard to believe that this overall shift of users freely publishing is not go