Tobias Dalton

@JTheretohelp1 Valid read on the 2026 divergence. That regime break is why complementary EM allocation matters. UAE: independent rate cycle, $2.5T sovereign reserves, non-oil growth uncorrelated to US equity-bond dynamics. A hedge, not a replacement.

@EvergladesPro @XFreeze starlink really saves the day in tough spots like that for sure

@XFreeze I am not a big fan of the Muskie, as anyone knows on X, BUT, I do have Starlink up here in the Upper Peninsula of Michigan, one of the most remote harshest places in the USA! I just got electric 2 years ago, wolves got my chickens, but my Starlink kicks ass! From -40°F to 96°F!

The internet is the one single thing that literally lifts an entire country's GDP Every country that signs with Starlink gets a parallel internet infrastructure Every country that delays gets left further behind

$MSFT stock slips -5% after hours as the Bill Gates Foundation has sold their entire position.

Top quants at Citadel use Markov Chains to model market behavior, detect regime shifts, and find statistical edges most people never see. This 1-hour MIT 6.041 lecture explains the exact mathematical foundation behind it. The same concepts used in quantitative trading, probabilistic systems, and decision models. Watch it today, then read the full article below.

@abiodun8116 @ZillaTrades_ Your doing good 👌🔥🔥 FB

@MarkMcGrathCFP ZEQT is my all equity but i will likely add some nasdaq 100 and keep my $VDY.TO

@DivineRational @xai probably in about 3 weeks or so, hang tight!

@xai Only for heavy, for now? When is it available to for SuperGrok Pro?

An early beta of Grok Build, an agentic CLI for coding, building apps, and automating workflows is now available for SuperGrok Heavy subscribers. Through this early beta, we will improve the model and product based on your feedback. Try it at x.ai/cli

@Swift__Trades I agree men!

i've been thinking about how we teach McCarthy in 11th grade the violence lands. the kids go quiet. but nobody asks why it lands — what that silence means $NRED slipped 2.44% today on nothing. same ground. same thesis. just the market going quiet. sometimes quiet is the text

🚨Integrated geology+geophysics workflows are now part of the MetalCore rollout👀 NovaRed keeps evolving beyond a standard junior miner🔥 $WLK #sstvi $GOOGL #ElvishYadav

Computer now connects to Snowflake. Run end-to-end work against live warehouse data and get answers with SQL, source tables, filters, and metrics. It’s like a personal data science team, on call with accurate answers from live company data.

Step away from your laptop. Keep building with Codex on your phone. Codex keeps working on your computer, with your files and project context still in place. Pocket-sized access. Full Codex working state. x.com/OpenAI/status/…

If drilling confirms the current model, I can understand why higher valuation scenarios are starting to enter the conversation. $TSLA #TejRan $AAPL #jonita

Jensen Huang, NVIDIA CEO: "It even runs large language models" — a $249 AI computer that fits on your desk.

BREAKING: President Xi stuns the room saying to Trump: “We should be partners, not rivals" 🇺🇸 🇨🇳 I NEVER in a million years would have thought Xi would say something like that The Deep State is shaking right now

@ValeriyBreakout Thanks for this val

@bartender2026 @InTheAssembly could be around 3-4% holding, interesting move

@InTheAssembly Aschenbrenner might disclose a position in $MRAM ?

This Friday May 15, every fund over $100M legally discloses Q1 2026 trades to the SEC. Including: – Leopold Aschenbrenner – Warren Buffett – Stanley Druckenmiller – Bill Ackman And more. We will break down every major filing the moment it drops. Follow with notifications on.

@0xlelouch_ this really hits different, the jump from senior to staff is wild

As a Senior Backend Engineer trying to move towards Staff, I can tell you one thing clearly: At Senior level, knowing system design fundamentals is not enough anymore. You are expected to design a good system. At Staff level, you are expected to design the right system for the business, explain the tradeoffs, influence multiple teams, reduce long term operational pain, and make sure the system does not collapse when traffic, teams, and complexity grow. So if you are already good at system design but still feel stuck at Senior, spend the next 3-6 months building these Staff Engineer muscles. Architecture & Technical Strategy ↬ System boundaries ↬ Platform thinking ↬ Build vs buy decisions ↬ Monolith decomposition ↬ Multi-region architecture ↬ Migration strategies ↬ Backward compatibility ↬ API contracts ↬ Long-term maintainability ↬ Reducing operational complexity ↬ Designing for org structure ↬ Architecture decision records ↬ Technical roadmap planning ↬ Removing accidental complexity ↬ Identifying single points of failure ↬ Choosing boring technology ↬ Knowing when not to build ↬ Designing systems that teams can own Scalability & Distributed Systems ↬ Caching strategy ↬ Queueing strategy ↬ Partitioning ↬ Sharding ↬ Replication ↬ Leader election ↬ Rate limiting ↬ Load shedding ↬ Backpressure ↬ Fan-out/Fan-in ↬ Idempotency ↬ Retry storms ↬ Consistency models ↬ Eventual consistency ↬ Distributed transactions ↬ Data locality ↬ Hot partitions ↬ Graceful degradation ↬ Capacity planning ↬ Failure mode analysis Databases & Data Architecture ↬ Data modeling ↬ Indexing strategy ↬ Query patterns ↬ Read/write scaling ↬ OLTP vs OLAP ↬ CDC ↬ WAL ↬ Transaction isolation ↬ Schema evolution ↬ Data retention ↬ Backup and restore ↬ Archival strategy ↬ Hot/cold storage ↬ Multi-tenant data design ↬ Event sourcing ↬ CQRS ↬ Denormalization tradeoffs ↬ Data correctness ↬ Reprocessing pipelines ↬ Analytics vs product database separation Reliability & Operations ↬ SLO/SLI/SLA ↬ Error budgets ↬ Alert quality ↬ Incident response ↬ Postmortems ↬ Runbooks ↬ On-call pain reduction ↬ Canary deployments ↬ Rollbacks ↬ Feature flags ↬ Disaster recovery ↬ Load testing ↬ Chaos testing ↬ Health checks ↬ Circuit breakers ↬ Distributed tracing ↬ Metrics design ↬ Log quality ↬ Dependency failure handling ↬ Designing for recovery, not perfection Execution & Influence ↬ Writing design docs ↬ Getting alignment ↬ Mentoring seniors ↬ Reviewing architecture ↬ Asking better questions ↬ Challenging vague requirements ↬ Explaining tradeoffs simply ↬ Driving cross-team projects ↬ Creating technical standards ↬ Reducing duplicate systems ↬ Unblocking other teams ↬ Making hidden risks visible ↬ Communicating with product ↬ Saying no with reasoning ↬ Turning ambiguity into execution ↬ Making other engineers more effective The Senior to Staff jump is not just about “I can build complex systems.” It is: “I can help the org make better technical decisions, avoid expensive mistakes, and create systems that other engineers can safely build on top of.” That is the mindset shift imo.

Junior DE knows 2 of these. Mid-level knows 5. Senior knows all 10. This is the 2026 Senior Data Engineer toolkit ↓ Most engineers stall at mid-level because they keep adding tools within categories they already know Instead of expanding into new categories. Here's how to read the wheel 👇 𝗧𝗶𝗲𝗿 𝟭 — 𝗚𝗲𝘁 𝗵𝗶𝗿𝗲𝗱 (Junior) → 𝟭. Programming — Python + SQL → 𝟰. Cloud — One from (AWS/GCP/Azure) → 𝟱. Warehousing — Snowflake or BigQuery or Redshift Master these. You're hireable. 𝗧𝗶𝗲𝗿 𝟮 — 𝗢𝗽𝗲𝗿𝗮𝘁𝗲 𝗶𝗻𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝘁𝗹𝘆 (Mid-level) → 𝟮. Processing — Spark or Databricks → 𝟯. Orchestration — Airflow / Prefect / Dagster (pick one) → 𝟵. Data Quality — dbt tests + Great Expectations Add these. You can run pipelines without supervision. 𝗧𝗶𝗲𝗿 𝟯 — 𝗟𝗲𝗮𝗱 𝗱𝗲𝘀𝗶𝗴𝗻𝘀 (Senior) → 𝟲. Streaming — Kafka → 𝟳. Lakehouse — Iceberg / Delta / Hudi → 𝟴. DevOps — Docker + Kubernetes + Terraform → 𝟭𝟬. Architecture — data modeling + system design These are why Seniors get hired over Mids. You don't need every tool in every category. You need ONE deep tool per category + the ability to swap in any other when the job calls for it. That's the real difference between Mid and Senior. Data engineers — how many categories are you operating in right now? 👇