I’ve spent years building and leading hospitality teams that have generated millions in revenue, and now, I help professionals like you tell your unique story on paper.

As an executive resume writer with hands-on experience in operations, I partner with leaders who have well-deserved accolades but struggle to position themselves for the next significant step. 

I've sat on the other side of the table as a hiring manager, so I know what stands out. I excel at transforming your complex, behind-the-scenes accomplishments into clear, compelling narratives that grab attention.

Whether your background is in hospitality, operations, or broader business leadership, my goal is simple: 
To position you as the clear choice for high-profile roles, promotions, and opportunities that truly align with your skills and aspirations.

Specialties include crafting executive and professional resumes, optimizing LinkedIn profiles, and guiding career transitions in the hospitality and operations fields. 

I take pride in working with a select number of clients each month, ensuring a personalized and high-quality experience for each one. If you’re ready to take your career to the next level, let’s connect!

Luke Duggan

People learn how to value your work by how you describe it.
If you minimize, they discount it.
If you generalize, they assume replaceability.
If you’re precise, they see you as credible.

It’s not about sounding impressive or grandiose (see what I did there😊).

It’s about being specific enough that your contribution can’t be mistaken.

📍 What does your language (and body language) teach people about your value?

Luke Duggan 

Executive Resume Writer | Led Multimillion $ Teams, Now I Help You Land High-Visibility Roles

Most senior resumes don’t fail because they lack results.
They fail because they hide judgment.

When you get to a certain rung on the career ladder, hiring leaders already assume competence.

What they’re scanning for is how you decide.

What you prioritize.
What you protect under pressure.
The tradeoffs you’re willing to make.

If your resume only lists outcomes, you look capable. (But at your level, aren't you capable?)

If it shows decisions, you look promotable.

📍 Where could you replace “what happened” with “how you chose”?

There’s a quiet difference between being trusted and being relied on.

Trusted leaders are respected.
Leaders who are “relied on” are leaned on.

They catch what others miss.
They stabilize moments before they escalate.
They absorb complexity so others can function.

But, 

Reliance doesn’t always translate to recognition.

I continue to see leaders who are essential day to day yet invisible on paper. 

Their resumes describe tasks, not gravity.

Careers don’t stall from a lack of contribution; they stall when the contribution isn’t articulated clearly.

📍 Where are you relied on but not fully recognized?

Building a solo business is not a clean upward line.
Some weeks, you do solid work, and nothing moves.
Some weeks, you have good conversations that go nowhere.
Some weeks, you question whether any of this is translating.

What keeps me going is not motivation.

It’s paying attention to what actually creates momentum, even when it’s small.

Which conversations led to follow-ups?
Which posts led to profile views?
Which work did people ask questions about?

Progress shows up quietly before it shows up financially.

📍 If you’re building something on your own, what’s the smallest signal you’ve noticed that tells you you’re not wasting your time?

When asked during an interview, “Tell me about a challenge you handled.”
Some provide a detailed answer that details the effort.
Others reveal leadership.

When you talk about what you did, you sound busy. We are all busy, right?

When you explain why you chose the solution when you had a split second to decide, you sound credible.

Authority shows up in decisions:
•	what you didn’t escalate
•	what you corrected early
•	what you chose to carry yourself

📍 What decision do you avoid naming directly when you tell your story?

Most leadership growth isn’t dramatic.
It’s directional.

What you reinforce.
What you let slide.
What you finally name instead of carrying quietly.

Either way, those choices compound.

Over time, they tell people exactly who you are to work for.

📍 If someone watched your last 30 days, what direction would they see? Firm, fair, and consistent or wishy washy when it matters most?

High performers often believe one thing will take care of everything else:
“If I keep delivering, the right people will notice.”

Sometimes they do.
Often times, they don’t.

However, consistency builds trust. Trust that you can handle the task at hand.

But trust alone doesn’t create opportunity.

I’ve seen impressive leaders stall not because they lacked results, but because they never articulated what those results actually required:

The judgment calls.
The tradeoffs.
The moments they stepped in when things could’ve gone sideways.

When you don’t name that work, others fill in the blanks, and they usually fill them in smaller than reality.

This isn’t about self-promotion.
It’s about accuracy.

If your work carries weight, it deserves to be described with the same care you put into doing it.

📍 What part of your contribution have you been assuming others “just know”?

Most professionals don’t undersell themselves on purpose.
They do it to stay comfortable.

They describe outcomes without decisions.
They mention results without pressure.
They talk about teams but not the weight they carried.
It sounds humble.
And yet it reads unclear.

Hiring decisions aren’t made on effort.
They’re made on trust.

And trust is built when someone can say:
•	Here’s what I saw
•	Here’s the call I made
•	Here’s what changed because of it

If you don’t give your work its proper shape, others will shrink it to something safer, and smaller.

📍 Where are you choosing comfort over clarity in how you talk about your work?

I don’t measure progress by how much I produce anymore.
I pay attention to resistance.

When decisions need less explaining.
When conversations don’t require backtracking.
When the work moves forward without constant justification.

Misaligned work creates drag, even when it looks productive.
Aligned work feels quieter, but it moves with purpose.

Lately, I’ve been noticing what no longer needs force.
That’s how I know I’m heading in the right direction.

📍 Where has your work started to feel clearer instead of heavier?

Most LinkedIn profiles are clean.
Polished.
Technically correct.
And completely interchangeable.

If someone finishes reading your profile and can’t clearly say:
• who you help
• how you think
• what problem you solve

you’re not positioned for the role you want, so you end up blending in.

Professionalism gets you seen.
But being specific gets you remembered.

📍 What do you want a decision-maker to know about you after 30 seconds?

Most people stall because their story stops evolving.
Their scope expands.
Their judgment deepens.
The risk they carry increases.

But they keep describing themselves the same way they did years ago.

That needs to change.
Hiring decisions are made on what is seen.

If your story hasn’t kept pace with your responsibility, your value gets misread.

Growth doesn’t require exaggeration.
It requires translation.

📍 Where has your responsibility increased without your narrative catching up?

Anyone can describe effort.
Leaders describe decisions.
What they chose.
What they ruled out.
What they took responsibility for when there wasn’t a clear answer.

Effort shows involvement.

Judgment shows readiness.

📍 What decision do you soften when it should be owned directly?

I used to say yes based on capacity.
If I could do the work, I would take the work.

What I pay attention to now is different.

I notice whether the work requires:
•	constant clarification
•	urgency without direction
•	emotional smoothing to keep things moving

That kind of work looks productive on the surface.
In reality, it drains judgment and hides impact.

The work that moves me forward doesn’t need performance.
It needs thinking, ownership, and decisions that hold.

📍 What kind of work keeps you busy but makes your contribution harder to see?

Most senior resumes don’t move forward because they don’t help the reader assess risk.
Hiring decisions at this level are about trust in the face of uncertainty.

On this sheet of paper, can this person show me they can:
make judgment calls without a playbook?
protect standards under pressure?
absorb complexity without creating noise?

Yes, most resumes demonstrate- “Here’s what I was responsible for.”

Effective resumes show: “I can be trusted to make the right decisions when it mattered.”

That sight difference can move someone from the “qualified” to the “shortlist” pile.

📍 Does your resume describe your role, or your reliability?

You’re reliable.
You deliver.
People trust you when things go wrong.
And slowly, that becomes your ceiling, and you’ve plateaued.
Because you’ve become operationally indispensable yet professionally invisible.

I see this when clients are:
•	people doing director-level thinking
•	carrying director-level consequences
•	while presenting themselves as “support” on paper

At this level, careers don’t stall from a lack of impact.

They stall because impact isn’t framed clearly enough to be valued.

Working harder won’t fix it.
Naming the work you’re already doing will.

📍 Where might your reliability be hiding in your leadership?

There’s a moment in interviews where the tone shifts.

It’s not when someone lists achievements.
It’s when they explain a decision.

Why did they choose one path over another?
Did they make a decision that was best for the business?

That’s when interviewers stop evaluating competence
and start evaluating judgment.

And judgment is what senior hiring is really about.

📍 What decision would immediately change how someone perceives your leadership if you owned it clearly?

How you describe the importance of your work (the task at hand) trains people to value it.

Generalize it, and it sounds too common.
Minimizing it discounts its impact.
Stay precise, and they feel the weight of what you want to accomplish.

Don’t make your own leadership voice invisible.

📍 Where could sharper language change how your work is taken seriously?

This year, I’ve stopped trying to measure progress by how motivated I feel.

Instead, I keep a simple weekly log:
What did I actually ship?
Who did I help make a decision?
What moved forward because I was involved?

No dashboards. No goals wallpaper.
Just a notebook and a pen at the end of each week.

It’s less inspiring, but it’s nice to measure (and see) the momentum.

📍 What would show up in your notebook if you tracked outcomes instead of effort?

Consistency helped me build trust early in my career.
It stopped helping when expectations changed.

At a certain level, showing up is assumed.

What people look for next is how you think.

If your value isn’t clearly articulated,
others decide for you, and they’ll get it wrong. Promise.

📍 Where might people misunderstand your contribution right now?

Most professionals don’t hit a wall because they lack skill.
They hit it because their story is outdated.

Their expertise has grown.
Their judgment is sharper.
The decisions they make carry more weight.
But they’re still describing themselves the same way they did years ago.

That disconnect comes across: 
In interviews.
When promotions become available.
In how seriously they’re taken.

📍 Where is your experience ahead of the way you currently explain it?

Chris Johnson, CPA, CCIFP

🌟CEO at CJ CPAs | Construction & 401k Auditor | Tech-Savvy Innovator 🌟

With over a decade of experience in the world of accounting, I'm dedicated to helping businesses in the construction industry and those requiring 401k plan audits navigate their compliance needs in the most effective and efficient way possible. 

In my role at CJ CPAs, my focus is on providing exceptional client service, fostering strong relationships, and utilizing innovative technology to deliver outstanding results.

I'm passionate about staying up-to-date with industry trends and embracing new technologies to create more efficient and effective solutions for our clients.

Outside of crunching numbers and analyzing financial statements, I'm a husband to my amazing wife Kimberly, father to three beautiful children, a jiu-jitsu hobbyist, tech enthusiast, avid YouTube learner, and a proud Texan. 

I'm always eager to connect with fellow professionals and share insights and ideas, so feel free to reach out!

Chief Executive Officer

There is a 100% chance that within 10 years, a $10,000,000,000+ company will exist with under 20 employees. That company does not have over 100 employees today.

I love everyone massively and have such a deep 
admiration for anyone going through 
the human experience.

But each individual person carries a communication tax.

And that tax can get really high.

To the point where you need whole departments 
whose entire job is just handling the 
communication overhead.

We've grown accustomed to this.
We see it as just the way business works.

But it doesn't have to be.

New age companies will pay a fraction of the
 communication tax that legacy organizations carry today.

Fewer people. Less friction. More focus.

The companies that figure this out 
first won't just be leaner.
They'll be unstoppable.

🌟CEO at CJ CPAs | 401k Auditor | I'm "button-clicking" the whole dang thing 🌟

The majority of my administrative tasks might be automated by the end of the weekend 🤯🤯🤯 Last year, I recorded over 1,500 Looms. Every business process I do. All of them.

Last night, a little Friday night fun, I analyzed 
all 1,500 and created a mental map. 

(Think Obsidian, except I just built my own.)

The map detailed everything. 
Then I analyzed the map.

My entire business boils down to 92 automations.

I grouped all 92 by value.

• $10/hour tasks
• $100/hour tasks
• $1,000/hour tasks
• $10,000/hour tasks

Over 60 were $10 tasks.

Over 60.

As we speak, automations are running that 
are creating the automations to put every 
single one of those on autopilot.

Read that again.

Automations building automations.
(Then making a recap to keep you in the loop 🤣🤣🤣)

All those administrative low-dollar items are 
just handling themselves now. Freeing me 
up to put real time toward $10,000, 
$100,000 per hour tasks and beyond.

1,500 recordings.
92 automations.
60+ on autopilot.

LFG

Holy sheesh!!! We ARE at launch MVP. I have created what I believe to be the most impressive software in the accounting industry ever made (primarily because its what I have always wanted 😅😅)

Still working through kinks. 
But I'll keep at it until it's inarguable.

And if you disagree?

It'll be like arguing with a microwave.
Trying to tell it that it doesn't make your food hot.

I'll keep trimming code.
Keep making it more efficient.

But this is what launch MVP looks like.
And this is just the beginning.

Here's some other stats: 
(all of this is this year)
- 2,600 commits 
- 400+ issues. 
- 400+ PRs
-  6.5 million total lines, 5.7 deletions (i know that doesn't particularly mean anything but interesting for a guy that 6 months into formal software development)
- a completely separate "road map" repo that probably have a half million lines itself 😅😅

Id you have expertise in ANYTHING, you are this ☝️☝️☝️👇👇👇away from redefining your industry.  

Every day it will get easier for the 
next person to do what i did. 

"Be your name Buxbaum or Bixby or Bray 
or Mordecai Ali Van Allen O'Shea, 
you're off to Great Places!
Today is your day!
Your mountain is waiting.
So...get on your way!"

ABSOLUTELY WILD week. Here's what I built/learned.  

- I built a automation thats run everyday at 5am that
rates my previous days work (see below). 
Gives me an Awesome rating,  speed,
regression, code quality and more. 
Runs a meta trend analysis, track. 
Awesome to see incredible speed 
and rapid improvement in code quality 

- A regression fix under pressure. 
Supabase redirects. Cloudflare security rules. 
Email deliverability across Microsoft domains. 
Not glamorous. Absolutely necessary.

- A staging environment separation strategy with 
my new Director of Information Security. 
Dev. Staging. Production. Three lanes. 
No more testing on live data. 
Lesson learned the hard way.

- A DOL audit response tracker. 
The Department of Labor is inspecting one of our plans.
We built a system to track every document request, 
map every response, and stay ahead of the auditor.
(you better believe my system is going to export DOL ready to review files!!)

- A client onboarding experience. 
By Friday, the same client who watched things break 
on Wednesday AND Froday was back on a call. 
3rd times the charm! 
Got access, got all.the needed docs.. 
She did the compliance questionnaire.
 
- Made a knowledge base search tool for my team.
Built off 1,600+ Loom training videos. 
I told my team to use it once an hour. 
And paid out an impromptu $200 bonus the the
person with the most pings over the rest of the...15 in 4 hours!!!

I did.this because the goal isn't 
just to build technology.
It's to build people who can use it.

Here's what I learned.

- Shipping fast means breaking things. 
And breaking things in front of clients 
means you better be the kind of 
person who fixes them faster.

- Your team watches how you handle failure 
more closely than how you handle success.

- The difference between a 50-hour audit 
and a 5-hour audit isn't just automation. 

It's every painful Wednesday that taught 
you what not to deploy without 
a staging environment.

- Building a company and building a 
family run on the same fuel. 
Show up. 
Stay honest. 
Fix what's broken. 
Celebrate what works.

Took a break from automating the accounting world today.  Kimberly and I are doing whole 30 this month sooo I made us an app.

> It comes preloaded with all the whole 30 compliant foods. 
> Has recipes, cook times 
> has a weekly food calendar where you click what meals you want to eat. Cool thing is that automatically updates you "grocery list" for what to buy 
> you can verbally add what you ate and it automatically pulls in the macro and calorie info into your daily log. 
> I've got alot of venison and orxy soo had it preload alot of receipts ready to go. 

I'm going to start tracking what I eat in the easiest way possible. 

I literally just talk to my phone if I put food in my mouth and it does it for me 🤣🤣

I'm not going to give this much more thought for a while but 2 things that would be cool is to 

> finish out the grocery list to automatically add to our weekly HEB pickup list 

> put the template on github for free for other people to use. 

Crazy easy Sunday Funday build

I worked off a laptop and side monitor for over a decade #auditorlife Things look a little different these days 😅

I was a bad/so-so auditor for 8 years. Then finally got pretty dang good at it!!...... to then become a bad/so-so software developer 🤣🤣

Very hopeful this path ain't as long 😅😅

There's ALOT of skills from being an
auditor that translate really well though!

The last 2 days have been ABSOLUTELY incredible from a build perspective on my primary automation software.

Heads up. I actually haven't posted much 
about my primary build. It's usually side 
projects and little things I'm learning.

This post is related to the BIG one. 

What went well:

• There has been an incredible confluence of skill and understanding that has allowed me to implement changes at a pace I couldn't have imagined. Insane to think that in September we built everything in VBA and now I've made enterprise-grade software 🤯🤯🤯

• Well over 100 commits

• Long-lasting bugs getting cleared out

• 2 clients have been exposed to the process. Each time we learned and made the changes.

What has sucked** Woops I mean the growth lessons 😅😅

• Software development basics. I have had lessons in the basics. Staging not set up right. Merging to main. Conflicting branches. Humbling stuff.

• I was building features and clearing review comments via Claude Code. Going fast. So I thought, why don't I tackle 5 at once!

I had all the Claudes pointed at one repo.

It was taking a while and the results 
were kinda weird so I started watching closer.

They were spending half their time fighting over branches 🤦‍♂️🤦‍♂️

And that's the story of how I learned about working trees 😂😂

I've still been moving fast but this 
took 3-4x longer than it should have.

Additional advice would be GREATLY appreciated!!

Thursday morning, I didn't know what end-to-end testing was. Fast forward to Friday night. I had 2 straight days where I learned an INSANE amount. And now have 31 automated checks running on every single pull request in our codebase.

Every time code is submitted, 
before it can be merged, it goes through:

• 9 Security Scans. 
AI-powered code review, vulnerability scanning, 
secret detection, dependency auditing. 
If a password accidentally gets committed, 
it gets caught. 
If a security hole exists, 
it gets flagged.

• 6 Code Quality Checks. 
Linting, formatting, style enforcement. 
The grammatical errors of code, caught automatically.

• Unit and Integration Testing. 
Does each function actually do what it's supposed to do?

• 3 End-to-End Tests. 
A headless browser launches, simulates a 
real human clicking through the entire application, 
and verifies everything works. Creating accounts. Uploading documents. If any critical workflow breaks, 
the code is blocked from merging.

• Post-Deploy Smoke Tests. 
After deployment, did the car start? Do the blinkers work? 
Simple checks that catch catastrophic failures immediately.

• 5 Database Safety Checks. 
Migration validation. Schema sync. 
Making sure code that depends on database 
changes doesn't go live before those changes are applied.

• 4 Deployment Automations. 
Auto-deploy to dev, production, and sandbox 
environments with preview links on every pull request.

72 hours. 
From not knowing the words to having 
the entire pipeline built and running.

This happened because I an INCREDIBLE 
SecOps expert walked into our office 
on Thursday and taught me
concepts that changed everything.

The Testing Pyramid. 
The Racetrack Guardrails. 
Chesterton's Fence. 
The Smoke Test.

He explained that AI agents will silently break things 
they don't understand the purpose of. 

And that end-to-end tests are the 
guardrails at every turn of the racetrack. 

You build them as you discover crashes. 
And over time, the entire track is protected.

I went from VBA in September to 
enterprise-grade CI/CD in March.

I did not know what an API was 4 years ago. 
Don't ever let anyone tell you what you can't learn.

Oh my goodness it worked!!!!!! I have been having a TIME with getting my sign-off logic working right in my software.  For every audit step we have this logic
> Every person has an open and closed color.  
> if assigned to a person it should show open color. if they sign off it should show closed. 
> if a higher person signs off their complete color takes over 
> all of thay activity is logged and viewable at the audit step , engagement, user and full activity levels. 

Doesn't seem like it should be that hard but this thing has been like playing wack a mole for months. 

Last week I learned about end to end testing and bolstered my vocabulary around integration testing.  

I put alot of time into it and it was prettt scary because you don't get the same immediate validation you do from front ens vibe coding.  

Front end vibe coding is cake walk. 
"I want the button to be blue.....wtf its not blue, make it blue" 

I've gotten better at back vibe coding and found some areas to gain comfort in the path and increased visibility towards checkpoints. 

But all of these checks felt pretty blind. 
You have to go pretty deep until you get that same 
"front end validation" 

So I dug deep into my prompt engineering bag id tricks and I've probably put 15+ hours in vibe coding tests 

Which is ALSO scary because I could just "doing the thing", which if this were to fail, id have to go back to "doing the thing " anyways. 


Well it all came together!!!
Over an hour 4 PRs all starting resolving. 
Checks started clearing. 

I hoped onto the live site and I couldn't believe it.
Everything was working!!!!!!!!!! 

I literally cried. 
It was incredible 🥹🥹🙌🙌

I've got one of my guys poking it from every angle tomorrow so we'll find out if thats ACTUALLY true.

But I mean we are pretty much at MVP!! 🤯🤯🤯

We've already added a few clients to validate the process. 
And I'm thinking we are about ready to start adding 10 at a time to see what breaks! 😬😬

But after we prove all that out, this thing going to be ready to ROLL!!!

10 days ago, I didn't know what end-to-end testing was.
Today: 15 phases. All green. 25+ PRs merged.

10 days.

Error handling. 
Unit tests. 
E2E infrastructure. 
Accessibility. 
Component splitting. 
Documentation. 
Service layer. 
State management. 
Observability. 
Deployment gates. 
Security scanning.

All of it. Done.

I wonder what the next 10 days has in store.

I am so proud of my construction team!! The level of quality work they are producing right now is so impressive 👏👏🙌🙌❤️❤️

In 6 years of running an audit department (3  
running my CPA firm), I have never 
received this level of quality work 
without my heavy involvement.

For the last 3 years, I've tried to delegate 
responsibilities to others so I can focus
on things that only I can do. 

And I haven't been able to do ao successfully
For a myriad of reasons. 
Learning how to delegate. 
Learning how to hire correctly. 
Learning how to manage and help others grow. 
And retaining high standards on quality.  

If it weren't for my dang standards on quality,
I could have got out of the weeds a whole lot
faster 😅😅😅

While mainting high quality standards (above our regulated standards) has some really good 
aspects, it has also kept me heavily involved.

I've worked to build this firm while ensuring our 
quality floor stays above my standards. 
(which is above industry standards)

And in our construction department I haven't 
successfully been able to get out of 
anything beyond a manager role. 
(Really, more of an experienced senior role 
on the majority of our construction engagements.) 

This year we've had some transitions. 
People stepping into new roles.

Last week, something landed in my inbox.
Draft financial statements.
On a job I hadn't been keeping a close eye on.
And the weird thing was they looked REALLY good.

I tried not to let myself get too excited.

Then yesterday, I did a live review of the file with the team. Took about 90 minutes.

ZERO critical issues.

The feedback I was able to provide was very nuanced. 
So many of our processes were excuted ao extremely 
well, the feedback I provided was able to get 
into thedetails that REALLY elevate 
comprehensionand quality. 


Then today, I got a WIP schedule 
back from one of my staff. 

This is their first year ever working on WIP schedules.

It rolled to the penny!!!

For anybody who knows what that means. 
I don't think I would have believed it was 
possible that someone with less than 
a year of experience could roll a 
WIP schedule to the penny.

(Took me probably 8 years before I was able to do that 😅) 

Oh my goodness.
I am so amazed. 
And so grateful for that I get a front seat 
to watch amazing people do amazing things ❤️

It takes a really long time to get 
the right people in the right seats.

But man. I'm just so proud of my construction team.
Shout out to them!!

Excited for what the future holds 🚀🚀🚀

You are 3,000 commits away from a completely different life. Better git to merging!
.....I promise I'm still an accountant 😂😂

What's the most powerful skill you can be working on right now that nobody is talking about?
Your vocabulary.

And I'm not saying grab a dictionary and go to town.

I'm talking about understanding the words and 
the way those words are used by experts in 
whatever discipline you want expert output in.

Here's why this matters right now.

I am an expert in auditing. 15 years. 
I know all the words, all the concepts. 
And I have been absolutely mind blown by 
the results I can get out of a large 
language model when I apply 
my expertise to it.

But here's the interesting thing.

Anyone who roughly knows the words and 
can use those words in the right order 
can get the same thing 
out of it that I can. **

Read that again.

You don't need my 15 years of audit experience 
to get my results out of a large language model.

You need to know how to effectively use 
your words and have it sound 
the same as my words.

The logic is simple.

I have found that if I communicate with 
large language models using vocabulary 
that other experts use, I don't need to sign 
up for their 15 years of experience.

I can skip those.
And still get incredible results.

Improve your vocabulary.
Study how experts in your target field communicate.
Learn the words. 
Learn the order. 
Learn the context.

That's the shortcut nobody is talking about.


**to note, you can also get yourself in trouble 
if get too far ahead of your skis. 
But its not as scary as you think. 
Get an expert for that last bit! 
The cycle of reflecting with an expert at a 
high level makes your vocab and 
comprehension even 
better even faster!

Calling all devs!! What would your world class End-to-End prompt look like?? Heres mine!! Anything you'd tweak?? "You are building a production CI/CD pipeline. Implement these GitHub Actions checks on every PR:

SECURITY: AI code review (Claude PR Review, required gate), CodeQL semantic vulnerability analysis, Semgrep SAST, Trivy filesystem scanning, TruffleHog secret detection in code + git history, npm dependency audit for supply chain attacks.

CODE QUALITY: Biome JS/TS linting, Python quality checks, ShellCheck for bash scripts. All with smart path-filters so irrelevant PRs skip cleanly.

TESTING: Vitest unit/integration tests. Playwright E2E full suite + Launch Blocker gate (simulates real users creating accounts, uploading docs, verifying data). Post-deploy smoke tests against live environments.

DATABASE: Supabase migration validation, pending migration detection, schema sync across dev/staging/prod.

DEPLOYMENT: Auto-deploy to dev, prod, and sandbox environments. Preview URL comments on every PR.

RULES: Never run E2E tests against production. Use GitHub Secrets with environment-specific prefixes. Every bug found becomes a regression test. AI agents get cloned repo folders to prevent branch conflicts. Index all GitHub Actions for tracking (01-claude-review, 02-codeql, etc.).

THE STANDARD: If an AI agent silently breaks backend logic while the frontend looks fine, these tests catch it. That's the whole point. Build fast. Never regress."


31 checks. 
Feel free to steal it and change the world 🌎 ❤️

#dev #ai #prompt #fullstack

10 minute weekend build. I added a "fast food" tab to our family app that shows all the whole 30 compliant options.  Not only that, click any items and it shows you "How to Order" too! 

We are doing whole 30 this month. 
With 3 kids and alot of family and personal 
goals, we do fast food. 

The decision fatigue is resolved. 
Need some fast food?
Want to stay compliant?
Open the app, and it shows exactly what to do.

I am a different kind of cat. And life is just crazy.
I have a 10-year goal to understand the actual formula and math behind the Many Worlds Interpretation of quantum physics.

The Schrödinger equation:
iℏ ∂/∂t |ψ(t)⟩ = Ĥ(t) |ψ(t)⟩

That's the thing. 
That's what I want to deeply understand.
Zero clue what any of that means today 😂

This week, I'm out at my son's 
gymnastics class with my other kids 
And I forgot a diaper for my youngest. 
She had a messy, messy diaper.

So I'm walking outside with my older daughter, 
talking to her about how sometimes 
we need to ask for help.

As I'm standing there, a man walks out 
with the same exact stroller we have.

Ask and you shall receive.🙌🙌

I asked if he had a diaper and 
some wipes I could borrow. 
Dad helping out a dad. 

Afterwards, we start talking about what we do.

He's a theoretical physicist by trade.🤯

Starts explaining the Many Worlds Interpretation to me. Tells me if I truly want to understand it, I should 
start with path integrals.

Walks me through concepts to help
build up my understanding. 

Just making an easier path for me to dive into.

I'm at my son's gymnastics class.
With a dirty diaper.
Asking a stranger for help.
And the stranger turns out to be a
theoretical physicist who starts teaching
me the exact thing I've set a 10-year goal to learn.

Life is crazy.
What an amazing journey we get to 
experience with this whole thing.

I'm staying focused on the task at hand. 
But Ooooooh man I am pumped to continually 
learn how this whole thing ACTUALLY works

If I can consistently have 5-hour stretches like the one I just had, this world is gonna look a whole lot different. Really soon.
Backstory.

We had a call with a new client today. 
New clients are inherently harder than repeat clients. 
We just got our stuff kicked in by a different 
new client recently, and I did not want our 
team to experience that pain again.

So I was well primed to think 
about the problem differently.

Two team members were on the call. 
After it ended, we kept talking 
about the best ways to handle it. 

One thing led to another, 
and through some really effective 
prompts, our problems were solved.

The team headed out for the day.

And I couldn't help but wonder how far it could go. 

Quickly.

TLDR: REALLY FN FAR!!!

So I started a triple build.

Same instructions. 
Same goal. 
Three tools building simultaneously.

• Claude in Excel: 90 minutes iterating. Fed it a massive prompt. It kept forgetting and regressing. Good output but hitting a ceiling. 3 hours in and still didn't finish.

• Shortcut AI: Made something pretty epic. Still working on it. Rated itself 3.2 out of 10 against what it could be. But the output was already solid.

• OpenClaw: The real winner 🏆 

I had them create their own test 
data and let them iterate on it

For the past 3 to 4 weeks, I've been 
slowly working on OpenClaw. 

Set it up in a secure, separate environment. 
Told it to go work on itself. 

Got so frustrated with it a few 
weeks ago that I took 2 weeks off.

Came back about 10 days ago. 
It was starting to grow up.

About 2 hours into today's build, 
I gave OpenClaw the same task.

In about 10 minutes, it returned something 
that blew all the others out of the water.

Absolutely incredible.

It just took my words that came from my ideas 
and nailed it. And right now, I have it going 
and iterating on itself and improving.

Now you might be asking about data. 
About security.

For each of these tools, I told them to build their 
own test data. 

Full test data. 
And they did it. 
I don't have to expose anything. 

Nothing. 
It tests itself on its own test data. 

And at the end of it, I have 
templates I can take any direction I want.

The last 5 hours have been mind-blowing.

And we're just getting started.

I've got an incredibly simple self-evaluation metric to help you identify if you're on the path to getting it in this AI revolution. "Are your problems today the same problems you had a year ago?" 

That's it.

If you're interacting with large language models and your 
problems have fundamentally changed, you're moving. You're growing. 
You're on the path.

If they're the same problems, you're not.

As I evaluate myself, some of my 
problems are worlds different. 

Eons beyond where I was a year ago. 
The problems I'm solving today didn't 
even exist in my vocabulary 12 months ago.

And then there are other problems I have that, 
as I sit here and reflect, are clearly the 
same ones I had a year ago.

Which means in those areas, I'm not getting it.
Super powerful reflection tool.

I'm personally going to spend more time 
on this one to see what I can uncover.

Asking for technical help! Any advice would be greatly appreciated. i'm looking for recommendations on how to best programmatically create consistent pdf outputs? see below for the juicy details! 

- I'm building a GAAP financial statement generator. 
> I thought it would be super easy......its hasnt been 😅😅
> I'm close. And at the same time a million miles away
> The little misses are so bad an below my standard I could not hand this off to someone elae 

Here's what's happening.

• I coded the entire financial statement output in HTML. And it's like playing whack-a-mole. I fix one thing and a number doesn't tie somewhere else. I fix that and something I thought was locked in from the beginning breaks.

• I don't know if that's just part of the process or if there are tips, tricks, and architectural decisions I could be making from the start to lock the logic in place so I'm not constantly chasing cascading breaks.

• Formatting. Spacing, alignment, page breaks. I can address each one individually and those fixes stay in place. But the logic breaks are killing me.

• I'm not even sure HTML is the right output format. The most consistent financial statement output I've ever experienced is Word and Excel. Every person I know who has built a financial statement generator uses Word and Excel to get that locked-in consistency.

So my real questions are:

• Is there a way to architect this from the start so the logic stays locked in place?

• Is there something better out there? A format or framework that gives you the automation and flexibility of code with the pixel-perfect consistency of Word and Excel?

• Or is the answer just to build the automation pipeline and output to Word and Excel anyway?

If you've solved this or even wrestled with it, 
I'd love to hear from you.

Building in public means asking for help in public too ❤️
#help #savemeeeee #audit #publicaccouting

taplio

The Battle

Luke Duggan

Chris Johnson, CPA, CCIFP

Followers

Posts

Engagements

Likes

Performance ScoreLuke Duggan's LinkedIn Performance

Performance ScoreChris Johnson, CPA, CCIFP's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Luke Duggan

Chris Johnson, CPA, CCIFP

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Luke Duggan's LinkedIn Performance

Performance ScoreChris Johnson, CPA, CCIFP's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreLuke Duggan's LinkedIn Performance