# opinions Published articles for opinions. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Facilitation Skills for Technical Meetings and Decision-Making DevFeed: [Facilitation Skills for Technical Meetings and Decision-Making]() Original publisher: [Read original article]() Author: Prasad Rao Published: 2026-08-06T17:01:10Z Content type: opinion Language: en Sources: [Big Tech Careers]() Topics: [Tech Careers](), [meetings](), [Development]() Tags: [meetings](), [opinions](), [skills](), [tech](), [tech-careers]() ### AI overview The article argues that facilitation is an important skill for technology professionals working in technical meetings. It defines facilitation as guiding a group toward a decision or outcome and distinguishes it from presenting and chairing. It also explains how facilitation addresses competing opinions, blockers, meeting dynamics, and decision-making. ### Source excerpt How to build the one skill nobody teaches ## Agentic Coding: Bet on the Primitives DevFeed: [Agentic Coding: Bet on the Primitives]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2026-07-31T06:00:00Z Content type: opinion Language: en Sources: [Robin Wieruch]() Topics: [agentic-coding](), [coding](), [React](), [SVG]() Tags: [abstraction](), [agentic-coding](), [ai-coding-agents](), [ai-engineer](), [build-vs-buy-components](), [coding](), [d3-vs-recharts](), [opinions](), [react](), [svg]() ### AI overview The article argues that agentic coding lowers implementation costs enough to make owning lower-level primitives more practical. It describes an experiment comparing D3 math primitives with React-rendered SVG against Recharts for custom charts: Recharts reached most of the result faster, but its remaining customization needs and an animation issue led to more workarounds than the primitive-based approach. ### Source excerpt Agentic coding collapses the cost of implementation labor. Why the rational bet is moving from high-level libraries back to primitives you own. ## Data Modeling's Relevance in Modern Data Engineering DevFeed: [Data Modeling's Relevance in Modern Data Engineering]() Original publisher: [Read original article]() Author: Daniel Beach Published: 2026-07-27T12:20:21Z Content type: opinion Language: en Sources: [Data Engineering Central]() Topics: [data-modeling](), [data](), [Artificial Intelligence]() Tags: [ai](), [article](), [data-modeling](), [opinions]() ### AI overview This opinion article examines whether data modeling remains relevant in modern data work. It presents differing views, notes the longstanding role of relational modeling, and questions why the topic has recently been treated as potentially obsolete. ### Source excerpt was it never alive? ## Opinionated Ktor Services DevFeed: [Opinionated Ktor Services]() Original publisher: [Read original article]() Author: Simon Vergauwen Published: 2026-05-21T00:00:00Z Content type: opinion Language: en Sources: [nomisRev]() Topics: [Ktor](), [Kotlin]() Tags: [2026](), [conference](), [kotlin](), [kotlinconf](), [ktor](), [microservices](), [opinions](), [services](), [talk]() ### AI overview The author describes a KotlinConf 2026 talk about using Ktor and the Kotlin ecosystem to build robust, maintainable, and scalable services. The talk presents the author's opinions on structuring Ktor services and choosing libraries, based on experience with teams. ### Source excerpt Today I gave a talk at KotlinConf 2026 in Munich about "Opinionated Ktor Services". In this talk, I shared my experience and opinions on how to build robust, maintainable, and scalable services using Ktor and the Kotlin ecosystem. ## Google's shift toward AI-first search increases the importance of AEO DevFeed: [Google's shift toward AI-first search increases the importance of AEO]() Original publisher: [Read original article]() Author: Rishabh Goel Published: 2026-05-21T00:00:00Z Content type: opinion Language: en Sources: [Dodo Payments Blog]() Topics: [Google Search](), [Search engine optimization (SEO)](), [Google](), [Artificial Intelligence](), [Large Language Model](), [Website]() Tags: [ai](), [google](), [google-search](), [llms](), [newsletter](), [opinions](), [seo](), [web]() ### AI overview The article argues that Google's integration of Gemini is shifting search from link-based discovery toward conversational, AI-mediated answers. It says SEO alone may no longer be sufficient and that Answer Engine Optimization (AEO), structured information, semantic clarity, and contextual relevance are becoming more important for visibility. It also introduces DualMark, an open-source project intended to make infrastructure more readable to AI systems. ### Source excerpt Google is moving deeper into AI-first search with Gemini, and the discovery layer of the internet is shifting from SEO to AEO. Here's why AEO matters and how we open-sourced DualMark to help. ## Signs That an Engineer May Be Planning to Leave DevFeed: [Signs That an Engineer May Be Planning to Leave]() Original publisher: [Read original article]() Author: Ryan Murphy Published: 2026-04-17T10:02:43Z Content type: opinion Language: en Sources: [The Software Engineering Times]() Topics: [engineering-leadership](), [engineering-culture](), [Code review]() Tags: [engineering-leadership](), [opinions](), [quality](), [team]() ### AI overview The article discusses observable signs that an engineer may be disengaging and considering leaving, including reduced input, less challenge to decisions, lower participation in future planning, and less investment in work quality. ### Source excerpt Most engineers decide to quit long before they tell anyone. Here is what to watch for. ## A quiz matches developers with Replay '26 conference sessions DevFeed: [A quiz matches developers with Replay '26 conference sessions]() Original publisher: [Read original article]() Author: Lauren Bennett Published: 2026-04-07T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [legacy systems](), [AI Agent](), [migration](), [reliability]() Tags: [ai-agents](), [community](), [legacy-systems](), [migration](), [opinions](), [reliability]() ### AI overview This interactive quiz assigns developers a Replay '26 conference path based on their work and interests, including legacy-system modernization, AI workflows, reliability, migration, and architecture. ### Source excerpt Are you migrating haunted legacy systems, wrangling AI agents with opinions, or quietly keeping everything from falling apart? Take the quiz to find your Replay '26 path. ## AI-First Mindset: How AI is Reshaping Teams and Leadership DevFeed: [AI-First Mindset: How AI is Reshaping Teams and Leadership]() Original publisher: [Read original article]() Author: Magda Miu Published: 2026-03-23T08:16:40Z Content type: opinion Language: en Sources: [Magda Miu]() Topics: [Artificial Intelligence]() Tags: [ai](), [ai-first-mindset](), [artificial-intelligence](), [co-intelligence](), [leadership](), [leadership-and-ai](), [opinions](), [personal-development](), [tech-leadership](), [technology]() ### AI overview The author describes developing an AI-first mindset influenced by Co-Intelligence by Ethan Mollick. They advocate working with AI as a thinking partner and inviting it into everyday work, leadership, exploration, and decision-making while keeping humans in the loop. ### Source excerpt AI is everywhere right now: new tools, new opinions, new predictions. And most of it sits somewhere between hype and fear. For me, it did not start with a tool. It started with a book. About two years ago, I kept seeing people I follow on X mentioning the same book: Co-Intelligence by Ethan Mollick. Enough times ... Continue reading AI-First Mindset: How AI is Reshaping Teams and Leadership ## Error Handling in C, Go, Rust, and Google's Absl DevFeed: [Error Handling in C, Go, Rust, and Google's Absl]() Original publisher: [Read original article]() Author: Nevin Zheng Published: 2026-02-28T00:00:00Z Content type: opinion Language: en Sources: [nevzheng]() Topics: [Error Handling](), [Programming](), [Embedded Systems](), [Microcontroller](), [C](), [Go Language](), [Rust](), [Hardware]() Tags: [c](), [embedded](), [embedded-systems](), [error-handling](), [errors](), [go](), [hardware](), [microcontrollers](), [opinions](), [rust](), [stm32]() ### AI overview An opinionated survey of error handling across C, Go, Rust, and Google's Absl. The article traces error recovery from hardware status registers, interrupts, watchdog timers, and resets to modern language features and libraries, with particular attention to firmware, embedded systems, and microcontrollers. ### Source excerpt Errors, opinions, and the rakes I've stepped on. ## How Service Level Objectives Align Developers and Product Managers DevFeed: [How Service Level Objectives Align Developers and Product Managers]() Original publisher: [Read original article]() Author: Anis Khan Site Reliability Engineering is my role Cost optimization is my goal GitHub profile Linkedin profile Published: 2026-02-02T00:00:00Z Content type: opinion Language: en Sources: [Trivago]() Topics: [Availability](), [User Experience](), [data]() Tags: [availability](), [developer](), [engineering-culture](), [maintainability](), [opinions](), [outages](), [performance](), [site-reliability-engineering](), [technical](), [uptime]() ### AI overview This article argues that Service Level Objectives (SLOs) can reduce conflict between developers and product managers by creating a shared, data-driven agreement about reliability and user experience. It explains how a 99.9% availability target creates a 43.2-minute monthly downtime budget and shows how that budget can guide decisions about releasing features versus restoring stability. ### Source excerpt It's a scenario developers relate to a little too well. The product manager always comes with more and more feature requests. They also want to release fast by giving a tight deadline. While you... ## On "AI Brendans" or "Virtual Brendans" DevFeed: [On "AI Brendans" or "Virtual Brendans"]() Original publisher: [Read original article]() Published: 2025-11-27T13:00:00Z Content type: opinion Language: en Sources: [Brendan Gregg's Blog]() Topics: [Artificial Intelligence](), [eBPF](), [systems]() Tags: [ai](), [ai-agents](), [blog](), [ebpf](), [opinions](), [performance]() ### AI overview Brendan Gregg discusses AI performance-engineering agents and "virtual Brendan" systems trained on his publications. He distinguishes agents that interpret flame graphs and eBPF metrics from systems intended to emulate his expertise, and argues that these tools have limited scope, may become outdated, and are difficult to price and evaluate. ### Source excerpt There are now multiple AI performance engineering agents that use or are trained on my work. Some are helper agents that interpret flame graphs or eBPF metrics, sometimes privately called AI Brendan; others have trained on my work to create a virtual Brendan that claims it can tune everything just like the real thing. These virtual Brendans sound like my brain has been uploaded to the cloud by someone who is now selling it (yikes!). I've been told it's even "easy" to do this thanks to all my publications available to train on: >90 talks, >250 blog posts, >600 open source tools, and >3000 book pages. Are people allowed to sell you, virtually? And am I the first individual engineer to be AI'd? (There is a 30-year-old precedent for this, which I'll get to later.) This is an emerging subject, with lots of different people, objectives, and money involved. Note that this is a personal post about my opinions, not an official post by my employer, so I won't be discussing internal details about any particular project. I'm also not here to recommend you buy any in particular. Summary There are two types: AI agents. I've sometimes heard them called an AI Brendan because it does Brendan-like things: systems performance recommendations and interpretation of flame graphs and eBPF metrics. There are already several of these and this idea in general should be useful. Virtual Brendan can refer to something not just built on my work, but trained on my publications to create a virtual me. These would only automate about 15% of what I do as a performance engineer, and will go out of date if I'm not training it to follow industry changes. Pricing is hard, in-house is easier. With a typical pricing model of $20 per instance per month, customers may just use such an agent on one instance and then copy-and-paste any tuning changes to their entire fleet. There's no practical way to keep tuning changes secret, either. These projects are easier as internal in-house tools. Some claim a lot but ## Does AI Get Bored? DevFeed: [Does AI Get Bored?]() Original publisher: [Read original article]() Published: 2025-09-27T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Artificial Intelligence](), [Large Language Model](), [Code](), [GitHub]() Tags: [ai](), [experiment](), [github](), [llms](), [opinions](), [perspectives]() ### AI overview The author experiments with giving AI models extended periods without assigned tasks, sometimes providing tools such as drawing, search, fetching, and time manipulation. They report behaviors they call "collapse" and "meditation," while acknowledging uncertainty about how to interpret the results. ### Source excerpt We always give AI something to do. Chat with us, do tasks for us, answer questions, parse text. What happens when we give an AI nothing to do? I didn't know, so I tried. ## Publishing Content as an Introvert DevFeed: [Publishing Content as an Introvert]() Original publisher: [Read original article]() Published: 2025-06-09T05:56:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Git](), [GitHub](), [Website]() Tags: [certifications](), [git](), [github](), [opinions](), [portfolio]() ### AI overview The article advises an introverted learner to publish networking labs as a portfolio. It recommends organizing lab files in Git repositories, hosting them on GitHub, documenting goals and lessons in README files, and sharing concise links on LinkedIn. The article emphasizes showing progress rather than competing for attention. ### Source excerpt I got an interesting question from a reader. He listened to my podcast with Eric Chou and decided to try to learn in public: Currently, I'm studying for the CCNP ENARSI exam, and would like to start posting my labs to LinkedIn, and perhaps even upload my lab topologies and configs to Git. That's a great idea. I would minimize the LinkedIn part1 and focus on Git: Read more ... ## Why the author questions SOLID and proposes CLARITY principles DevFeed: [Why the author questions SOLID and proposes CLARITY principles]() Original publisher: [Read original article]() Published: 2025-05-05T00:00:00Z Content type: opinion Language: en Sources: [Vasya Drobushkov]() Topics: [Development](), [Programming](), [clean-code]() Tags: [best-practices](), [development](), [opinions](), [programming]() ### AI overview The author argues that SOLID principles are interpreted inconsistently and that rigid application can produce difficult-to-maintain code. The article proposes using a set of principles called CLARITY instead, beginning with consistent abstraction levels. ### Source excerpt A long time ago, when I had just started my journey into programming, development, and engineering, it wasn't easy to find information, and bikeshedding could happen quite often because of that. We read books to gain insights into best practices and learn how to do things correctly. The concepts from the past were usually crucial and provided a great ramp-up to avoid obvious mistakes. Over time, we became flooded with information and opinions. In such an environment, old-time thoughts may even seem better, as they've been tested by time and by many engineers in the field. ## Rant: You Should Have Written a Book DevFeed: [Rant: You Should Have Written a Book]() Original publisher: [Read original article]() Published: 2025-04-17T06:07:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [evpn]() Tags: [blog-post](), [evpn](), [opinions](), [technology]() ### AI overview The author responds to criticism that EVPN videos should have been given away or turned into a book. They argue that producing high-quality videos and presentations takes substantial time, and explain that presentations and downloadable videos let them share more ideas than writing books. ### Source excerpt I apologize for the rant; I have to vent my frustration with people whose quantity of opinions seems to be exceeding their experience (or maybe they're coming from an alternate universe with different laws of physics, which would be way cool but also unlikely). You've been warned; please feel free to move on or skip the rant part of the blog post. Rant mode: ON This is the (unedited) gem I received after making some of my EVPN videos public: Read more ... ## Using feature flags in GraphQL DevFeed: [Using feature flags in GraphQL]() Original publisher: [Read original article]() Published: 2024-09-10T19:42:33Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [GraphQL](), [feature flags]() Tags: [algorithms](), [android](), [apollo](), [blog](), [career](), [compose](), [development](), [engineering](), [feature-flags](), [finance](), [functional](), [graphql](), [growth](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This tutorial explains how GraphQL directives can conditionally include fields in queries. It shows how passing a feature flag to a directive, including with Apollo, can prevent risky new fields from triggering backend requests and causing an entire query to fail. ### Source excerpt I've been using GraphQL in some form or another for a couple of years now, and I have... opinions about it. Opinions notwithstanding, it's a supremely flexible and powerful tool, and I just want to highlight something here that it seems quite a few people don't know about. That something is Directives, which is a way of optionally including fields. But why is this useful? ## Avoid Reading Feature Flags Inside Functions DevFeed: [Avoid Reading Feature Flags Inside Functions]() Original publisher: [Read original article]() Published: 2023-09-29T22:45:18Z Content type: opinion Language: en Sources: [Posts on Adam Bennett]() Topics: [feature flags](), [Development]() Tags: [advice](), [algorithms](), [android](), [blog](), [career](), [compose](), [development](), [engineering](), [feature-flags](), [finance](), [firebase](), [functional](), [growth](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [performance](), [remote-config](), [server](), [software](), [startup](), [startups](), [state](), [thoughts](), [training](), [tutorial]() ### AI overview This article argues that feature flags should be read once and passed into functions or constructors rather than looked up repeatedly. It cites performance costs in hot code paths and unpredictable behavior when flag values change during synchronization with a server. ### Source excerpt I Threaded - made a thread? Posted? Tweeted (can we use that again now)? Whatever - about this earlier but I thought I'd elaborate a little. You do use feature flags, right? You should. If you work with trunk-based development, like everyone does now, you must use feature flags to hide upcoming features. Side note: this is why release notes are so boring now, because features aren't really tied to releases. ## On Waiting DevFeed: [On Waiting]() Original publisher: [Read original article]() Published: 2023-09-14T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Monitoring](), [Tooling]() Tags: [architecture](), [monitoring](), [opinions](), [strategy]() ### AI overview An opinion piece explains the author's decision-making philosophy of waiting as long as possible when decisions lack information. It presents examples involving preview features, architecture, and product design, while emphasizing the need to monitor situations and revisit decisions when circumstances change. ### Source excerpt I was telling a colleague about my philosophy toward making decisions: "wait as long as you can". She replied, "have you heard of the Chinese concept of 无为 (wu wei)?". Uh, no, I have not. She elaborated: ## Migrating Your Design System to Jetpack Compose Part 4: Stakeholder Retro DevFeed: [Migrating Your Design System to Jetpack Compose Part 4: Stakeholder Retro]() Original publisher: [Read original article]() Published: 2023-04-03T11:19:56Z Content type: opinion Language: en Sources: [Posts on Adam Bennett]() Topics: [Design system](), [Jetpack Compose](), [Compose](), [Development](), [Logging]() Tags: [algorithms](), [android](), [blog](), [career](), [compose](), [design-system](), [development](), [engineering](), [finance](), [functional](), [growth](), [java](), [jetpack](), [jetpack-compose](), [kotlin](), [logging](), [metrics](), [money](), [opinions](), [software](), [startups](), [technical](), [thoughts](), [training](), [tutorial]() ### AI overview A retrospective on migrating a design system from Views to Jetpack Compose, focusing on stakeholder communication, measuring internal developer-facing metrics, and presenting progress during a risky refactoring project. ### Source excerpt Featured in jetc.dev. What, praytell, has caused me, nearly two years after I said I would, to finish this blog series? Could the single day of sunlight we had yesterday have triggered something in my Canadian winter-addled brain? Perhaps. A second theory: I've done a lot of interviewing recently, and I've had to talk a lot about projects - what went well, what went not so well, and talk a lot about some of my strengths and failings as a technical lead. And I spoke about this project a lot. ## Year in Review - 2021 Edition DevFeed: [Year in Review - 2021 Edition]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-01-03T08:57:44.331000Z Content type: opinion Language: en Sources: [Eevis Blog]() Topics: [Development](), [coding-community](), [Accessibility]() Tags: [accessibility](), [blog-post](), [developer-community](), [internet](), [opinions](), [review](), [year-in-review]() ### AI overview A personal review of 2021 covering the author's blogging, conference speaking, accessibility work, selected posts, and experiences receiving supportive and hostile feedback in the developer community. ### Source excerpt It's that time of the year again: time to look back and summarize what has happened last year. And when I started listing different things, oh boy, what a year has it been! This blog post will look into some of the highs and lows of 2021 in my life. I also checked what I've added to Polywork and made a collection of 2021 highlights. There are some additional things there, so if you want to have a look, here's the link: 2021 Highlights in Polywork Let's dive in. Blogging So, I started blogging a little over a year ago. First, I was publishing my posts in Dev.to. In the fall, I finally put together my own blog, and since then, I've published the posts first there and then cross-posted to Dev.to. In addition to that, I've published a couple of other blog posts, one in Mimmit Koodaa (a Finnish organization working towards equality in tech) and in my previous workplace's blog. I want to mention a couple of my favorites: Don't Develop Just for Yourself - A Developer's Checklist to Accessibility Published at May 28 Read the post Don't Develop Just for Yourself - A Developer's Checklist to Accessibility This blog post has been part of my talk with the same name, and I've shared it when speaking at conferences. I've also been able to use it at work; I've been constructing checklists for PR templates, and this blog post has been really helpful. Why I'm Not One of the Guys Published at Jul 24 Read the post Why I'm Not One of the Guys This blog post has been one of the hardest to write and publish. When I cross-posted it to Dev, I got tons of comments - many telling me how wrong I am to feel excluded. Some of them were really rude, and I noticed I'm still reluctant to publish posts in Dev after that. In addition to rude comments, I got supportive comments, and I am super happy about them. So thank you all who wrote them! I guess one of the reasons I feel so bad after the comments is that this was the first time I faced this much hatred towards my opinions on the internet. And I ## A response to Martijn's blog DevFeed: [A response to Martijn's blog]() Original publisher: [Read original article]() Published: 2022-08-18T00:00:00Z Content type: opinion Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone-Pro](), [Mobile](), [Linux](), [Development]() Tags: [article](), [community](), [opinions](), [pine64](), [pinephone](), [pinephone-pro]() ### AI overview PINE64 responds to Martijn Braam's criticisms of its treatment of mobile Linux developers and explains why SPI was initially considered for removal from the PinePhone Pro. The company says developer input led it to include SPI despite concerns about past limited use, support problems, and increased cost and sourcing difficulty. ### Source excerpt We rarely, if ever, make responses to blog posts or articles. In fact, there is only one instance that I can think of when we did so. So then, somewhat uncharacteristically, this is a response post to Martijn Braam's blog in which he explains why he left the PINE64 community. Let's get one thing out of the way first: Martijn has done a lot for mobile Linux and PINE64 - he is a valued contributor and a colleague with a good insight into how PINE64 and the Pine Store Ltd operate. I should add that his opinions are welcome just as they have always been. Finally, there is no denying that his leaving is a significant loss to the project and, on a private level, a sad state of affairs for us in the community. If it wasn't clear, we really like Martijn. But this isn't what this blog post is about. Instead, this is a response to the points and concerns Martijn raises. A short summary first: Martijn's blog entry alleges that following PinePhone community editions, and after settling on Manjaro with KDE's plasma mobile as the default OS, PINE64 and the Pine Store Ltd have sidelined developers from other mobile Linux projects. The argument is made that this has hurt development. The example given in the blog post supposes that the community team and Pine Store employees were firmly intent on removing SPI on the PinePhone Pro and coerced not to ship Tow-Boot. He concludes by saying that we no longer listen to the development community. But here is the thing, SPI has been included on the PinePhone Pro due to the input from developers and against our initial intent. The talks concerning SPI were tense, as Martijn mentions in the article, in part because we did approach them with a presumption that we'll inform developers of our plan to drop SPI. I may add that the decision was made among ourselves, without the input of any third parties or partners. The reasoning behind not including SPI on the PCB wasn't motivated by any single project or outside source - it was based on the fac ## Things you can do in Android Studio DevFeed: [Things you can do in Android Studio]() Original publisher: [Read original article]() Published: 2022-06-18T08:38:44Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Android Studio](), [IntelliJ IDEA](), [Dagger](), [Code]() Tags: [algorithms](), [android](), [android-studio](), [blog](), [career](), [code](), [compose](), [copy](), [dagger](), [dependency](), [development](), [engineering](), [finance](), [function](), [functional](), [growth](), [intellij](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [productivity](), [scopes](), [software](), [startups](), [thoughts](), [tooling](), [training](), [tutorial]() ### AI overview A practical list of Android Studio and IntelliJ productivity features, including excluding generated files with Scopes, using scratch files to test ideas, editing multiple lines simultaneously, and accessing clipboard history. ### Source excerpt Based on a recent discussion on Twitter: a list of things that you can do in Android Studio which can make your life much easier. Hide files you don't care about If you work in a project with lots of generated code (e.g.: you use Dagger), you can exclude generated files from searches using Scopes: ## How to Prepare for Data Structures and Algorithms Job Interviews DevFeed: [How to Prepare for Data Structures and Algorithms Job Interviews]() Original publisher: [Read original article]() Published: 2021-11-24T11:00:29Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Programming](), [Algorithms, Complexity](), [Data structures](), [Computer science](), [LeetCode](), [Mobile]() Tags: [advice](), [algorithms](), [android](), [blog](), [career](), [compose](), [data-structures](), [development](), [engineering](), [finance](), [functional](), [growth](), [interviewing](), [java](), [jetpack](), [jobs](), [kotlin](), [mobile](), [money](), [notes](), [opinions](), [remote](), [retention](), [shortage](), [software](), [startups](), [thoughts](), [training](), [tutorial]() ### AI overview This article shares practical advice for preparing for software engineering interviews, especially Data Structures & Algorithms interviews. It recommends actively studying computer science fundamentals, algorithms, data structures and related strategies instead of solving random LeetCode questions without a structured study method. ### Source excerpt In case you weren't already aware, the market right now for software engineers is super hot - it's crazy out there. A combination of the entire world moving online, people burning out of their jobs and a chronic shortage of experienced software engineers means there's never been a better time to see what's on offer. If you want fully remote, better pay and a title change, there are many companies out there willing to give it to you. ## MockWebServer + HTTPS DevFeed: [MockWebServer + HTTPS]() Original publisher: [Read original article]() Published: 2021-09-11T07:06:08Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [configuration](), [Testing](), [Instrumentation](), [JSON](), [Network](), [Firebase]() Tags: [algorithms](), [android](), [blog](), [career](), [compose](), [configuration](), [development](), [engineering](), [finance](), [functional](), [growth](), [harness](), [instrumentation](), [java](), [jetpack](), [json](), [kotlin](), [money](), [network](), [opinions](), [security](), [software](), [startups](), [test-lab](), [testing](), [thoughts](), [training](), [tutorial]() ### AI overview This article describes configuring MockWebServer to serve HTTPS responses for instrumentation tests. It explains the testing context, including acceptance and regression testing, legacy-code verification, network interception, Firebase Test Lab, and JSON responses for edge cases. ### Source excerpt Recently I ran into a fairly niche configuration problem with MockWebServer, where I needed to be able to connect to the server via https. What follows is some notes on the problem and the solution we used - hopefully somebody else finds this information useful and I'm sure there are other solutions which would have worked just as well. [Next page]()