Skip to content

Instantly share code, notes, and snippets.

@eonist

eonist/hard_problems.md

Last active January 18, 2026 14:23
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save eonist/b74e659aa17c07bc9c8c3b112e977ec9 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save eonist/b74e659aa17c07bc9c8c3b112e977ec9 to your computer and use it in GitHub Desktop.
Download ZIP
hard_problems.md
Raw
hard_problems.md

hard problems

This is how I solve bigger code challanges. Like really complex features.

  1. I asked for feedback on legacy code. pros and cons.
  2. i made my idea for v2 how it should work etc. then i asked the AI to plan it out in detail in a plan.md doc.
  3. i asked the ai to make readme doc for the feature before coding it.
  4. then i gave the ai all of these docs, and asked it to code it. it took 2h for it to finish.
  • four ais did this simultaniously. 2 in pplx. 1 cursor 1 cline. about 20$ each.
  • When you have 4 branches with solutions. Then you ask 1 AI to cherry pick from each. Picking the best code etc.
  • You start by asking the AI to review all docs so far. and you chat with it about focus areas, reach goals, phased dev etc.
  • The goal is to find the sweet spot. Plan and code up the final solution with best of the best from the 4 branches
  • the 2 branches that pplx coded has PR descriptions. the cursor and cline branches does not have prs. but you can ask pplx to make prs with comprehensive descriptions based on the branches. Store these pr descriptions as .md doc
  • the plan.md doc also serves as a compass for when the AI compres context etc
  • Cline will generate a task list.md for big jobs, reference this task list and original plan, if they AI strays
  • You can also code the final solution in parallel. Cline and cursor, in different clones of the repo. And then just pick the best end result. Its overcocking things a bit, but sometimes alt versions are golden. sometimes an AI will stray and build too much because it got trapped in a rabbit hole. Also looking at two final solutions, if they do not diff too much, you know that the AI didnt stray.
  • Making the plan for the final soulition can be done in 4x matrix parallel. 2 local agents (seperate clones, because we check out branches). 2 remote agents. because you dont write any code, you just read and present a plan. then you can store all plans and make 1 plan from these 4 plans.
@eonist
Copy link
Author

eonist commented Nov 16, 2025

Task:

  • Checkout all 4 branches one by one and look at the solutions that has been added to these feature branches
  • read the PR descriptions. stored as markdown. these are great at describing what the feature branches contain
  • your task is to create a plan of what our "final solution" will contain, Which parts you want to use from each of the 4 feature branches. try to analyze pros and cons with each feature branch. also consider using pieces of code from the legacy solution. see code paths in the bottom of this document. we should call the tool simply "export", and
  • once we have the plan we should discuss it. we might want to add more to the plan and we might want to remove things. then we will store the plan as a .md doc and we will reference this when we begin building our "final solution" export tool.
  • when we make the plan and also when we code it, we can always checkout branches to get code etc, just stash or commit working dir before we do that etc, so we dont lose our inprogress work etc

Idea:

More around the idea in detail: _proposals/advance-export/advance-export-idea.md

  • Basically you just design your website in desktop and mobile frames in figma.
  • And if you want themes like light/dark mode etc. you just make aditional frames for that.
  • Also works for multi page websites. so you just add your needed matrix of frames select them and the export feature compiles it all into tidy css and clean html
  • 🚀 WYSIWYG -> Code

Branches:

Cherry pick from these 4 feature branches:

get_advance_code, export_advance_4, feature/export-advanced-mvp, feature/export_advance

PR overviews of the 4 branches:

These are birds eye view of what the feature branches contain and what they do:

_proposals/advance-export/pr_export_advance_4.md
_proposals/advance-export/pr_export_advance.md
_proposals/advance-export/pr_export_advanced_mvp.md
_proposals/advance-export/pr_get_code_advance.md

Relevant feature documents

planing, ideation, pr-descriptions, readme-sketches, feature plans, legacy code feedback

_proposals/advance-export/

Legacy code

these has alot of useful code that can be copied.

  • plugin code: src/plugin/src/commands/code_enhanced
    — server code: src/server/commands/figma/export_enhanced

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment