Tom Tao

Digital Analytics Professional @Trader, Certified Web Analyst @DAAorg. Husband, father, sports fan(NBA, Tennis, NFL), reader(non-fiction)

[Andrej Karpathy @karpathy]

We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:

Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:

Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better:

Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better:

Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work!

In summary:
- As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
- Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.

[Dave Kline @dklineii]

https://t.co/XNvycK71o0

[NiKITa🇺🇦 @NiKiTa_32156]

伊朗電視台轉播「打碼奧運」

[Google Analytics @googleanalytics]

💡Missed the webinar? Catch up on the Google Analytics 4 Durable Foundations session. Learn how GA4 is getting ready with strong first-party data foundations and Google AI-powered solutions to enhance durable measurement and activation. Watch On Demand! → https://t.co/ufLFjCY4z4

[Trung Phan @TrungTPhan]

Lily Zhang’s parents get a Gold medal in Asian Parenting

[Jesse Pujji @jspujji]

Jeff Bezos on stress, where it comes from, and how to deal with it.

[David Vallejo @thyng]

I'm trying to understand why TikTok Pixel intercepts all `fetch` requests on a site, even those not meant for TikTok. It seems they just doing a reqs count log https://t.co/J7fJXfNXUq() ...

🧐

[Tom Tao @icecafe]

@DashHuang tennis 的话 建议使用@SwingVisionApp 手表还可以测挥拍速度

[Michael Drogalis @MichaelDrogalis]

Things I wish I knew as a 22 year-old engineer:

1. Software engineering is mainly about people, not code. Technical expertise will only take you so far.

2. There's a time to hack together a house of cards and a time to build a masterpiece. Learn the difference.

3. Prioritize simplicity, not cleverness. Most code is read many more times than it's written.

4. Sales, marketing, and other departments do equally important work to engineers. Respect them.

5. The most important engineering ideas are timeless. Don't obsessively learn the latest tech.

6. Engineers who can write and make complicated ideas simple have outsized influence. The IDE isn't the only place to do valuable work.

7. Code only matters if it solves a real problem for a real person.

[Gergely Orosz @GergelyOrosz]

Got to give it to the GitHub team.

While most "AI developer tools" are aiming for a workflow that takes a spec and (much later) generates code (with no developer input): GitHub created a developer-driven, AI-assisted, workflow.

The developer is in control, the full cycle:

[王局志安 @wangzhian8848]

今天是劳动节，我和同事还在工作。我觉得人生最大的快乐就是从事自己喜欢的工作。祝各位都能找到实现自己价值，还能同时赚到钱的工作。

[jeremy @jeremyj_eth]

@SimoAhava 🙄

[Drive Tesla 🇨🇦 @DriveTeslaca]

🤣

[Mehdi Oudjida @wissi_analytics]

Looker (BI) roadmap for 2024
1/5
A lot of features about Looker Studio have been announced during the presentation today of Looker (BI) roadmap for 2024.

To sum-up, for non Looker users but LS ones...
🧵

[Tom Tao @icecafe]

Thanks @SwingVisionApp for your referral gift ! 5 yrs in the making ! #swingVision #tennis #tracking

[Simo Ahava @SimoAhava]

If you're running #GoogleAnalytics4 on a single-page app, you don't have to fire Google Tag again on every route change UNLESS you are manually overriding page_location and/or page_title (as is common on SPAs).

#measure #singlepageapp

[Simo Ahava @SimoAhava]

Holy crap.

“BigQuery Studio”

- SQL code assistance
- Collaboration tools (Colab notebooks)
- Asset management built on Dataform
- Duet AI for assistive code development
- …and more

https://t.co/dVXdDZPdJZ

[John Isner @JohnIsner]

After 17+ years on the ⁦@atptour⁩, it’s time to say goodbye to professional tennis. This transition won’t be easy but I’m looking forward to every second of it with my amazing family.

The ⁦@usopen⁩ will be my final event. Time to lace ‘em up one last time. ❤️ ♥️ 💜

[Cyrus SEO @CyrusShepard]

Q. Using GA4, how many users visited my site from Google. Simple, right? Do you use:

• User Acquisition Report?
• Traffic Acquisition Report?
• Conversions Report?

@CharlesFarina wrote an excellent post explaining how each report works and the traps of each (🔗 in thread)

[Himanshu Sharma @analyticsnerd]

In some cases, you might want to send data to multiple #GA4 properties.

This is very useful if your website has multiple owners (business function), and each owner would like to track the same website with different approaches.

This can be done in two different ways based on the method of implementation you have used (Global Site Tag OR Google Tag Manager).

Learn more >> https://t.co/XOdesux5JP