Co-founder of StockStory, acquired by CNBC, music lover, petrol head
Prague, Czech Republic
Joined September 2008
- Tweets179
- Following530
- Followers124
- Likes76
Tested Opus 5.5 on complex gap analysis between prototype and already drifting production code. The concepts and nuances it picked up were spot on. During grilling session I had to correct just two out of 25 questions. Comparable with Fable, but with better understandable lingo.
This is a view from our new CNBC / StockStory office in Prague. I'm pretty excited about what's ahead, growing the engineering team. We're hiring 🚀 stockstory.org/careers
Radek Strnad retweeted
This week we are rolling out new article type on @StockStoryHQ: earnings call analysis
Another release at @StockStoryHQ, this time we greatly improved the peers selection for large companies.
Radek Strnad retweeted
Happy birthday to @princeofpersia, released on Apple II 35 years ago today!💾🕹️
I tell the behind-the-scenes story in my 1980s "The Making of Prince of Persia" journals,📘 and in my new graphic novel memoir "REPLAY."📕You can check out both books here: jordanmechner.com/en/books/
Upgraded my old @turris_cz router with Wi-Fi 6 kit to give it couple more years of service. The signal range is better, speed has improved and all devices on the network are nearing the line limit.
This is a performance of @StockStoryHQ stock picks since we started publishing our theses last summer. Including the underperforming first one, they are roughly doubling the #SP500 performance.
4) Avoid nested queries. Leverage "SELECT DISTINCT ON", "GROUP BY" or "PARTITION BY" instead if possible.
5) Consider re-designing tables for more performance. Normalize to optimize for writes, denormalize for read-heavy apps.
3) Optimize performance by breaking large queries into multiple smaller instances. Keep data in memory and avoid disk spills.
2) Optimize queries by creating indexes based on expected usage. In composite indexes, prioritize the most impactful columns first. Not all created indexes are used. Striking the right balance is crucial; excessive indexes can impede write performance.
1) Master EXPLAIN ANALYZE plans. Check couple distinct query plans to uncover potential edge cases. If you're a beginner, graphical tools might be helpful.
I was optimizing queries for a new data source dumped into #PostgreSQL tables we've plugged into @StockStoryHQ . Multiple joins across several tables 10GB - 300GB large. Here's what made the most impact 🧵#DatabaseTips:
Radek Strnad retweeted
UX Methods Catalog: Largest open resource of UX Research Methods on the Web producthunt.com/posts/ux-met… by @viktorbezdek
5 days of holiday sitrep:
✅ caught up with missing sleep
✅ spent quality time with my family
✅ fixed KRK Rokkit 8 G2 blowing fuses
✅ poured self-leveling compound in a new bedroom
✅ migrated laptop to a larger / faster SSD
✅ reconfigured / rewired home network / router
As an occasional PS player I never thought gaming on Linux is a good experience. This Christmas I installed
@LutrisGaming
- one click installs, game specific Wine configs, no crashes, great performance, immense fun. I'm seriously impressed how smooth the experience is.