aristotel onassis

TL;DR

Pretending to be a polymath and charging you for caring about solving your problems.

+++ With quick content creation.

Intro

When the ideas bucket stops filling up, I got clarity.

Making dividend or market cap race, is no longer a problem.

GoPro overlays? Nah, past

Mechanisms…

Is it time to go back to the real world?

Because software PER is going down to 20, being lower than NASDAQ avg for the first time in history.

Does that tell you anything about the market future expectations also knowing that currently their FCF is also growing?

Conclusions

If you have ever thoughts about Ikigai

or tried to understand the psyc under your decision making

you might have done a TOP/BOT 10 actions life to date.

I did that.

And do you know what was surprising?

That the Bottom 10 moments had one thing in common.

They were all: NOT done this/that in this/that situation

Until now you might have waited for the right moment to start shipping that project.

You dont need to wait anymore:

Consulting Services

Consulting - Service for the Ones with Questions

DIY via ebooks

Distilled knowledge for the ones who want to create step by step

My Current Value Ladder

Active income »> passive income delayed active income.

#git init && git add . && git commit -m "Initial commit: Starting services" && gh repo create jalcocertech-services --private --source=. --remote=origin --push
git clone https://github.com/JAlcocerT/jalcocertech-services

How does my value ladder looks like as of today?

flowchart LR
    %% --- Styles ---
    classDef free fill:#E8F5E9,stroke:#2E7D32,stroke-width:2px,color:#1B5E20;
    classDef low fill:#FFF9C4,stroke:#FBC02D,stroke-width:2px,color:#FBC02D;
    classDef mid fill:#FFE0B2,stroke:#F57C00,stroke-width:2px,color:#F57C00;
    classDef high fill:#FFCDD2,stroke:#C62828,stroke-width:2px,color:#C62828;

    %% --- Nodes ---
    L0("Free Content
($0)"):::free
    L1("AuditMagnet 🛡️
(Web Audit )"):::free
    L11(" Blog/Youtube"):::free
    L12(" ebooks"):::free
    L2("DIY
(Optimization Guides) $"):::low
    L3("Done With You
(Consulting) $$"):::mid
    L4("Done For You
(Full Service) $$$"):::high

    %% --- Connections ---
    L0 --> L1
    L0 --> L2
    L0 --> L11
    L0 --> L12
    L2 --> L3
    L3 --> L4

Quick Content Creation?

If you have watched a vidoe like this one and tinker with remotion like I did.

You are aware that you are one step away to blow social media with spam videos of what you ship.

cd ./remotion-content #get your core offer well defined, then just create promo videos with your defined UI/X

What if promoting your new web app features is already one prompt away?

If code is cheap and you can do videos as a code

Isnt it the math telling you that videos are also cheap now?

The time for courses/watching yt tutorials was 3y ago, now is about building

or…

Whats next?

~1/3 of the year is gone…

where did i wanted to be?

TBD 0426

Where am I?

Keep Doing

1. Following my roadmap for this year, as planned here.

Yea, im not considering Side-Quests26 nor Tech talks.

Oh, also not the monthly selfhosted/homelab recaps.

2. Monthly Life ~ IKIGAI Checks: just that not done in onenote, but in .md

git clone /my-logseq-notes

3. Quiiick PoCs: like the recent iperf3

git clone 

3. Generating random data animated videos & rendres: is probably time to unify these…

git clone /VideoEditingRemotion
cd remotion-cc #ideas.md is a gold mine

make render-multi-invest-short
#To make a different comparison:                                                                                    
 # Nvidia vs Apple vs S&P ETF from 2015
 #python3 scripts/compute_multi_invest.py --tickers NVDA AAPL SPY --start 2015-01-01                                 
                                                                                                                  
# Dividend kings from 2000                                                                                         
  #python3 scripts/compute_multi_invest.py --tickers KO MCD PEP --start 2000-01-01 \                                  
  #  --labels "Coca-Cola" "McDonald's" "PepsiCo"   
make render-dividend-race-short
mpv renders/dividend-race-short.mp4

#make data-f1-telemetry F1_YEAR=2026 F1_ROUND=3 F1_DRIVER=ANT
#make render-f1-telemetry F1_YEAR=2026 F1_ROUND=3 F1_DRIVER=ANT
make data-f1-telemetry F1_YEAR=2026 F1_ROUND=3 F1_DRIVER=RUS
make render-f1-telemetry F1_YEAR=2026 F1_ROUND=3 F1_DRIVER=RUS
#mpv renders/f1-telemetry-2026-r3-RUS-Q.mp4

Full F1 pipeline summary:

F1-A: Telemetry HUD

make data-f1-telemetry F1_YEAR=2024 F1_ROUND=1 F1_DRIVER=VER
make render-f1-telemetry F1_YEAR=2024 F1_ROUND=1 F1_DRIVER=VER

F1-B: ERS Clipping grid

make data-f1-clipping F1_YEAR=2024 F1_ROUND=1
make render-f1-clipping-short F1_YEAR=2024 F1_ROUND=1

F1-C: Championship race

make data-f1-championship F1_CHAMP_YEAR=2025
make render-f1-championship F1_CHAMP_YEAR=2025

F1-D: Sector delta duel

make data-f1-delta F1_YEAR=2024 F1_ROUND=1 F1_D1=VER F1_D2=NOR
make render-f1-delta-short F1_YEAR=2024 F1_ROUND=1 F1_D1=VER F1_D2=NOR

All four share F1_YEAR, F1_ROUND, F1_SESSION — so you can point all four at the same race weekend with consistent
variables. The entire project now has 26 renderable compositions. Want to continue into the macro ideas (16–22), or is there something else you’d like to explore?

  19      --d1       First driver code        (default: VER)                                                     
  20      --d2       Second driver code       (default: NOR)
  21      --session  Session type             (default: Q)                                                       
  22 +    --lap      Specific lap number      (default: unset → fastest lap)                              
  23      --npts     Interpolation points     (default: 500)
  24      --out      TS variable name prefix  (default: f1Delta)

#Usage example for Abu Dhabi 2021 last lap:                                                                         
make data-f1-delta F1_YEAR=2021 F1_ROUND=22 F1_D1=HAM F1_D2=VER F1_SESSION=R F1_LAP=44                             
make render-f1-delta-short F1_YEAR=2021 F1_ROUND=22 F1_D1=HAM F1_D2=VER F1_SESSION=R  

make data-f1-delta F1_YEAR=2026 F1_ROUND=3 F1_SESSION=Q F1_D1=LEC F1_D2=HAM && make render-f1-delta-short F1_YEAR=2026 F1_ROUND=3 F1_SESSION=Q F1_D1=LEC F1_D2=HAM

make data-f1-delta F1_YEAR=2026 F1_ROUND=2 F1_SESSION=Q F1_D1=LEC F1_D2=HAM F1_MAP=1 && make render-f1-delta-short F1_YEAR=2026 F1_ROUND=2 F1_SESSION=Q F1_D1=LEC F1_D2=HAM F1_MAP=1

One of the coolest poles in the recent years:

make data-f1-delta F1_YEAR=2023 F1_ROUND=3 F1_SESSION=Q F1_D1=VER F1_D2=ALO F1_MAP=1 F1_TABLE=1 && make render-f1-delta-short F1_YEAR=2025 F1_ROUND=3 F1_SESSION=Q F1_D1=VER F1_D2=NOR F1_MAP=1 F1_TABLE=1   

make data-f1-delta F1_YEAR=2025 F1_ROUND=3 F1_SESSION=Q F1_D1=VER F1_D2=NOR F1_MAP=1 F1_TABLE=1 && make render-f1-delta-short F1_YEAR=2025 F1_ROUND=3 F1_SESSION=Q F1_D1=VER F1_D2=NOR F1_MAP=1 F1_TABLE=1   

With 14km/h of speed gap in T10 that make the magic happen.

git clone /mbsd

git clone /3Design

Yea… its about time:

/eda-f1
/eda-geospatial

Stop Doing

1. Collaborations with people around vague ideas/projects, those who dont have a clearer (>=) than what I expect before executing my own worthless ideas are to be skipped.

When you have certain volume, this is the kind of thing that you put into a disqualification form.

Have your own ideas checklist in place!

Start Doing

1. As code is cheap and so are videos…

I need to think about the FOSS/JAlcocerTech yt videos rebump - TBC though

2. Data is no longer a full thing, data product is the end to end

Because nobody will pay you to make a group by and filters any more

As you know, agents are coming to the workspace, that includes pbi, looker and whatever

Why should you restrict yourself to existing dashboarding tools?

not talking about streamlit pocs, but full stack data pocs

git clone /poc
#claude
#/usage #as long as you have still tokens

FAQ

The market of time

Some people think that two of the most important factors to predict success are:

1. The RISK that you allow yourselv to take
2. The amount of TIME that you can wait without possitive rewards to keep going in a certain direction (~persistency)
3. The number of times that you ROLL the dice

The good thing about tracking that daily new action since ~wk40y24 for some time is that you can see how non-sense previous things were

Meaning: that those actions were not meant to make yo be closer to where you want to be

This idea might suggest you open questions

Ideas Checklist

https://jalcocert.github.io/JAlcocerT/ideas-to-execution-via-sdlc/#evaluating-business-ideas

https://jalcocert.github.io/JAlcocerT/ideas-and-opportunities-health-check/#business-idea-checklist

This will help you to understand how to disqualify business ideas: https://jalcocert.github.io/JAlcocerT/ideas-to-execution/

Still doing PPTs?

You know that im in love with slidevJS for my tech talks.

But I got to know reminded about python-pptx.

So for the pocs if you were doing slidev or giving a prompt to notebookllm or copilot:

You are outdated.

Take one branded pptx, tell to write the store with the branded slides and move on :)

Or…behave logically like an agent does: swirly requirements = swirly output

for those moments where things are wrong, but people dont agree of the concepts/meaning of whats correct / definitions

“When we say ‘The data is wrong,’ it usually means one of two things: either my code is failing, or we haven’t agreed on what ‘right’ means conceptually.

To build a dashboard we all trust, we must climb this ‘Hierarchy of Right’ for our main metrics.

We will start at the bottom and work up: What is the source, how is it calculated, and most importantly, what business concept does it represent? Let’s begin with the concept.

The Top-Down Hierarchy of “Right”

That is a much more strategic way to handle a room full of executives.

By starting at the Concept, you are speaking their language first (Business Strategy) and only moving toward your language (Code/Data) once the foundation is poured.

If you start with the code, they tune out. If you start with the concept, they take ownership of the result.

Here is the Top-Down Alignment Protocol redesigned for that flow.

The Top-Down Hierarchy of “Right”

Phase 1: The Semantic Concept (The “Why”)

Focus: Business Intent At this level, don’t mention databases or SQL. Talk about the real world.

• The Question: “Let’s ignore the numbers for a second. What is the business event we are trying to capture? For example, when we say ‘Customer Acquisition,’ do we mean the moment they sign a contract, or the moment they pay their first invoice?”
• The Conflict Resolver: “If we have two different views on what an ‘Active User’ is, we don’t have a data problem; we have a strategy gap. Which definition drives our decision-making today?”
• The Goal: A written, plain-English sentence: “A ‘Sale’ is defined as a signed contract regardless of payment status.”

Phase 2: The Logical Formula (The “How”)

Focus: The Mathematical Blueprint Now that you have the concept, translate it into logic.

• The Question: “Now that we’ve defined the event, how do we turn it into a KPI? To get the ‘Net Margin’ we just described, are we subtracting Gross COGS or Net COGS including shipping? Are we excluding internal test accounts?”
• The “Corner Case” Test: “If a customer signs today but cancels tomorrow, does our formula for ‘Growth’ include them or filter them out?”
• The Goal: An agreed-upon formula: $$(Total Revenue - Returns) \times Tax Rate = Net$$.

Phase 3: The Data Source (The “Where”)

Focus: The Source of Truth Identify which system is “The Law.”

• The Question: “Every system tells a slightly different story. For this specific formula, which system is the Golden Record? Is it the CRM (Sales view) or the ERP (Accounting view)?”
• The Accountability Check: “If the CRM says $1M and the ERP says $900k, which one do you want this dashboard to show? We must pick one, or we will always be chasing ghosts.”
• The Goal: Naming the primary database (e.g., “NetSuite is the source for all Revenue metrics”).

Phase 4: The Technical Execution (The Code)

Focus: Verification This is your domain. You only show this if they challenge the first three steps.

• The Statement: “Now that we’ve agreed on the Concept, the Formula, and the Source, my job is purely to ensure the code reflects those three things perfectly. If you ever feel the data is ‘wrong’ from here on out, we can check the code together to ensure it hasn’t drifted from our agreed-upon definitions.”
• The Goal: Technical confidence. You are now just the “translator” of their own rules.

When an executive says “the data is wrong” after this meeting, your response becomes a diagnostic check rather than a defense:

1. “Did the Concept change since our last meeting?”
2. “Is the Formula missing a new variable (like a new tax or discount)?”
3. “Is there an issue with the Source system (human entry error)?” - Maybe sanity checks required by PMOs :)
4. “Is my Code failing to execute the logic?”

90% of the time, the answer is 1, 2, or 3.

By starting at the top, you’ve made them the “Product Owners” of the logic, leaving you to simply be the master of the execution.

When the logic is “wrong,” it’s often because a new business reality exists that hasn’t been coded yet.

The “New Variable” Question: “We agreed on this formula last month. Has a new business factor been introduced—like a new tax code, a seasonal discount, or a ‘friends and family’ rate—that our current math isn’t subtracting yet?”

The “Inclusion” Question: “Is there a specific transaction you’re looking at that should be in this total but isn’t? If so, what ’tag’ or ‘category’ does it have in the spreadsheet that our formula might be filtering out?”

SoloPreneur + AI versus Oldschool

You ikigai points somewhere different?