# effective Published articles for effective. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Senior Engineer ≠ Years of Experience DevFeed: [Senior Engineer ≠ Years of Experience]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-08-24T06:01:00Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [Software Engineering](), [Development](), [engineering-culture]() Tags: [effective](), [engineering](), [experience](), [learning](), [mistakes](), [software]() ### AI overview This opinion argues that years of software engineering experience do not reliably measure engineering ability. Repeated habits, including poor design, avoiding tests, and overengineering, can become more entrenched over time, while continuous learning, experimentation, feedback, and willingness to change are presented as stronger indicators of effectiveness. ### Source excerpt "I've been doing this for 15 years, so I already know." ## How Guideless uses Tinybird for real-time product analytics and training insights DevFeed: [How Guideless uses Tinybird for real-time product analytics and training insights]() Original publisher: [Read original article]() Author: Tinybird Published: 2026-08-20T16:00:00Z Content type: article Language: en Sources: [Tinybird]() Topics: [product analytics](), [real-time](), [Back end]() Tags: [analytics](), [backend](), [customer-stories](), [effective](), [insights](), [product-analytics](), [real-time]() ### AI overview The article describes how Guideless used Tinybird to launch real-time product analytics without building a separate analytics backend. It says the approach saved weeks of engineering work and produced engagement insights for improving training effectiveness. ### Source excerpt Learn how Guideless used Tinybird to launch real-time product analytics without building a separate analytics backend, save weeks of engineering work, and turn engagement data into insights that help users create more effective training. ## Cost-effective orchestration with Fable 5 DevFeed: [Cost-effective orchestration with Fable 5]() Original publisher: [Read original article]() Author: Jeff Morhous Published: 2026-07-21T11:37:27Z Content type: tutorial Language: en Sources: [The AI-Augmented Engineer]() Topics: [Fable](), [Claude Code](), [Orchestration]() Tags: [better](), [claude-code](), [cost](), [effective](), [fable](), [how-to](), [results]() ### AI overview This tutorial presents Fable 5 in Claude Code as an orchestration approach and claims it can produce better results at lower cost. The supplied text does not provide implementation details or supporting measurements. ### Source excerpt Fable 5 in Claude Code is effective. I'll show you how to use Fable as an orchestration to get better results at a fraction of the cost ## 4 Disciplines That Separate Effective Engineers From Busy Ones DevFeed: [4 Disciplines That Separate Effective Engineers From Busy Ones]() Original publisher: [Read original article]() Author: The T-Shaped Dev Published: 2026-02-24T11:19:19Z Content type: article Language: en Sources: [The T-Shaped Dev]() Topics: [Software](), [coding](), [Code]() Tags: [code](), [effective](), [engineering](), [software]() ### AI overview The article identifies four disciplines that distinguish effective software engineers from busy ones. It emphasizes solving the right problems, understanding users and team strategy, prioritizing carefully, and treating AI as a tool rather than a substitute for judgment. ### Source excerpt Learn about the daily habits that help engineers be more effective. (7 min) ## Using Mutation Testing to Evaluate Test Suite Effectiveness DevFeed: [Using Mutation Testing to Evaluate Test Suite Effectiveness]() Original publisher: [Read original article]() Author: Andres Sacco Published: 2025-12-04T02:02:10Z Content type: tutorial Language: en Sources: [Java Advent Calendar]() Topics: [mutation-testing](), [Testing](), [test-coverage](), [Code]() Tags: [2025](), [code](), [code-coverage](), [effective](), [mutation](), [mutation-testing](), [testing](), [tests]() ### AI overview The article explains why high code coverage does not necessarily indicate effective tests. It introduces mutation testing, which evaluates a test suite by making small controlled changes to source code and checking whether the tests detect those changes. ### Source excerpt Creating or modifying an application involves many aspects, such as following best practices and applying design patterns to solve everyday problems. After writing the code, developers usually add unit tests and rely on tools like Sonar to track metrics such as code coverage and highlight potentially untested areas. However, high test coverage does not guarantee [...] The post Test Your Test appeared first on JVM Advent. ## How to Make Team Retrospectives Effective DevFeed: [How to Make Team Retrospectives Effective]() Original publisher: [Read original article]() Author: Domenico Luciani Published: 2025-11-02T23:00:00Z Content type: opinion Language: en Sources: [Domenico Luciani]() Topics: [retrospectives]() Tags: [continuous](), [effective](), [retrospective](), [self-improvement](), [team](), [team-dynamics]() ### AI overview This opinion article explains how team retrospectives can support learning, self-improvement, idea sharing, celebration, and continuous improvement. It emphasizes psychological safety, focusing on processes rather than blaming people, and adapting the retrospective format to the team's situation. ### Source excerpt A team retrospective is not just another useless meeting, and if you feel so, it means you are doing it wrong, and this article is for you. ## Escaping the Build Trap DevFeed: [Escaping the Build Trap]() Original publisher: [Read original article]() Author: Tom Published: 2025-09-20T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [Product Management](), [Tech Lead]() Tags: [book](), [business](), [collaboration](), [effective](), [examples](), [experimentation](), [leadership](), [management](), [metrics](), [pitfalls](), [product-management](), [team](), [tech-lead]() ### AI overview A review of Melissa Perri's book Escaping the Build Trap, focusing on its explanation of Product Management, experimentation, metrics, organizational perspective, and creating real value. ### Source excerpt Escaping the Build Trap How Effective Product Management Creates Real Value Author: Melissa Perri This was the first book on Product Management I've ever read, and I'm glad I started with such a solid one. In my daily work, I collaborate closely with product owners, and I wanted to better understand their role: How do they work? What are their priorities? And how can our collaboration be more effective? What I appreciated most about this book is how clearly it structures the profession of Product Management and breaks down its many facets. ## But first, connect with your audience DevFeed: [But first, connect with your audience]() Original publisher: [Read original article]() Published: 2025-05-02T17:21:27Z Content type: tutorial Language: en Sources: [Bert Hubert's writings]() Topics: [Programming]() Tags: [advice](), [effective](), [presentation](), [talks]() ### AI overview The article advises presenters to understand their audience, tailor content to their interests and knowledge, and establish an early connection. It also recommends briefly explaining the presenter's background and relevance to the audience. ### Source excerpt I do a lot of talks and because of this I also attend quite a lot of them. I've previously shared some hopefully useful advice on how to give a decent presentation. But there's something I'd like to add. I'm still somewhat on hiatus, but things appear to be going better! To give the most effective presentation, you must always think about the audience. You are not there for your personal enjoyment. ## Best practices for downsampling billions of rows of data DevFeed: [Best practices for downsampling billions of rows of data]() Original publisher: [Read original article]() Author: Paco González Published: 2025-04-08T00:00:00Z Content type: article Language: en Sources: [Tinybird]() Topics: [data]() Tags: [best-practices](), [compute](), [data](), [effective](), [reduce](), [scalable-analytics-architecture]() ### AI overview The article presents best practices for downsampling billions of rows of data. It states that downsampling can reduce compute resource use, while noting that this approach involves tradeoffs. ### Source excerpt Data downsampling can be an effective way to reduce compute resources, but it comes with tradeoffs. ## Mixed-input matrix multiplication performance optimizations DevFeed: [Mixed-input matrix multiplication performance optimizations]() Original publisher: [Read original article]() Author: Google AI (noreply@blogger.com) Published: 2024-01-26T19:56:00Z Content type: article Language: en Sources: [Google Research]() Topics: [Large language models (LLMs)](), [quantization](), [Hardware](), [GPU](), [Nvidia](), [Tensor Cores](), [Open Source](), [Software](), [data type]() Tags: [accelerators](), [ai](), [algorithms](), [ampere](), [compute](), [conversion](), [data](), [deep-learning](), [effective](), [efficiency](), [hardware](), [implementation](), [language-models](), [large-language-models-llms](), [models](), [nvidia](), [optimization](), [performance](), [precision](), [quantization](), [research](), [software](), [tensor-cores]() ### AI overview This Google Research article explains software techniques for mapping mixed-input matrix multiplication onto NVIDIA Ampere hardware. It describes using lower-precision weights with higher-precision inputs, data-type conversion, and layout transformations to support weight-only quantization. The authors report minimal software overhead and performance close to peak hardware capabilities, and state that the techniques were released in the open-source NVIDIA/CUTLASS repository. ### Source excerpt Posted by Manish Gupta, Staff Software Engineer, Google Research AI-driven technologies are weaving themselves into the fabric of our daily routines, with the potential to enhance our access to knowledge and boost our overall productivity. The backbone of these applications lies in large language models (LLMs). LLMs are memory-intensive and typically require specialized hardware accelerators to efficiently deliver tens of exaflops of computing power. This blog post shows how we can start addressing the computational challenges by utilizing memory more effectively. The bulk of an LLM's memory and compute are consumed by weights in matrix multiplication operations. Using narrower data types reduces memory consumption. For example, storing weights in the 8-bit integer (i.e., U8 or S8) data type reduces the memory footprint by 4x relative to single-precision (F32) and 2x relative to half-precision (F16) or bfloat16 (BF16). Furthermore, previous work has shown that LLM models running matrix multiplications with weights in S8 and input in F16 (preserving higher precision of the user-input) is an effective method for increasing the efficiency with acceptable trade-offs in accuracy. This technique is known as weight-only quantization and requires efficient implementation of matrix multiplication with mixed-inputs, e.g., half-precision input multiplied with 8-bits integer. Hardware accelerators, including GPUs, support a fixed set of data types, and thus, mixed-input matrix multiplication requires software transformations to map to the hardware operations. To that end, in this blog we focus on mapping mixed-input matrix multiplication onto the NVIDIA Ampere architecture. We present software techniques addressing data type conversion and layout conformance to map mixed-input matrix multiplication efficiently onto hardware-supported data types and layouts. Our results show that the overhead of additional work in software is minimal and enables performance close to the peak har ## Effective Kotlin Item 49: Use caching when possible DevFeed: [Effective Kotlin Item 49: Use caching when possible]() Original publisher: [Read original article]() Published: 2023-11-20T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Caching](), [Back end](), [Android](), [Kotlin]() Tags: [android](), [backend](), [caching](), [effective](), [how-to](), [optimization](), [performance](), [workshop-learning-programming]() ### AI overview This article explains caching as a performance optimization technique. It describes caches as quickly accessible redundant copies of data, demonstrates caching repeated user lookups, and discusses stale data and time-based expiration, with different considerations for backend and Android applications. ### Source excerpt Why we should use caching and how to do it. ## Effective Kotlin Item 48: Consider using object declarations DevFeed: [Effective Kotlin Item 48: Consider using object declarations]() Original publisher: [Read original article]() Published: 2023-11-06T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [object](), [classes](), [Kotlin programming]() Tags: [classes](), [consider](), [effective](), [instead](), [kotlin](), [object](), [regular](), [using](), [workshop-learning-programming]() ### AI overview This tutorial explains when to use Kotlin object declarations instead of regular classes, including the covariant Nothing object pattern for generic types. ### Source excerpt Why we should use object declarations instead of regular classes. ## Solution-Oriented Coaching, or the Lost Art of Effective Conversations DevFeed: [Solution-Oriented Coaching, or the Lost Art of Effective Conversations]() Original publisher: [Read original article]() Author: Emmanuel Goossaert Published: 2023-08-23T09:24:04Z Content type: article Language: en Sources: [Code Capsule]() Topics: [Job](), [help](), [decision-making](), [Framework](), [Learning]() Tags: [coaching](), [decision-making](), [effective](), [leadership](), [leadership-and-management](), [leadership-and-management-leadership-management-mentoring-sfbt-solution-focused-solution-focus](), [management](), [managerial-roles](), [mentoring](), [reports](), [sfbt](), [solution-focused](), [solution-focused-brief-therapy](), [solution-focused-coaching](), [solution-focused-leadership](), [solution-oriented]() ### AI overview This article explains how Solution-Focused Brief Therapy techniques can be adapted into Solution-Focused Coaching for workplace conversations with direct reports and peers. It draws on the author's three years of personal experience, covering the framework's basics, workplace use, limitations, and further resources. ### Source excerpt Solution-focused coaching is a way of using therapy techniques in order to lead better conversations with direct reports and peers at work. The post Solution-Oriented Coaching, or the Lost Art of Effective Conversations first appeared on Code Capsule. ## Prototyping as a Quick and Cost-Effective Way to Test Hypotheses DevFeed: [Prototyping as a Quick and Cost-Effective Way to Test Hypotheses]() Original publisher: [Read original article]() Author: IceRock Development Published: 2023-02-09T10:58:46Z Content type: article Language: en Sources: [Stories by IceRock Development on Medium]() Topics: [Development](), [Mobile](), [ui](), [navigation](), [App]() Tags: [android-app-development](), [apps](), [cost](), [design](), [effective](), [ios-app-development](), [mobile](), [mobile-app-development](), [mobile-apps](), [navigation](), [prototyping](), [ui](), [ui-design](), [workflows]() ### AI overview The article explains how IceRock uses wireframe and design prototypes during mobile app development. It argues that clickable prototypes communicate navigation, functionality, usability, and final behavior more effectively than screen maps, with fidelity varying according to client needs. ### Source excerpt Businesses are always looking for ways to launch apps quickly and with minimal development costs. There are various ways to do this: sketch your app design, launch apps from scratch with frameworks, or use builders. Different situations call for different solutions. In this article, I will tell you about the approaches we use at IceRock. Our company specializes in outsource development of mobile apps, so we constantly look for new ways to speed up the development and enhance tried-and-true workflows. Why a Prototype is Better than a Screen Map Before we start the development, we prepare one or several prototypes of the future app. This is more efficient than going straight to design or starting to develop the app right away. A screen map is a set of images showing all app screens and their relationships. It visualizes the flow of the screens, but it doesn't allow you to get a feel for the result and understand how usable the interface will be. In other words, it is less illustrative. Clickable prototypes are more informative. We divide prototyping into two parts: we use a "wireframe prototype" before the design, and a "design prototype" after. A wireframe prototype is a schematic prototype that helps us understand the navigation and functionality aspects of an app. A design prototype is a product assembled once the UI design is complete. It is used to demonstrate the future app to the customer, for marketing purposes, and sometimes for testing. It also shows the developers how the final app is supposed to work. After the design, we make a clickable prototype. The level of detail in this prototype can vary according to the client's needs: it can be low-fidelity or high-fidelity. Low-fidelity prototypes consist of static images with active links to the next screens on the buttons. This is the type of prototype we used for the Snow4u project. High-fidelity prototypes are very similar to the app and fully interactive: you can type any text in the input fields, there are ## Nix, Caching, and CIs DevFeed: [Nix, Caching, and CIs]() Original publisher: [Read original article]() Published: 2022-12-17T00:00:00Z Content type: article Language: en Sources: [Garnix Blog]() Topics: [Nix](), [Caching](), [ci]() Tags: [caching](), [ci](), [easy](), [effective]() ### AI overview The article discusses caching in Nix CI and characterizes it as easy, safe, and effective. ### Source excerpt Caching in a Nix CI is remarkably easy, safe, and effective! ## Effective Kotlin Item 10: Design for readability DevFeed: [Effective Kotlin Item 10: Design for readability]() Original publisher: [Read original article]() Published: 2022-10-24T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Kotlin programming](), [Programming]() Tags: [code](), [cognitive-load](), [effective](), [elvis-operator](), [implementation](), [junior](), [kotlin](), [programming](), [readability](), [workshop-learning-programming]() ### AI overview This article explains why code readability matters in Kotlin, emphasizing that developers spend much more time reading code than writing it. It argues that fewer lines or characters do not necessarily make code easier to understand, and that readability depends on cognitive load and familiarity with programming idioms, especially for less experienced Kotlin developers. ### Source excerpt Do we really want out applications concise, or do we rather want them readable? ## Counting over Range Predicates DevFeed: [Counting over Range Predicates]() Original publisher: [Read original article]() Author: Richard Startin's Blog Published: 2022-03-27T00:00:00Z Content type: tutorial Language: en Sources: [Richard Startin's Blog]() Topics: [Java](), [Streams](), [Sorting](), [Benchmark](), [Code]() Tags: [benchmark](), [effective](), [filter](), [inlining](), [java](), [modularity](), [performance](), [roaring](), [sorting](), [streams]() ### AI overview This post examines counting objects that satisfy range and other filters when no database is available. It compares Java's Stream API with specialized Java code and finds that exploiting data already sorted by time can make filtering and counting more efficient. ### Source excerpt This post follows on from my last post about selecting objects satisfying a range predicate, and instead looks at how to count the objects. If you can select objects, you can count them too, but it's a simpler problem so resources can be saved with a specialised solution. ## Principles and Techniques for Effective Localization DevFeed: [Principles and Techniques for Effective Localization]() Original publisher: [Read original article]() Published: 2021-08-30T09:00:00Z Content type: article Language: en Sources: [Material.io - Material Design]() Topics: [Localization (l10n)]() Tags: [effective](), [inclusive](), [techniques](), [translation]() ### AI overview The article presents principles and techniques for effective localization, emphasizing inclusive experiences beyond direct translation. ### Source excerpt Going beyond translation to create more inclusive experiences ## Ten Reasons the Author Says They Are Effective at Getting Things Done DevFeed: [Ten Reasons the Author Says They Are Effective at Getting Things Done]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-11-18T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Code](), [coding](), [Test-driven development](), [Software as a service]() Tags: [code](), [coding](), [complexity](), [developer](), [effective](), [productivity](), [startup](), [tdd](), [time]() ### AI overview The author explains personal productivity practices, including removing sources of frustration, calculating the value of time, learning from people with greater expertise, and accepting messy code over perfection. The supplied text ends partway through the discussion. ### Source excerpt A close friend recently said to me: I'm Copying You Since You're So Effective with respect to how much I tend to get done and I thought I'd elaborate on this a bit since I suspect that why I'm effective isn't always apparent. These aren't really in any order other than the order that I chose to finish them. I suspect they are all pretty important. Ten Reasons Why I Think I'm Effective Get Rid Of Anything That Pisses You Off. To the outside world, I'm a pretty chill person. I try very, very hard to never lose my cool and there's a reason for that - I have a bad temper. One of the things I learned early on about myself is that getting upset ruins my productivity. And so what I do is when I find that something pisses me off, I get rid of it - by fixing it. See my upcoming post on Url Soup for an example. Time is The Only Thing You Have So Do the Math on Everything. I'm a father, a husband and a technologist and I started my first company when I was 19 - and I've pretty much been busy since I was 19. This has always made me very, very aware of just how valuable anyone's time is. I don't waste my time and I hate, hate, hate anything that wastes my time. Just as an example, I used to loathe configuring new laptops. Setting up a new laptop, for a developer, is generally about a week long endeavor until I (or any developer I've ever watched) is really comfortable with it. If you assume that a laptop lasts a developer 3 years and you have 30 years left in your career, that's 10 weeks of your life. Once I did that math then I realized that my figuring out how to configure a laptop quickly and easily was seriously worthwhile and I did (and then I open sourced an example). Find People Smarter than You - And Copy Them. I'd love to tell you that it was my idea for how to configure a laptop automatically but it wasn't. I stole this, shamelessly, from Jeff Geerling; but I did (and do) credit him. One thing I learned early on is that when you don't know what you are doing, finding p ## Running Effective Agile Standup Meetings DevFeed: [Running Effective Agile Standup Meetings]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-11-06T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Agile](), [Self-organizing Team]() Tags: [agile](), [daily](), [effective](), [google](), [management](), [meetings](), [offsite](), [scrum](), [startup](), [team](), [zoom]() ### AI overview A personal account of effective daily Agile stand-up meetings for a team of eight. The recommended practices include starting on time regardless of attendance, scheduling meetings five minutes after the hour, using a consistent meeting URL, and following a simple three-question format. ### Source excerpt So my new gig has moved to doing daily agile standup meetings and while I've done these before, I don't think I've ever seen them done quite so consistently well. And the credit for this goes to my boss, Dave Sifry, who is our lead facilitator. We are a team of 8 people and, so far, we have brought them in at under the scheduled 15 minutes per meeting every time. Here are the techniques that we are using: Start on time. If everyone isn't there, well, the meeting happens anyway. Ideally, if the team lead isn't on time, the meeting happens anyway. Scheduled for 5 minutes after the hour. This allows people in other meetings to make it. A consistent Url. This is the one down side to Zoom - the meeting can't start if the leader isn't present. If we used Google Meet then that wouldn't be an issue. A simple format. A ridiculously simple, fast format: Here's what I'm up to today Here's what I'm stuck on. How can I help anyone else? While I'm generally not a fan of meetings, agile stand ups, done this way, tend to bring developers into line. Even if a developer isn't good with email - or good with text messages - normally they can handle "show up at time X for 15 minutes every day". In closing, while I'm not a huge proponent of heavy weight agile processes (think scrum / agile velocity), I am really enjoying daily stand ups again. Recommended. ## History and effective use of Vim DevFeed: [History and effective use of Vim]() Original publisher: [Read original article]() Published: 2019-07-19T00:00:00Z Content type: article Language: en Sources: [Joe Nelson]() Topics: [Vim](), [Unix](), [systems](), [Command-line interface]() Tags: [article](), [blog](), [effective](), [history](), [intellectual-property](), [legacy](), [plugins](), [posix](), [systems](), [vim]() ### AI overview An article on Vim's historical development and effective use. It traces the editor's lineage from QED through ed, ex, and vi, and encourages readers to study Vim's core functionality, use plugins thoughtfully, and rely less on pre-packaged vimrc files. ### Source excerpt 2019-07-19 This article is based on historical research and on simply reading the Vim user manual cover to cover. Hopefully these notes will help you (re?)discover core functionality of the editor, so you can abandon pre-packaged vimrc files and use plugins more thoughtfully. To go beyond the topics in this blog post, I'd recommend getting a paper copy of the manual and a good pocket reference. ## DNS Security DevFeed: [DNS Security]() Original publisher: [Read original article]() Author: Adam Published: 2019-06-13T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [DNS security](), [Security]() Tags: [cyber](), [deploy](), [dns](), [dns-security](), [easy](), [effective](), [report](), [research](), [security](), [threat-intel]() ### AI overview The Global Cyber Alliance published research by Jay Jacobs, Wade Baker, and the author on the value of DNS security. The article says DNS providers using threat intelligence to block malicious sites can be effective and easy to deploy, citing a report that says DNS security can mitigate one-third of cyber incidents. ### Source excerpt I'm happy to say that some new research by Jay Jacobs, Wade Baker, and myself is now available, thanks to the Global Cyber Alliance. ## Using email as an effective tool DevFeed: [Using email as an effective tool]() Original publisher: [Read original article]() Author: Map Published: 2019-04-16T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [email]() Tags: [effective](), [email](), [philosophies](), [tips](), [tool](), [work]() ### AI overview A product manager shares practical ways to use email for cross-functional communication and engagement. The article recommends including meeting notes and action items directly in emails, recirculating substantially revised documents, using personalized mail merge for feedback requests, and encouraging timely discussion on team emails. It presents the author's reported response-rate experiment while noting that the supplied text is incomplete. ### Source excerpt I send way too many emails in a day. My inbox is very intermingled with my to do list and often represents some form of it. More relevant though is that email is a primary means of how I accomplish work. Being a PM I work cross functionally with other teams (from marketing, to engineering, to sales, to BD, to other product teams) and of course customers. Having to work so cross functionality I've found a lot of hacks I use to be able to better accomplish your goals with email, here is a collection of some of those. Let me be clear, this is not another post about inbox 0, how I swapped to slack. This instead is how I use email to more effectively communicate and get people to engage. In other words it is about making emails more useful, not just getting through them faster. And onto those tips. Don't leave a document in a document Often times I've found folks will collaborate in a document during a meeting or take notes there. After the meeting folks will email the document around, but few seldom actually open. Reasons may be they're not logged in on their phone or it may be they just don't care that much, I'm not really sure. What I do know is that by taking the notes and action items from the doc and including them in the email you will get more people paying attention to them. If you really want to get good at this when there is significant revisions of a work in progress document, re-circulate the updated version via email. Again not just a link to it, but the document itself. Mail merge isn't just for marketing Years ago I sent a company wide request for feedback (to about 120 people). I got less than 3 responses. I ran an experiment the next time I needed the same thing using a mail merge so my same email seemed personal and was from me to them instead of some large alias. I got a response rate of over 45%. Use this wisely... not every email you send needs a response. A broad update can absolutely be to team@, but when you need to get actual feedback and people d ## On being an effective developer DevFeed: [On being an effective developer]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2018-04-07T00:00:00Z Content type: opinion Language: en Sources: [Carlos Becker]() Topics: [Development](), [Frameworks](), [GitHub]() Tags: [articles](), [developer](), [effective](), [how-to]() ### AI overview An experienced engineer shares personal advice on becoming more effective as a developer. The article recommends focused study, understanding problems deeply, fixing issues early, improving the development environment, reducing noise, keeping solutions simple, and practicing. ### Source excerpt Over the years I read several articles on how to be effective, and how the 10x engineer thing is or is not a lie and all that. [Next page]()