Speedoc

speedoc

Build Your Own RAG App: A Step-by-Step Guide to Setup LLM locally using Ollama, Python, and ChromaDB

আপনার নিজস্ব RAG অ্যাপ তৈরি করুন: Ollama, Python, এবং ChromaDB ব্যবহার করে স্থানীয়ভাবে LLM সেটআপ করার জন্য একটি ধাপে ধাপে নির্দেশিকা

Erstellen Sie Ihre eigene RAG-App: Eine Schritt-für-Schritt-Anleitung zum lokalen Einrichten von LLM mit Ollama, Python und ChromaDB

Cree su propia aplicación RAG: una guía paso a paso para configurar LLM localmente usando Ollama, Python y ChromaDB

Créez votre propre application RAG : un guide étape par étape pour configurer LLM localement à l'aide d'Ollama, Python et ChromaDB

अपना खुद का RAG ऐप बनाएं: ओलमा, पायथन और क्रोमाडीबी का उपयोग करके स्थानीय रूप से LLM सेटअप करने के लिए चरण-दर-चरण मार्गदर्शिका

独自の RAG アプリを構築する: Ollama、Python、ChromaDB を使用して LLM をローカルでセットアップするためのステップバイステップ ガイド

나만의 RAG 앱 구축: Ollama, Python 및 ChromaDB를 사용하여 로컬에서 LLM을 설정하는 단계별 가이드

Crie seu próprio aplicativo RAG: um guia passo a passo para configurar o LLM localmente usando Ollama, Python e ChromaDB

Создайте свое собственное приложение RAG: пошаговое руководство по локальной настройке LLM с использованием Ollama, Python и ChromaDB

Kendi RAG Uygulamanızı Oluşturun: Ollama, Python ve ChromaDB'yi kullanarak LLM'yi yerel olarak kurmak için Adım Adım Kılavuz

Xây dựng ứng dụng RAG của riêng bạn: Hướng dẫn từng bước để thiết lập LLM cục bộ bằng Ollama, Python và ChromaDB

构建自己的 RAG 应用程序：使用 Ollama、Python 和 ChromaDB 在本地设置 LLM 的分步指南

Driving Innovation: Patents and Projects Shaping the Automotive Industry

ড্রাইভিং ইনোভেশন: পেটেন্ট এবং প্রকল্পগুলি মোটরগাড়ি শিল্পকে আকার দেয়

Impulsando la innovación: patentes y proyectos que configuran la industria automotriz

Poticanje inovacija: patenti i projekti koji oblikuju automobilsku industriju

イノベーションの推進: 自動車産業を形成する特許とプロジェクト

ນະວັດຕະກໍາການຂັບລົດ: ສິດທິບັດ ແລະໂຄງການສ້າງອຸດສາຫະກໍາລົດຍົນ

Go Kganna Boitlhamelo: Dipatente le Diprotšeke tše di Bopago Intasteri ya Dikoloi

Продвижение инноваций: патенты и проекты, формирующие автомобильную промышленность

Kutyaira Innovation: Patents uye Mapurojekiti Kugadzira Iyo Indasitiri Yemotokari

ขับเคลื่อนการสร้างสรรค์นวัตกรรม: สิทธิบัตรและโครงการที่กำหนดรูปลักษณ์ของอุตสาหกรรมยานยนต์

Pagmamaneho ng Innovation: Mga Patent at Proyekto na Humuhubog sa Industriya ng Automotive

Innovatsiyalarni qo'zg'atuvchi: avtomobil sanoatini shakllantiruvchi patentlar va loyihalar

I-Driving Innovation: Amalungelo Obunikazi Nemiklamo Ebumba Imboni Yezimoto

You make too many different changes in a single pull request TL;DR: Always stick to baby steps Problems Readability Code Review time and complexity Merge Conflicts Testing Challenges Solutions Break the change in atomic parts Context When pull requests become very large, they can pose several challenges and problems for development teams. You must avoid merge requests making different unrelated changes. Sample Code Wrong function generateFibonacci(ordinal) {
  const fibonacciSequence = [0, 1];

  for (let index = index; index < ordinal; index++) {
    const nextFibonacci = fibonacciSequence[index - 1]
          + fibonacciSequence[index - 2];
    fibonacciSequence.push(nextFibonacci);
  }

  return fibonacciSequence;
}

// This function solves a very different problem
// You should not mix them in a single pull request

function voyagerDistanceFromEarth(currentDistanceInKms, yearsTravelled) {
  const speedOfVoyagerInKmS = 17; 

  return currentDistanceInKms + 
        speedOfVoyagerInKmS * yearsTravelled * 60 * 60 * 24 * 365.25;
} Right function generateFibonacci(ordinal) {
  const fibonacciSequence = [0, 1];

  for (let index = index; index < ordinal; index++) {
    const nextFibonacci = fibonacciSequence[index - 1]
          + fibonacciSequence[index - 2];
    fibonacciSequence.push(nextFibonacci);
  }

  return fibonacciSequence;
}

// You break it into two different pull requests Detection Automatic: You can put a threshold and a warning on big merge requests. Exceptions Big refactors that cannot be made with baby steps Tags Complexity Level Beginner AI Assistants AI assistants do not create pull requests. They generate the code you need. Conclusion Software engineers must be experts at managing (and avoiding) . accidental complexity Relations Code Smell 170 - Refactor with Functional Changes Disclaimer Code Smells are my . opinion Credits Photo by on Håkon Grimstad Unsplash First make the change easy (warning: this might be hard), then make the easy change. Kent Beck Software Engineering Great Quotes This article is part of the CodeSmell Series. How to Find the Stinky Parts of your Code

Code Smell 239 - Big Pull Request

If governments had been orange-pilled first instead of citizens, it would have been the end of finance as we know it. A Brief History before UN Bitcoin My idea of Bitcoin starting in the hands of multiple governments and not a handful of individuals is one I find too good to leave to only one blog article. Two days ago, I introduced you to this idea with the article ‘ ’. To recap, I mentioned how it would have been genius beyond Da Vinci, Gauss and Einstein combined, if the great Satoshi Nakamoto had, on that fateful day when he published the Bitcoin white paper online, taken a major step back and stopped his finger from pressing the send key. The Big Boy train that Bitcoin missed “If I do this, Bitcoin will likely become a global phenomenon. But governments will have been left behind so they will play to sabotage the technology. They won’t be glad to play catch up. But if I get them in the lead, they will gladly play lead while citizens gladly play catch up. Citizens have unlimited energy for playing catch up to such great power - the power to own money. Satoshi’s personal notes (Timeline - UN Bitcoin). Moreover, the power is now decentralized and decentralization is by definition the foray of the individual”- I lack the philosophical and other devices of knowledge to properly capture what this means. But I think we would have gotten something to rival the very power of the internet itself. Something to rival any emerging AI technology. and surpass Something powerful enough to finance continuous human space exploration. So that we would have had humans on the moon this year, and humans on Mars 2 years later. The thing is, this would be a financial revolution as momentous as the invention of money. Maybe more. When money was invented, the economic energy for trade was finally captured in a singular good, which dramatically improved the efficiency of our markets. For example, prices were cut from an exponential number that increases with the number of market goods to prices only as many as the number of goods – all priced in the good we now call ‘money’. However, the invention of money was challenged by the fact that the power to own money was still vested, apriori, in the hands of Lords, Chiefs, Kings and Presidents of our time. These political rulers could control the money because the supply was centralized. Some gold mine somewhere, some cowrie shells beach somewhere. They could impose exorbitant taxes, they could inflate the currency, they could loot it. To invent a currency immune to all 3 would be magic. Because it would mean the power to control money would now be something everybody and every organization have to earn. Even Kingdoms and Empires. There has to be proof-of-work. Wanna loot someone’s coins? you might be utterly disappointed, embarrassed, and jobless faster than the time it takes a rocket to get into the exosphere. After all, even a King is an individual. This is what UN Bitcoin would have given us. Bitcoin gave us a diluted version of this, so no wonder it is snailing to global victory. Wall Street in the era of UN Bitcoin As I mentioned before, our collective greed would likely push the UN Bitcoin mining hash rate to 500 zetta hashes / second. Let’s go with a modest 50 zetta hashes per second, 100 times the hash rate of Bitcoin in our timeline. The market cap would likely 100x as well to make UN Bitcoin worth 80 trillion US Dollars circa. 2023. Let that sink in. This is almost the current (our timeline) world’s money supply, which is only $83 trillion and almost , so the world’s GDP would have doubled in 14 years! To move from one to 80 trillion dollars in 14 years would have broken Wall Street’s speedometer, with an average yearly return of 400%, ~40 times the growth rate of the S&P 500. the GDP of all countries combined As I mentioned before, this is not wealth replacing our other assets like energy resources, gold, silver, housing, technology companies. It is wealth adding on and boosting them. From hitherto unimagined sources prior to the 2008 market crash. Unlike CDOs, UN Bitcoin would actually be adding valuable things to the world economy. It would also be the greatest story of money to ever tell. The first thing is dramatic expansion of the electricity energy grid. UN Bitcoin would be using stranded energy from nuclear power, volcanoes and renewables to inch us closer to a Type 1 civilization on the Kardashev scale, and away from carbon-pollutant fossil fuels. With such a big market cap, billions of dollars of UN Bitcoin would be changing hands every day around the world, a lot of it going towards carbon capture and storage technologies. This would make many people excited about the future while they earn very handsome salary packages. Me too. The next thing is Wall Street itself. The invention of lecherous instruments like CDOs and Ponzi ‘crypto tokens’ would be banned and canceled because there would be really few people gullible enough to invest in derivative assets that do not provide more value. The idea of ballooning the global debt would be put somewhere in the FED’s not-to-do list and quickly forgotten, with the idea of sustaining the hash rate for the US government put front and centre. The FED would get an honest day job. UN Bitcoin money flows would be huge (billions) and asymmetric. Spread out to all corners of this planet. While the world’s governments would be leading on the mining front, hence collecting those pretty fees before most private enterprises, innovations like the lightning network would be mostly in the private domain. In Africa, it would greatly help sustain livelihoods for the disadvantaged, while growing the middle class in developing countries on the speedy growth of UN Bitcoin. Good housing would be ubiquitous even in slums, using 3D printers of plastic materials. Cheap electricity would be abundant as Bitcoin’s growth takes the electric grid wherever it goes. Cheap electricity would bring piped utilities like fresh water closer to everybody, hence bring cleanliness and disease-free environs even in our slums. World politics, music, fashion, social media, everything would be transformed in wonderful ways. It cannot be, because it is only a fairy tale. But as Walt Disney has shown us, fairy tales should be told. To give us hope and an ideal to look up to. ******************* P.S. >>  Who wants a comic strip?

Bitcoin Is Snailing to Global Victory

বিটকয়েন বিশ্বব্যাপী বিজয়ের দিকে ধাবিত হচ্ছে

Bitcoin ist auf dem Weg zum globalen Sieg

Bitcoin está avanzando hacia la victoria global

Bitcoin se dirige vers la victoire mondiale

बिटकॉइन वैश्विक विजय की ओर बढ़ रहा है

ビットコインは世界的な勝利に向けて順調に進んでいる

비트코인은 글로벌 승리를 향해 달려가고 있습니다

Bitcoin está caminhando para a vitória global

Биткойн движется к глобальной победе

Bitcoin Küresel Zafere Sürülüyor

Bitcoin đang tiến tới chiến thắng toàn cầu

比特币正在走向全球胜利

So, you've developed an app or a SaaS and are grappling with the challenge of attracting your initial users. It's a common struggle, and the first 100 users are undeniably the toughest to acquire. I've compiled insights from leading SaaS companies, outlining a set of actionable strategies. The key to gaining early-stage customers often lies in undertaking activities that aren't easily scalable. One prevalent mistake at the outset is an excessive focus on the future. This is a common scenario—I frequently observe founders yearning for virality and rapid scalability, envisioning massive success. However, getting lost in these dreams can divert attention from what truly matters. In reality, a fledgling founder should concentrate on comprehending their customer base. Conducting research doesn't require a large user base; a handful of individuals is sufficient. Obtaining the first few dozen users is more feasible through manual actions—activities that, although not scalable, lay the foundation for sustainable growth. Now, let's delve into some examples of these manual actions. Massive following people on Twitter This strategy proved instrumental in Suhail's efforts to launch Mixpanel, the analytics tool. https://twitter.com/Suhail/status/1009454402048937986?embedable=true Remember that you can follow up to 400 persons per day. Start with an email newsletter The concept is to curate a list of individuals who appreciate your content and then leverage this audience as a launching pad for your product. One of my favorite instances of employing this strategy involves Ryan Hoover's experience from a decade ago. He initiated a daily email newsletter featuring intriguing startups he discovered. Over time, he cultivated a list of 170 highly engaged individuals. These recipients not only responded to Ryan but also expressed their enjoyment of his curated digests. This positive interaction sparked the idea to develop a product. Enter the infamous Product Hunt. With the support of this initially small yet enthusiastic audience, the new website swiftly gained momentum, transforming into the premier social network for startup enthusiasts. "The Collinson Installation" Paul Graham writes: "At YC, we use the term Collinson installation for the technique they invented. More diffident founders asked: 'will you try our beta?'. And if the answer is yes, they say 'great! We will send you the link'. But Collinson brothers weren't going to wait. When anyone agreed to try Stripe, we would say 'right then, give me your laptop!'. And set them on the spot." Source: (must read btw) http://paulgraham.com/ds.html Product forums Zapier serves as a tool that seamlessly connects different applications, such as Salesforce with MailChimp or Dropbox with Google Drive. Now, who constitutes Zapier's user base? That's right—the users of these diverse apps. Where do you find these users? Often, on the product forums of platforms like Salesforce, MailChimp, and others. And here's where the strategy unfolds. Zapier's CEO employed a simple yet effective plan. He frequented product forums for companies like Dropbox, Salesforce, and Evernote, scanning for posts like: "I love MailChimp! It would be awesome if you had Wufoo Integration!" Capitalizing on these opportunities, he presented Zapier as a solution. While each link brought in only 10 visits, the traffic was modest. However, the CEO recognized that he was attracting the right customers—50% of these visitors signed up for the beta. A remarkable success rate! The takeaway here is clear: targeted outreach is the key. You don't necessarily need a thousand customers to kickstart your venture; you just need the right 10. Source: https://read.first1000.co/p/zapier Direct sales "Content marketing doesn't work nearly as well for a new product. Direct sales killed it." says Nathan Barry, the founder of ConvertKit. While we all detest spam, there's an acknowledgment that, when executed correctly, it can yield results. The key lies in meticulous research before approaching a potential client, enabling a personalized and compelling offer. Let's compare two scenarios. First scenario:
"Hello, dear sir/madam! Your company has a decent website, but it could be better. Please buy my professional website speedometer tool." Now, consider the second approach:
"Hello, Alex. I learned about your company while watching your latest podcast show with James. You were discussing website performance extensively. Out of curiosity, I tested your website on my speedometer tool, and it only scores 18 out of 100. Want to know what exactly needs improvement?" The difference is evident, isn't it? Nathan Barry introduces another intriguing concept called "concierge migrations": "The biggest objection in the sales process for us has always been. 'But it's so much work to switch!'So we did the ultimate thing that doesn't scale and offered to switch them out of their ConvertKit. Totally for free. Yes. It costs us a lot of time and money, but the referrals and ongoing revenue give an incredible ROI." Great tactic that works for the type of products that are hard to move from. For example, a website builder (my case 🙂). Source: https://nathanbarry.com/2015-review/ Keyword in domain name The next strategy is truly ingenious, and it's surprising that more people aren't utilizing it nowadays. This gem dates back to 2013 when the team at Doordash aimed to validate the demand for quick food delivery. Despite having limited resources for marketing, they came up with a brilliant plan. Their approach was to target individuals in Palo Alto searching for food delivery on Google. Doordash strategically chose the domain name "PaloAltoDelivery.com," anticipating that the domain would secure top positions in Google searches for the keywords "Palo Alto delivery." Essentially, the keyword became the domain name, and it proved to be a highly effective move. Source: https://read.first1000.co/p/case-study-doordash I personally employed a similar strategy with success. My side project, uigenerator.org, has generated over $20,000 in profit since 2022, with the majority of the traffic originating from Google. You can probably guess the keyword. Moreover, just a couple of weeks ago, a friend of mine used the same tactic to garner free traffic from Google. He created a website, allgpts.co, which now ranks at the top for the "all gpts" keyword. So, yes, the "keyword in domain" trick remains a viable and potent strategy. ​ This post was originally an which was then flavored with memes and turned into a . Originally published . 𝕏 thread YouTube video here

The First 100: Proven Tactics From Stripe, Zapier & Convertkit That Get You the Users You Want

প্রথম 100: স্ট্রাইপ, জাপিয়ার এবং কনভার্টকিট থেকে প্রমাণিত কৌশল যা আপনাকে আপনার পছন্দের ব্যবহারকারীদের পাবে

Die ersten 100: Bewährte Taktiken von Stripe, Zapier und Convertkit, die Ihnen die gewünschten Benutzer verschaffen

Los primeros 100: tácticas comprobadas de Stripe, Zapier y Convertkit que le permitirán obtener los usuarios que desea

Les 100 premiers : tactiques éprouvées de Stripe, Zapier et Convertkit qui vous permettent d'obtenir les utilisateurs que vous souhaitez

पहली 100: स्ट्राइप, जैपियर और कन्वर्टकिट की सिद्ध युक्तियाँ जो आपको मनचाहे उपयोगकर्ता दिलाती हैं

最初の 100: 望むユーザーを獲得する Stripe、Zapier、Convertkit の実証済みの戦術

첫 번째 100가지: 원하는 사용자를 확보하는 Stripe, Zapier 및 Convertkit의 입증된 전술

As primeiras 100: táticas comprovadas de Stripe, Zapier e Convertkit que proporcionam os usuários que você deseja

Первые 100: проверенные тактики от Stripe, Zapier и Convertkit, которые принесут вам нужных пользователей

İlk 100: Stripe, Zapier ve Convertkit'ten İstediğiniz Kullanıcılara Ulaşmanızı Sağlayan Kanıtlanmış Taktikler

100 đầu tiên: Các chiến thuật đã được chứng minh từ Stripe, Zapier & Convertkit giúp bạn có được người dùng như mong muốn

前 100 名：来自 Stripe、Zapier 和 Convertkit 的经过验证的策略，可为您带来所需的用户

The Fifth Dimension: Worlds Beyond Measure 

A Comprehensive Guide to UAV Digital Forensics With DJI Drones

Let's learn about via these 53 free stories. They are ordered by most time reading created on HackerNoon. Visit the to find the most read stories about any technology. Software Engineering Metrics /Learn Repo 1. The Engineering Leader’s Guide to Empowering Excellence with Data [FREE ebook] Find out how engineering data can help you remove blockers, encourage professional growth, and empower excellence on your team. 2. 7 Qualitative Metrics to Measure Code Quality that Every Engineer Needs to Know High-quality code is critical to creating functional error and bug-free software that is easy to edit and understand. Let's look at how to measure code quality. 3. Welcome To the New Reality: Engineering Metrics are Business Metrics According to a McKinsey study of over 400 large enterprises across 12 industries, companies with high-performance engineering teams best their competition in all areas, including revenue growth, customer satisfaction, and brand perception. The evidence is so clear that the study itself is called, “How software excellence fuels business performance,” and it concludes that software development is integral to business success in all industries — retail, financial services, manufacturing, and of course, software companies, all require a strong engineering department to succeed. Yet, many executives view their engineering departments as a “black box.” While other departments report on their success with metrics like revenue, customer retention rate, or cost of new customer acquisition, engineering metrics don’t often make it into the board deck. But engineering metrics are essential to understanding how your company is doing. They convey critical information about your company’s ability to deliver value to your customers, and your company’s potential for future success. Plus, engineering is expensive — it’s important to know whether that’s money well-spent. For a holistic picture of how your engineering department — and your business — is doing, you need to start tracking engineering metrics. 4. Why You Should Use Lead Time Instead of Cycle Time Our concepts of Lead Time and Cycle Time came from the field of Operations Management and Production Engineering. As such, I think it’s beneficial to all of us to maintain coherent with them and use the same semantics in Software Engineering Management as well. 5. Developing Software Quality Metrics as a Data Scientist - 5 Lessons Learned Software quality metrics are essential tools in ensuring a product provides the best experience to its users. Here are some tips for (not only) data scientists. 6. Now Available: The Engineering Leader’s Guide to Cycle Time [eBook] One critical engineering metric can help you innovate faster, outrun your competition, and retain top talent: Cycle Time. It’s your team’s speedometer, and it’s the key to everything from developer satisfaction to predictable sprints. And Cycle Time has implications beyond engineering — it’s also an important indicator of business success. That’s why we’re excited to announce the release of our new book, The Engineering Leader’s Guide to Cycle Time. For those looking to boost their team’s efficiency and productivity, we offer a data-driven approach, backed by research, case studies, and our own experience as an industry-leading Engineering Intelligence platform. 7. Why You Should Manage WIP Having too much Work in Process, also known as Work in Progress (WIP), is a remarkably common issue. In my experience, management often encourages this behavior. I don’t know if it is the notion that we will get more done if we work on more things simultaneously. Or perhaps there is a fear we won’t get enough things done unless we work on several of them at once. 8. How Engineering Teams Can Leverage the Power of Metrics Ever wondered what key metrics other engineering teams are tracking? 
The short answer: it varies completely. Even within the same organization, different teams 9. 50 Shades of Lead Time: Measuring Each Part of the Development Process I have read multiple definitions for Lead Time and Cycle Time over the last years. Recently, I shared why I prefer using the first over the later. 10. Engineering Metrics: The Moneyball Approach Engineering managers often rely on subjective clues to assess how their team is doing. But decisions made based on gut feel and imperfect measurements are less than ideal — sometimes they result in team success; other times they result in disappointment. 11. How to 10x Your Skills and Become a More Efficient Tech Lead The secret sauce to an engineering team's success is an effective tech lead guiding the team to be on the right track. 12. How To Assess And Improve Your Software Engineering Team's Performance How do you measure how well your engineering team is doing and how do you find the bottlenecks where you can improve things the most? 13. Managers: Beware the Fallacy of Process Processes are essential for effective management. They keep people in sync, making it possible for team members to come together and achieve a shared goal. But they’re also dangerous. Processes can create the illusion that things are running smoothly because they’re moving along according to the shared understanding of how they’re “supposed to” run. This is the Fallacy of Process — the idea that by adding consistency and predictability to a shared workflow, a given process is inherently valuable. Too often, process becomes canon. A team develops an effective way of doing something, then returns to that framework indefinitely, long past its expiration date. 14. Technical Debt or Technical Fraud Technical Debt is one thing, but when let to fester for too long, it can become Technical Fraud. A much more dangerous and much more insidious predator. 15. Should You Hire More Software Engineers or Better Manage the Ones You Have? That technology is here to stay is an obvious duh. If and how well-prepared companies are to deal with the constant need to increase investments in technology, that’s not as simple. Another obvious axiom is that software engineers and developers are highly valuable resources. Weather having more or putting the ones you have to better use is the best approach, that is less obvious. 16. On Discussing Engineering Metrics to Direct Your Team's Focus, Daily Software engineering metrics help daily stand-up meetings to be more productive for the team. They can become tedious or irrelevant for many developers when they frequently exceed the fifteen minutes time box or even sound like a work report. 17. Five Pieces of  Advice for Developers Transitioning to Tech Leader Position Becoming a Tech Leader implies in more responsibilities. Your toolkit must include new skills. Besides designing, writing, and reviewing code, tech leaders must care about the team members and the overall code quality and architecture. 18. DevOps: I Measure The Metrics A Bit Differently. Here's Why The four key DevOps metrics are an exciting set of measurements. They’re getting more and more relevant since the book Accelerate has been published. I firmly believe they’re essential for engineering teams seeking effectiveness and efficiency. 19. The 6 Stages of the Software Development Process The software development lifecycle methodologies (SDLC) or the Systems Development Life Cycle method aids in planning the design process of the software 20. Becoming a Manager of Engineers: How to Focus on Visibility and Predictability Becoming a manager is usually one of the biggest challenges of an engineer’s career. We are usually used to algorithms and state machines, which are predictable and have specific outputs depending on the input. 21. Leveraging Data as a Proactive Engineering Manager Proactive (software) engineering leadership means you’re not a firefighter all the livelong day. 22. Startup CEOs: Here’s Good News You Can Include in Your 2020 Board Deck As you prepare for your board meetings, you might be struggling to find some good news to share with the board. Sure, it’s a mistake to go into a board meeting pretending everything is going well — board meetings are a valuable opportunity to share your startup’s challenges and get guidance from a panel of trusted advisors. 23. OKRs vs. KPIs: What's the Difference for Engineering Teams? OKRs vs. KPIs, what are the differences? That’s a common question I hear from managers of Engineering Teams. KPIs are more straightforward to explain than OKRs, which can be tricky and more complex. They don’t mean the same, although they are connected. 24. Verification and Configuration Management for Avionics Systems The performance of verification and configuration management is essential to the ARP4754A document and other avionics development documents. ARP4754A, officially titled Guidelines for Development of Civil Aircraft And Systems, is concerned with “the development of aircraft systems taking into account the overall aircraft operating environment and functions.” 25. Code Refactoring: A Comprehensive Guide for Engineers In this guide, you’ll learn all about refactoring source code: the benefits, challenges, tools, and best practices, and what is the difference between refactoring and technical debt. 26. Strategies to Improve Your Sprint Retrospectives with Data Most agile teams do sprint retrospectives at least once a month, to iterate and improve on their software development process and workflow. However, a lot of those same teams rely only on their feelings to “know” if they have actually improved. But you need an unbiased reference system if you want to compare how two sprints went. 27. Tech Teams in Brazil: 42% Deploy Daily, Another 38% Deploy Weekly [Study] Between January 29th and March 5th, we conducted a survey to get a technology landscape of the Brazilian startups and companies. We released the full report with the results of the study. 28. 5 responsibilities of a Tech Lead and 17 Metrics to Track Their Performance Tech lead, team lead, software architects, and engineering managers — as any developer already knows, naming is hard. Throughout the industry, those roles are as fuzzy as their responsibilities. 29. What Should I Do After the Data Observability Tool Alerts Me We need to start building the best practices across the ecosystem to maximize the value of data observability. 30. How To Determine A Good Application Architecture When I started writing a small but real growing project, I noticed that the app shouldn’t only work well but also should be well organized. 31. 5 Metrics Engineering Managers Can Extract from Pull Requests Many Engineering Managers promote Pull Requests as part of the development workflow. It’s a consolidated practice that brings lots of benefits. It consists of comparing the changes of a branch with the repository’s base branch (conventionally called master). 32. It Is Time To Make Tough Engineering Decisions We have entered a critical time in the life cycle of many companies around the world. The world has shifted away from a period of immense growth, and as many struggle to meet revenue expectations, companies and their leaders face a ton of pressure both internally and externally. 33. What's Your Cycle Time? If you can’t answer it, don’t worry, you’re not alone. Many engineering leaders couldn’t tell you without some significant number-crunching. Gaining visibility into performance is only half the battle though. Knowing how to interpret metrics and how to apply them to improving performance is where the magic happens. Many CEOs do not know how to align engineering metrics to business KPIs (revenue, customer retention, etc.). Bringing metrics to your board or non-technical CEO for the first time may be challenging if you are unable to help them bridge the gap. 34. Software Requirements Specifications Template This article is devoted to the consideration of Software Requirements Specifications, their importance in the software development process, and how they could be written. Within this article, I will pay more attention to the effective SRS template and its description. 35. Engineering Leadership versus Engineering Management: What's The Difference? It has become a constant temptation to praise engineering leaders and undervalue engineering managers, but maybe we shouldn’t be focusing on their differences but on correctly understanding their roles. 36. Increasing Engineering Efficiency with Software Development Analytics We’re right on the precipice of a reality that’s more agile than Agile — as we move from Agile development and a DevOps culture to autonomous development 37. 7 Rules to Track Software Engineering Metrics Correctly How to Use  -  and NOT Abuse  -  Software Engineering Metrics 38. You Can’t Set Effective Goals for Software Developers Without Data The most popular goal-setting frameworks — FAST goals, SMART goals, OKRs — break when it comes to the engineering department. The cornerstone of every framework is specificity, but most engineering departments run on benchmarks and estimations that are vague, subjective, or constantly in flux. Common project measurements, like story points or t-shirt sizes, lack objectivity. And while lists of completed features are definite cause for celebration, they’re too broad to provide insight into the actual work being done by the engineering department. To get specific, you need data. With information from your VCS, it’s possible to gain visibility into your development workflow and spot opportunities for advancement. Subjective measurements, like t-shirt sizes and story points, can be replaced with objective metrics that are comparable across projects and teams. For example: 39. Software Quality: The Top 10 metrics to build confidence How do you measure quality in software engineering? I guess this is the question there will always be a debate on. There are so many approaches to this question that finding only one answer is just impossible. In this article, we will be listing the quality-related metrics that the top engineering teams have been keeping track of, and see when and how you should use them. 40. How Engineering Managers Benefit from Synthetic Metrics Engineering managers are in charge of tech teams. It means there are tens or maybe hundreds of people supporting them. Generally, they need to ensure the best practices around software development, hire and train engineering staff, align and motivate the team towards the company’s goal, manage the team’s performance, and be accountable for all technical decisions. 41. Top 10 Software Engineering Metrics To Track If You Lead An Agile Team Every conversation I have with CTOs, Engineering Managers, and Tech Leaders eventually gets to the “Which Metrics Should We Measure?” discussion. 42. Top 3 Metrics For Engineering Team Performance What’s the overall performance of your engineering team? Let’s look at how we can improve your team’s performance. 43. Software Intelligence: How to Take Quality Control in 6 Practical Steps Lead Photo by Max Duzij on Unsplash 44. How Metrics Lead to Effective Sprint Retrospectives In the Atlassian playbook, it states that Sprint Retrospective’s goal is to identify how to improve teamwork by reflecting on what worked, what didn’t, and why. Usually, the meeting consists of brainstorming what the team did well and what the team needs to do better. 45. Overwelming Formula For Goal Achievement As a Tech Lead In 90 Days Recently, I read a blog post titled "VPE and CTO — The first 90 days". It’s a brief article in which James Turnbull shows a mind map with four areas that “every new technical leader needs to, at least, think about and explore when starting at a new organization.” 46. How to Measure Your Technical Debt: 8 Metrics to Consider Technical debt metrics help you to monitor deficiencies in your current codebase. We decided to look at how they work, and pick out the best tracking tools. 47. It Could Always Have Been Done Better! (In Hindsight) This is one of the hardest lessons to learn in the Software Engineering business.  It doesn't matter how good you were at doing something, or how much you accomplished, there will always be something that didn't go right. There was that feature you hacked to meet a deadline, or that bug that took 4 days to diagnose, or that weird edge-case that flaked out, or ...
And even when you didn't have any of those issues, there are the things you didn't do - the features you didn't put in, or the customer types that you didn't support, or whatever. 48. Rework Costs Your Company Millions — How to Cut Back? On average, a software development team reworks about 26% of its code prior to release. Even after accounting for necessary changes, those wasted hours can cost a medium-sized business upwards of $4.7M a year. Still, when engineering leaders look to cut costs, they often look at departmental spending. Software licenses, discretionary expenses, and even salaries may come under scrutiny. But not all costs come with such a clear price tag — inefficiencies in the software development process are harder to quantify, but much more expensive. According to a 2017 DORA white paper, Forecasting the Value of DevOps Transformations, the cost of Rework in software development is staggering, setting businesses of all sizes back millions of dollars a year. 49. How to Select Software Engineering Metrics and Set KPIs that Matter Software Engineering KPIs (Key Performance Indicators) are measurable values that indicate the progress of engineering teams’ performance towards business objectives. Therefore, they need to be consistent, broad enough to consider everyone’s effort, and, most importantly, measurable. 50. Engineering Management Trends in 2022 Take a look at some of the most interesting findings of the 2022 State of Engineering Management report, and become a better engineering manager today! 51. Code Churn: How it Relates to Refactoring and Technical Debt Code churn is a measure or indication of how often a file changes. It typically refers to how often a developer throws out code 52. 1:1 with Alex Roetter: Leading Engineering at Twitter Below is an excerpt from our conversation with Alex Roetter, former SVP of Engineering at Twitter, Managing Director and General Partner at Moxxie Ventures, and featured in the Netflix documentary, The Social Dilemma. 53. Understanding Technical Debt As A Software Engineer What is tech debt? How to manage it effectively? In this Engineer's Complete Guide to Technical Debt, you will learn metrics, statistics, and tools that help engineering teams accelerate the software development process. Thank you for checking out the 53 most read stories about Software Engineering Metrics on HackerNoon. to find the most read stories about any technology. Visit the /Learn Repo

53 Stories To Learn About Software Engineering Metrics

We are excited to release a stable version of React Native ECharts 1.1. In the new version, we have added support for the gesture solution, among other enhancements. Read on to learn more! react-native-gesture-handler , An awesome charting library for React Native, built upon Apache ECharts and leveraging and . Offers significantly better performance compared to WebView-based solutions. If you want to learn more about the project's design principles, you can . @wuba/react-native-echarts react-native-svg react-native-skia click here To provide a more intuitive and accurate understanding of the project's features, we have decided to officially rename the initial version to . In the new version. wrn-echarts @wuba/react-native-echarts The project source code is available at . https://github.com/wuba/react-native-echarts Features ​ Rich Chart Types Supported ​ is a solution that brings the charting library into React Native applications. It utilizes the rendering capabilities of React Native's native components, resulting in a significant improvement in rendering speed. It supports a wide range of commonly used chart types, including line charts, area charts, bar charts, and scatter plots, as well as more complex charts such as candlestick charts and heat maps. It can fulfill various visualization requirements in different scenarios. @wuba/react-native-echart ECharts Here are some examples of common chart types: In addition to the usual chart types, supports a variety of other graphs, such as tree, heat and K-line charts, with excellent rendering performance. @wuba/react-native-echart In addition, we provide comprehensive support for various dynamic charts, and here are some examples. Chart 1 and Chart 2 demonstrate the dynamic changes in per capita income across multiple countries. Chart 1 presents the growth trend of per capita income over the past 70 years, while Chart 2 showcases the dynamic sorting of per capita income for 10 countries in the year 1982. Chart 3 displays a continuously updated speedometer that adapts to changing values over time, and Chart 4 demonstrates a dynamic node addition chart. These charts can dynamically re-render based on evolving data. Regardless of the data update frequency, they consistently deliver outstanding rendering performance. supports a wide range of chart types, but they are too numerous to display here. If you want to explore more comprehensive chart types, you can visit the repository to check them out. There, you will find example demos showcasing various ECharts chart types. @wuba/react-native-echart taro-playground Svg and Skia Supported ​ supports two rendering modes: Svg and Skia. It is implemented based on and . How do you choose between the two rendering modes? From the perspective of rendering speed, Svg and Skia have similar performance, as shown in the following figure. However, it's important to note that Skia rendering has some limitations in terms of Chinese language support. To display Chinese characters correctly, you need to set up fonts separately. Therefore, when choosing a rendering library, please consider the language requirements of your project and the importance of Chinese language support. We recommend selecting the appropriate rendering mode based on specific circumstances to achieve optimal performance and user experience. @wuba/react-native-echart react-native-svg react-native-skia Support various gestures ​ Support for various gestures such as tapping, dragging, and scaling is available. By default, we use the built-in PanResponder from React Native to handle these gestures. Starting from version 1.1, we have added support for the library. If you have already integrated this gesture library into your project, we recommend using it directly to handle gestures for enhanced performance and user experience. react-native-gesture-handler Below is a comparison of the two gesture solutions. Judging from the smoothness of chart scrolling, both the default gesture handling and the use of provide excellent fluidity. You can choose the approach that best suits your needs. react-native-gesture-handler Web Support ​ We also support reusing the components of in the web environment to meet cross-platform requirements and achieve code sharing across multiple platforms. This enables easy code unification, ensures consistency of charts across different platforms, and enhances our development efficiency. @wuba/react-native-echart , provides a wide range of online rendering examples for the web. But how well does it perform on React Native? To address this, we offer corresponding online preview and testing support. You can directly copy the chart configuration to see how it renders on React Native. ECharts, the charting library Online preview click here Roadmap ​ Despite our already extensive and well-rounded support for ECharts, we are committed to further optimizing and enhancing it. In our upcoming work, we will focus on improvements and enhancements in the following areas to deliver even more refined functionality. to see more detailed information and progress updates. Click here Performance Enhancement ​ Compared to the rendering solution using Webview, has achieved significant improvements in overall rendering performance. However, there is still room for further improvement in rendering speed and memory usage when dealing with large data sets. We are committed to optimizing performance in handling large data sets to ensure exceptional performance and stability in various complex data scenarios. @wuba/react-native-echart Known Issue Fixes ​ Currently, the support for the ECharts charting library is very comprehensive. However, there are still some issues that need to be improved in some chart rendering, such as not supporting map display and incorrect image display in Skia rendering mode. We take these issues very seriously and will continue to work on fixing them. to provide a better chart presentation experience. ECharts GL Supported ​ With the widespread application of 3D visualization in various business scenarios, such as the displayed 3D chart below, we will continue to explore and enhance our support for ECharts GL to meet more business needs. You can click to check the latest progress. here Improve the Infrastructure ​ In the future, we will continue to improve the infrastructure by refining test cases, adding user use cases and other content. Standardized test cases can check whether any changes made during the development process have an impact on other functions. We will gradually add more test cases, standardize the code and improve the quality of the code. Acknowledgments ​ We are deeply grateful to all our friends in the open-source community. Whether you have contributed to the codebase, provided bug reports along with contextual information, or shared ideas to enhance existing features, your contributions have been incredibly valuable to this project. We wholeheartedly welcome you to join us and actively participate in the project's discussions and collaborative development. @wuba/react-native-echarts Lastly, we would like to express our special thanks to the developers who have contributed to the project's success: Also published . here

Revolutionizing Data with React Native ECharts 1.1: Now More Interactive!

190 Stories To Learn About Engineering Management

Stories, News & Mentions about SPEEDOC

Speedoc’s Stories on HackerNoon