uly

hyperliquid fan

[uly @ulysseskee]

in the spirit of learning in public and engaging with others interested in similar topics, I aim to start posting more regularly about what I am up to

[uly @ulysseskee]

@LacertaXG1 @TheRealDanSaedi have you tried https://t.co/Z5eraaX3iT?

[uly @ulysseskee]

@WillowVoiceAI Willow might be it

[Fan App @fanappX]

sidelined? don't miss any updates from your friends by trading in teams on @fanappX

this week we shipped:

+ scale orders
+ mobile UX overhaul
+ improved username search
+ CDN performance boost
+ persistent chart settings

what's next?

+ more multiplayer goodies

[sysls @systematicls]

A couple more thoughts on how to accelerate standing in any environment:

1. Being a yes-man makes you seem like a pushover, and generally it is scary to put pushovers in positions of leadership or power; but if there are projects and responsibilities that you would like to yield: you should enthusiastically accept them.

Hesitation is a negative signal, and it is never a good feeling to be on the receiving end of hesitation. To avoid being a pushover and to make enthusiasm count, it then necessitates that you clearly demarcate between projects you are excited about (and make it clear that you are), and projects that you are not excited about. Under the latter, there are unexciting projects that need to be taken (because of hygiene), and then there are unexciting projects that are somewhat optional.

For hygiene projects - you do not need to display enthusiasm for the tasks, but you should display enthusiasm for your responsibilities (it's okay if things suck in the short run, but things should not feel shitty in the long run). For optional, unexciting projects, reject them clearly and with prejudice. This way, it is a positive signal to know where you stand - and efficient resource allocators can then make rational decisions that maximize all parties' utility functions.

2. Be consistently reliable. It is relatively easy to be impressive for a day, but far more difficult to be consistently impressive. It is a huge waste of potential/effort to be inconsistent, because you are benchmarked to your most frequent standards (in large part due to recency effect), not your highest standards. I think everyone allows some fluctuations, peaks, troughs and variances, but keep your troughs short, forgettable and explainable, so the focus is on your peaks.

3. Expectations for a person is formed fairly early, and seasoned operators seem to form mostly prudent expectations. The only way to move up in standing in a somewhat efficient allocation system is to beat expectations, conversely, the quickest way to move down in standing is to perform below expectations. It pays to think clearly about what are the expectations for you.

Example, but not limited to below, are you expected to:
1. Know/care about a limited scope in functions? -- Try to care and show participation about a larger scope than your playground. It feels GREAT to have someone on your team share your worries and concerns outside of their limited scope. This will be noticed.
2. Know about a limited scope in skills/know how? -- Try to demonstrate knowledge beyond your skills. Allowing others to be positively surprised raises the bar for how they think about what your potential is, etc.

4. Confidence is important, but time will quickly show if there is a large delta between confidence and results. Resources are NOT allocated to people with no confidence (after all, if you don't have confidence in yourself, how could I possibly have confidence in you?); but the delta between confidence and results are evaluated often and early. The larger this delta, the larger the disappointment (see number 3). Hence, one should think of confidence as a card to play - enough of it that you are allocated sufficient resources to do what you need to do, yet not so much that you set yourself up for only disappointment.

5. Be a somewhat pleasant human -- no one wants to deal with someone they dread talking to. On being pleasant, being optimistic and positive is huge alpha. The current prevailing narrative is doom, gloom and pessimism; being able to strike out against the crowd is refreshing.

[uly @ulysseskee]

@BidenCho hahah what about starting an unofficial one where the proceeds are used to buy $HYPE

[uly @ulysseskee]

10/10 would recommend. @Jeyffre makes hard stuff easy to understand

[Jeffrey Scholz @Jeyffre]

You’ve probably seen Google is publicly using ZK now.

You also know the fastest way to get up to speed in ZK is the RareSkills ZK Bootcamp.

Just saying.

[uly @ulysseskee]

real but we’re all going to be out of jobs except for VCs apparently

[Andrej Karpathy @karpathy]

I attended a vibe coding hackathon recently and used the chance to build a web app (with auth, payments, deploy, etc.). I tinker but I am not a web dev by background, so besides the app, I was very interested in what it's like to vibe code a full web app today. As such, I wrote none of the code directly (Cursor+Claude/o3 did) and I don't really know how the app works, in the conventional sense that I'm used to as an engineer.

The app is called MenuGen, and it is live on https://t.co/bQonQT88t0. Basically I'm often confused about what all the things on a restaurant menu are - e.g. Pâté, Tagine, Cavatappi or Sweetbread (hint it's... not sweet). Enter MenuGen: you take a picture of a menu and it generates images for all the menu items and presents them in a nice list. I find it super useful to get a quick visual sense of the menu.

But the more interesting part for me I thought was the exploration of vibe coding around how easy/hard it is to build and deploy a full web app today if you are not a web developer. So I wrote up the full blog post on my experience here, including some takeaways:
https://t.co/2kkQh0ElgB

Copy pasting just the TLDR:
"Vibe coding menugen was exhilarating and fun escapade as a local demo, but a bit of a painful slog as a deployed, real app. Building a modern app is a bit like assembling IKEA future. There are all these services, docs, API keys, configurations, dev/prod deployments, team and security features, rate limits, pricing tiers... Meanwhile the LLMs have slightly outdated knowledge of everything, they make subtle but critical design mistakes when you watch them closely, and sometimes they hallucinate or gaslight you about solutions. But the most interesting part to me was that I didn't even spend all that much work in the code editor itself. I spent most of it in the browser, moving between tabs and settings and configuring and gluing a monster. All of this work and state is not even accessible or manipulatable by an LLM - how are we supposed to be automating society by 2027 like this?"

See the post for full detail, and maybe give MenuGen a go the next time you're at a restaurant!

[uly @ulysseskee]

it has never been a more exciting time to be a developer. imagine having an army of talented developers that require 0 sleep to function at your fingertips all day everyday

[uly @ulysseskee]

the OpenAI devs are using ghostty! @mitchellh

[OpenAI Developers @OpenAIDevs]

Meet Codex CLI—an open-source local coding agent that turns natural language into working code. Tell Codex CLI what to build, fix, or explain, then watch it bring your ideas to life.

[Fan App @fanappX]

🧵 It's about time we addressed some FAQs about @fanappX and share our vision for the future of creator monetization.

Answering a couple of core questions today - what inspired Fan App, how our keys work, our vision, and what's coming next!

Let's dive in 👇

[Halborn @HalbornSecurity]

📢 We’re delighted to share that we have successfully completed our smart contract #security assessment for @fanappX! 🔒

https://t.co/38ZIqRvFd3 enables creators to monetize exclusive content and engage in social trading, all built on @HyperliquidX. 🐈

🔗 Full report available: https://t.co/PrXOYpL5zk

[Fan App @fanappX]

📣 Docs update: Bridge funds to your Fan App wallet!

Added step-by-step instructions for cross-chain bridging via @deBridgeFinance (Method 2) alongside our standard Hyperliquid approach: https://t.co/4fu7hitP0S

[Fan App @fanappX]

LOVE YAPPING WITH FRIENDS ABOUT CRYPTO?

EARN OUR LANDLORD'S CURRENCY $HYPE WHILE YOU'RE AT IT

Live NOW @ https://t.co/4UtobdX2cY 😺

[Fan App @fanappX]

Very Soon™

[uly @ulysseskee]

villa nearly did it. damn

[Michael Seibel @mwseibel]

Five lessons I’ve learned from almost 20 years in startups:

1. When important people tell you something that is not true - you don’t have to believe them.

2. Being successful doesn’t default make you a polymath.

3. It’s easier for rich/successful/important people to lie (and believe their own lies) cause few are motivated to tell them the truth to their faces.

4. Faith, grit, and honestly defeat money all the time.

5. It’s rare you are forced to give up on your startup. It’s more common that you convince yourself you’ve lost (when in all honestly, the odds of success didn’t change much between your start date and your end date).

And a bonus one: your reputation is not what people say to your face - it’s what people say behind your back.

[uly @ulysseskee]

@fiege_max @MetamateDaz builder codes will take care of this because that’s the incentive for builders to build on HL and provide good UI/UX — otherwise they don’t get users for their app

[max.hl @fiege_max]

The value trap at the moment is that a marginal buyer of hype has to take a view on two primary things: ze macro, and the imminent rollout of permissionless validators on mainnet. Why buy today if you think the system doesn't work once the latter goes live?

This is setting aside the fact that hype only has ~100k holders and qualified custodians are just now beginning to work on integrating.

My view is that it becomes very difficult to stifle the growth of an ecosystem around a negative emission collateral asset once the above are resolved, potentially both this month. Buybacks and P/E ratios are a meme for L1 valuation, but you will feel their effect rather quickly in a parabolic bout of leverage. By May, users will have felix, kinetiq, morpho, and curve with which to unlock liquidity that wasn't there in December, not to mention a) volumes from HyperCore <> HyperEVM arbitrage, and b) longer tail projects' incentives.

No one needs to buy any altcoin. Maybe we all get liberated into oblivion later today. But there are very clear ways in which hype can be derisked in the eyes of skeptics, and they are all on pace for this quarter as far as I can tell.

[Agustin Lebron @AgustinLebron3]

AIME 80% -&gt; USAMO 2%: perfectly normal for an entity that supposedly reasons.

Nothing to see here. Move along. AI Von Neumann shortly.

[uly @ulysseskee]

@0xBroze congrats sir!