Engineering Problem-Solving Techniques

Explore top LinkedIn content from expert professionals.

  • "The Prompt Engineering Playbook for Programmers" My latest free write-up: https://lnkd.in/g9Kxa7hG ✍️ The difference between a vague "fix my code" request and a well-crafted prompt can mean the difference between generic, unhelpful advice and precise, actionable solutions that accelerate your development workflow. My "Prompt Engineering Playbook" has actionable strategies to help you get the most out of AI coding assistants. If you missed it, or need a refresher on crafting prompts that deliver real results, now's a great time to dive in. Inside, you'll find: ✅ Effective patterns (role-playing, rich context, iterative refinement) ✅ Smart debugging strategies with AI ✅ AI-assisted refactoring for better code ✅ Building new features step-by-step with your AI pair programmer ✅ Common anti-patterns to avoid (and how to fix them) Here's what separates developers who struggle with AI from those who use it effectively: 🎯 The Foundation Rich context: Never just say "fix my code" - specify language, framework, error messages, and expected behavior Clear goals: Replace "this doesn't work" with "this function should return a sorted array but returns undefined" Break it down: Don't ask for entire features - iterate from skeleton → logic → optimization ⚡ Refactoring game-changer ❌ Vague: "Refactor getCombinedData function" ✅ Specific: "Refactor to eliminate duplicate fetch logic, parallelize requests, and optimize data merging. Preserve individual error messages." Result: AI delivers parallel fetching, efficient data structures, and maintains debugging capability. 🎭 Secret weapon: role playing "Act as a senior React developer reviewing this code for performance issues..." "You're a TypeScript expert - refactor following modern best practices..." This simple technique dramatically improves response quality and specificity. ⚠️ Avoid these anti-patterns - Overloaded prompts ("build a complete app") - Vague success criteria ("optimize code" vs "reduce memory usage") - Ignoring AI clarifying questions - Inconsistent style across conversations 💡 Bottom line With AI, the more context and direction you provide, the better your results. I hope it's a helpful read. #ai #programming #softwareengineering

  • View profile for Armand Ruiz
    Armand Ruiz Armand Ruiz is an Influencer

    ai @meta

    207,885 followers

    Anthropic’s “Prompting 101” is one of the best real world tutorials I’ve seen lately on how to actually build a great prompt. Not a toy example. They showcase a real task: analyzing handwritten Swedish car accident forms. Here’s the breakdown: 𝟭. 𝗣𝗿𝗼𝗺𝗽𝘁𝗶𝗻𝗴 𝗶𝘀 𝗶𝘁𝗲𝗿𝗮𝘁𝗶𝘃𝗲. You don’t write the perfect prompt on the first try. You test, observe, refine. Just like any other product loop. 𝟮. 𝗦𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗺𝗮𝘁𝘁𝗲𝗿𝘀. The best prompts follow a playbook: - Start with task + tone context - Load static knowledge into the system prompt - Give clear rules and step-by-step instructions - Show concrete examples - Ask the model to think step-by-step - Define structured output 𝟯. 𝗗𝗼𝗻’𝘁 𝘁𝗿𝘂𝘀𝘁 𝘁𝗵𝗲 𝗺𝗼𝗱𝗲𝗹, 𝘆𝗼𝘂 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗱𝗲𝘀𝗶𝗴𝗻 𝗳𝗼𝗿 𝗶𝘁. In the first version, Claude hallucinated a skiing accident. Only after adding context, rules, and constraints did it produce reliable results. You wouldn’t let a junior analyst guess on regulatory filings. Don’t let your LLM do it either. 𝟰. 𝗧𝗵𝗲 𝗽𝗿𝗼𝗺𝗽𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗶𝗻𝘁𝗲𝗿𝗳𝗮𝗰𝗲. In traditional software, interfaces are buttons and APIs. In GenAI, the interface is language. Your prompt is the program. Most teams still treat prompts like notes in a playground. High-performing teams treat them like production code. That's why in our IBM watsonx platform, prompts are assets just like code or data. 👉Access the video tutorial here: https://lnkd.in/gUdHc2uy ________________________ ♻️ Repost to share these insights! ➕ Follow Armand Ruiz for more

  • View profile for Kevin Donovan

    Empowering Organizations with Enterprise Architecture | Digital Transformation | Board Leadership | Helping Architects Accelerate Their Careers

    24,512 followers

    🎭 𝐏𝐞𝐫𝐜𝐞𝐩𝐭𝐢𝐨𝐧 𝐯𝐬. 𝐑𝐞𝐚𝐥𝐢𝐭𝐲: 𝐈𝐓 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐬 Perception: “Just someone drawing boxes and lines on diagrams.” Reality: ✅ Master of Complexity – Designs solutions that balance business goals, tech constraints, and future needs ✅ Stakeholder Whisperer – Aligns executives, developers, vendors, and users (all with competing priorities) ✅ Requirements Detective – Captures functional and non-functional needs: security, scalability, compliance ✅ Legacy Wrangler – Modernizes decades-old systems while keeping the lights on ✅ Portfolio Curator – Oversees an ecosystem of apps for integration, cost control, and lifecycle health ✅ Change Leader – Prepares organizations for transformation without chaos ✅ Quality Custodian – Guards performance, security, cost, usability, and future maintainability ✅ Endless Learner – Keeps pace with AI, cloud, and regulation shifts ✅ Documentation Guardian – Ensures architectural decisions stay transparent In short: • It’s not just diagrams. • It’s shaping the digital backbone of an enterprise—through clarity, foresight, and relentless collaboration. 💡 Save this for when someone says, “So… you draw diagrams all day?” 😉 👇 What’s the most misunderstood part of YOUR role as an architect? --- ➕ Follow Kevin Donovan 🔔 ♻️ Repost | 💬 Comment | 👍 Like 🚀 Join 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐬’ 𝐇𝐮𝐛 – for resources, insights, and community. Subscribe 👉 https://lnkd.in/dgmQqfu2

  • View profile for Shreyas Doshi
    Shreyas Doshi Shreyas Doshi is an Influencer

    Startup advisor. ex-Stripe, Twitter, Google, Yahoo.

    252,096 followers

    The ability to create clarity when there’s no shortage of chaos, opinions, and competing priorities is a rare skill. In any reasonably competent company, this skill alone will help take you quite far, fairly quickly. Concretely, this means creating clarity on the main problems, clarity on the right solutions, and clarity on the action plan & priorities. Very few people can do this well even though most people possess the intelligence necessary to do it. This is because most people in the workplace have been conditioned to add more information, sound more clever, satisfy more stakeholders, and feign more precision & certainty than is possible. Few understand that clarity in a chaotic situation can only emerge from subtraction, never from addition. Clarity comes from communicating what stands out as most important, why it is most important, how it will be achieved, and last but not the least, giving people a way of thinking about why it is okay, even great, that we aren’t doing All The Other Things.

  • View profile for Jeroen Kraaijenbrink
    Jeroen Kraaijenbrink Jeroen Kraaijenbrink is an Influencer
    333,368 followers

    There are always situations in which you need to communicate fast and clearly. Especially in a crisis, in new situations, or when there is time pressure. The STICC protocol helps you achieve this. The STICC Protocol was developed by psychologist Gary Klein as a tool for managing the unexpected. STICC stands for: Situation, Task, Intent, Concerns, Calibrate and is a technique for productive communication about what to do when you face a new, unexpected situation. This is what it means: S - Situation = Here’s what I think we face. The leader summarizes how they see the situation, problem, or crisis at hand. T - Task = Here’s what I think we should do. The leader explains their plan for addressing the situation, problem, or crisis at hand. I - Intent = Here’s why I think this is what we should do. The leader explains the reasons why they think this is the best way of addressing the situation, problem, or crisis at hand. C - Concerns = Here’s what we should keep our eyes on. The leader mentions possible downsides or future consequences of the solution suggested to be taken into account as well. C - Calibrate = Now talk to me and give me your views. The leader asks others in the team to give their feedback and viewpoints, and especially invites them to disagree and add. This technique helps you in managing pressured situations in three ways: First, once something unexpected happens, it helps to develop appropriate responses. The five steps are aimed at discussing with a team what to do in cases that are not familiar. Through its focus on concrete action, on gathering different viewpoints, and on speed, the STICC protocol is a quick way to take appropriate action in new situations. Second, in step 4 (Concerns), you open up the discussion for further uncertainties and other changes that may follow. In this way, you mentally prepare people that there will always remain uncertainties. This helps in developing a crisis-ready mindset that is not only helpful in the current crisis, but also in the next. Third, the fact that a constructive dialogue takes place also facilitates communication and mutual learning. Even though the leader brings the suggestions here, it is the team together that comes to a solution. And while doing that, they learn together and from each other in an open and adaptive way, which helps further prepare them for future crises. My advice: use STICC whenever you have to communicate fast and clearly. === Follow me or subscribe to my Soulful Strategy newsletter for more: https://lnkd.in/e_ytzAgU #communicationtips #agile #teamexercise

  • View profile for Zach Wilson
    Zach Wilson Zach Wilson is an Influencer

    Founder @ DataExpert.io | Join my Nov 16th Analytics Engineering Cohort! DM me for more details

    535,258 followers

    Building Data Pipelines has levels to it: - level 0 Understand the basic flow: Extract → Transform → Load (ETL) or ELT This is the foundation. - Extract: Pull data from sources (APIs, DBs, files) - Transform: Clean, filter, join, or enrich the data - Load: Store into a warehouse or lake for analysis You’re not a data engineer until you’ve scheduled a job to pull CSVs off an SFTP server at 3AM! level 1 Master the tools: - Airflow for orchestration - dbt for transformations - Spark or PySpark for big data - Snowflake, BigQuery, Redshift for warehouses - Kafka or Kinesis for streaming Understand when to batch vs stream. Most companies think they need real-time data. They usually don’t. level 2 Handle complexity with modular design: - DAGs should be atomic, idempotent, and parameterized - Use task dependencies and sensors wisely - Break transformations into layers (staging → clean → marts) - Design for failure recovery. If a step fails, how do you re-run it? From scratch or just that part? Learn how to backfill without breaking the world. level 3 Data quality and observability: - Add tests for nulls, duplicates, and business logic - Use tools like Great Expectations, Monte Carlo, or built-in dbt tests - Track lineage so you know what downstream will break if upstream changes Know the difference between: - a late-arriving dimension - a broken SCD2 - and a pipeline silently dropping rows At this level, you understand that reliability > cleverness. level 4 Build for scale and maintainability: - Version control your pipeline configs - Use feature flags to toggle behavior in prod - Push vs pull architecture - Decouple compute and storage (e.g. Iceberg and Delta Lake) - Data mesh, data contracts, streaming joins, and CDC are words you throw around because you know how and when to use them. What else belongs in the journey to mastering data pipelines?

  • View profile for Aakash Gupta
    Aakash Gupta Aakash Gupta is an Influencer

    Helping you succeed in your career + land your next job

    328,376 followers

    I’ve spent 15+ years writing Product Requirements Documents (PRDs). Give me 5 minutes, and I’ll show you how to write a great one: — SIX STAGES OF PRD LIFECYCLE Before we dive in, remember this: the PRD is not one and done. If your PRD is static, your team will build the wrong thing. A great PRD evolves over six stages to keep teams aligned and focused. Here’s how: — STAGE ONE - Aperture → Align leadership & team on direction This is the starting point where leadership and product teams decide what’s worth exploring. → It’s often just a speck of an idea — a pain point, market shift, or competitive insight. → The goal is not to finalize anything but to agree on where to dig deeper. — STAGE TWO - Discovery → Identify the right problem to solve Now, the team goes deep into problem exploration. → User research, data analysis, competitive benchmarking, everything to validate that the problem is real. → Often, this stage results in a one-pager that outlines why this problem matters. — STAGE THREE - Define → Shape and scope the problem This is the final convergence on the problem statement. → The team nails down key constraints, trade-offs, and non-goals. → You answer questions like: What’s in scope? What’s out? — STAGE FOUR - Design → Explore potential solutions Finally, we move from problem space to solution space. → Brainstorming, prototyping, and early technical feasibility checks happen here. → You don’t pick just one solution yet, you explore different options. — STAGE FIVE - Deliver → Finalize and commit to a single solution Now, the team is ready to lock in the approach. → Engineers define technical specs. → Designers finalize user flows and edge cases. → PMs ensure cross-functional alignment. — STAGE SIX - Live → Launch, track results, and iterate The product ships… but the PRD isn’t done. → Measure adoption, impact, and user feedback. → Analyze what worked, what didn’t, and what needs iteration. — TWO - PRD Process: Problem Space vs. Solution Space A great PRD is built in two phases: ONE - Problem Space → Define the ‘What’ Team Kickoff → What problem are we exploring? Planning Review → Leadership alignment on the problem’s scope. XFN Kickoff → Gather cross-functional input before locking in the problem statement. TWO - Solution Space → Define the ‘How’ Once the problem is crystal clear, this phase ensures you solve it the right way. Solution Review → Align on user experience, edge cases & tradeoffs. Launch Readiness → Lock in implementation details, success metrics & rollout plan. Impact Review → Iterate based on insights. — In a nutshell… A great PRD doesn’t just tell what to build, it also inspires teams to build the right thing. — And if you want to learn how to write the PRDs with examples, template, and step-by-step, go here: https://lnkd.in/e-nzkAwX

  • View profile for Brij Pandey

    AI Architect & Engineer | Agentic systems, AI Harness, AI infrastructure

    742,477 followers

    The moment an AI agent can take action, your engineering responsibilities multiply. You have to decide what it knows, what it can access, how it recovers, and when it must stop. That’s why I find it useful to think about AI systems engineering across seven layers: 1. Foundation Model → Capability Choose a model for the actual task. Understand its strengths, limitations, and failure modes. 2. Prompt Engineering → Instructions Define the task, constraints, examples, and expected output. Make success specific enough to evaluate. 3. Context Engineering → Information Assemble the evidence, memory, and tool results the model needs for its next decision. Relevance and freshness matter. 4. Harness Engineering → Runtime Build the environment around the model: tools, permissions, execution boundaries, state, and logs. 5. Loop Engineering → Feedback Design how the agent acts, checks results, and retries. Give it clear stopping conditions and an escalation path. 6. Graph Engineering → Coordination Connect the work through dependencies, branches, and handoffs. Decide what runs in parallel and what must wait. 7. Ontology Engineering → Shared Meaning Define the entities, relationships, and business rules the system uses. What exactly counts as a customer, an approval, or a completed order? These areas overlap. Many difficult failures happen where they meet. An unclear business definition can look like a model error. A tool timeout can look like a reasoning failure. A missing stop condition can turn a useful retry into an expensive loop. Before changing the prompt or switching models, identify where the failure actually lives. That diagnostic skill is becoming a core part of AI engineering. I’ve brought these seven layers together in this September 2026 edition. Use the diagram to review your architecture and spot the decisions that still need an owner. Which layer needs the most attention in the AI systems today?

  • Most engineers still default to riprap. This pour replaces 70 cm of rock with 20. What you’re looking at is a fabric-formed concrete revetment — a double-layered woven geotextile pumped full of fine-aggregate concrete on site. The fabric is the formwork. Once cured, the geotextile becomes secondary; the concrete shell does the work. Under ASTM D18.25/D35.05 these are formally called GGFM (geotextile grout-filled mattresses) or FFCR. The pillow-like surface you see isn’t decorative — those are filter points that bleed pore-water pressure out of the embankment, which is what keeps the lining from blowing off the slope during drawdown. Why crews on canals, river banks, and bridge abutments are switching: → Thickness: typically 20–50 cm of concrete vs 60–80 cm of riprap for the same flow regime → Underwater install: no cofferdam, no dewatering — fabric is laid, then pumped → Conformity: the mattress drapes over irregular subgrade; no shaped formwork, no shotcrete crew → Material logic: fine-aggregate concrete pumps cleanly and resists abrasion better than gap-graded rock The trade-off most people miss: it’s a rigid lining once cured. Settlement, undermining at the toe, or a missed filter point will crack a panel the same way it cracks any concrete slab. Subgrade prep is the whole job. What’s your call — fabric-formed concrete or riprap when the bank is unstable and dewatering isn’t an option?

  • At Amazon, we would often spend months working on a single paragraph of the PR/FAQ for a new product idea. This was the "problem paragraph". Done well, it could lead to a successful product. Done wrong, it will lead to failure. Here is how to write a successful problem paragraph: The “problem paragraph” defines the customer problem you’re solving. Without this, you will build a product that doesn’t address a customer pain point. It shows whether you truly understand your customer's needs, not just your company’s capabilities. To write this paragraph, start by precisely identifying the customer segment that will be served by your product. Great products are built for specific people with specific needs. For instance, designing a car for single urban professionals under 35 differs significantly from designing for suburban families with three kids and a dog. If you think your product is for everyone, you’re mistaken. A strong way to begin your paragraph is: “Today, [customer segment] has [problem], which they currently solve using [methods A, B, and C]…” Next, quantify the problem: → How large is the segment? (e.g., 17 million households) → What methods do they use? (e.g., 45% use A, 25% use B, 30% use C) → What are the tradeoffs? (e.g., speed, cost, quality) Here’s an example for a hypothetical robot vacuum product: “Today, 15 million busy urban and suburban professionals earning between $100,000 and $200,000 struggle to find the time and energy to keep their homes clean. Approximately 30% of these households use traditional vacuuming, which requires up to 2 hours per week. 55% hire a cleaner at a minimum of $50/week, and 15% use robot vacuums that cost $600 plus $100/year in maintenance, while leaving behind up to 30% of dust and dirt.” This problem paragraph quantifies the customer problem in terms of money, time, and other metrics where possible (in this case, the dust and dirt left behind). The problem should always be quantified; otherwise, how can you assess the potential value of a product that solves it? Well-defined customer problems are built on data-based insights. Insights are gleaned from swimming in data and metrics. This includes customer usage metrics, process or operations metrics, user interviews, demographic data, customer feedback, customer support data and anecdotes. The more data-based and specific your insight, the more accurate and helpful your problem paragraph will be. This is why the process can take months. However, distilling these quantified insights into a single paragraph gives you the best chance at building a truly useful product. At Amazon, this paragraph was always the most debated section in a PR/FAQ. This is because getting the problem wrong is the worst mistake you can make in building a product. Everywhere else, you can pivot. But if the problem is incorrectly diagnosed, nothing else matters. (cont. in comments)

Explore categories