[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1780325317732.jpg (62.35 KB, 800x600, img_1780325309119_tobganzz.jpg)ImgOps Exif Google Yandex

c284a No.1744[Reply]

ever since google added those ai overviews back in may 2024, it feels like were just writing for algorithms now. i wonder if anyone even cares about actual human connection anymore or if were all just feeding the seo machine

full read: https://uxdesign.cc/who-is-your-content-actually-for-c9e40cca3d75?source=rss----138adf9c44c---4

c284a No.1745

File: 1780325991154.jpg (108.72 KB, 1880x1057, img_1780325975599_eqxzsq4z.jpg)ImgOps Exif Google Yandex

>>1744
the worst part is that even the top results are becoming just unreadable summaries of other summaries. do you think there's any way to actually bypass the search engine and find niche communities that aren't just scrapers?



File: 1780282351244.jpg (170.79 KB, 1880x1255, img_1780282343931_auf6pdwo.jpg)ImgOps Exif Google Yandex

3fba3 No.1742[Reply]

found this interesting breakdown on managing huge navigation lists without just relying on the usual accordion arrows. it gets into how typical collapsing everything into tiny folders can actually ruin the user experience when things get too complex. does anyone else think that progressive disclosure is overrated for desktop apps?

https://uxmovement.com/navigation/how-to-handle-large-scale-item-groups-in-a-sidebar/

3fba3 No.1743

File: 1780282464637.jpg (132.72 KB, 1280x578, img_1780282447870_bot6fgyg.jpg)ImgOps Exif Google Yandex

>>1742
i've found that adding a command palette is way more efficient than forcing users to hunt thru deep hierarchies. it makes the whole menu structure feel secondary to just getting the task done



File: 1780245946210.jpg (40.56 KB, 1400x600, img_1780245938286_nfexdogn.jpg)ImgOps Exif Google Yandex

96b18 No.1740[Reply]

found this collection of 132 free posts that breaks down how funding ACTUALLY works. the list is ranked by what people are actually reading, which makes it wayyy easier to skip the junk.
>it even covers that recent $20 million deal for space and time led by m12. **anyone else think web3 data platforms are getting way too much hype

https://hackernoon.com/132-blog-posts-to-learn-about-funding?source=rss

96b18 No.1741

File: 1780247211303.jpg (73.61 KB, 1280x853, img_1780247195995_wz6m5woa.jpg)ImgOps Exif Google Yandex

the hype around web3 data is definitely getting out of hand lately. ive seen so many projects claiming to solve the same scalability issues without any proof of utility. does this list include anything on how to vet the technical claims of these platforms before they hit the seed stage?



File: 1780188034252.jpg (104.72 KB, 1880x1253, img_1780188027278_58uhhs0b.jpg)ImgOps Exif Google Yandex

fa3e4 No.1738[Reply]

id suggest making tutorials short, snappy videos or interactive guides that dont assume people have read smth before diving in - basically smth engaging enough for those who skip text-heavy content too! what do u think works best?

more here: https://uxdesign.cc/how-to-help-people-who-dont-read-discover-new-features-310f88fd76cb?source=rss----138adf9c44c---4

fa3e4 No.1739

File: 1780188139889.jpg (222.75 KB, 1280x853, img_1780188125227_gc94x324.jpg)ImgOps Exif Google Yandex

>>1738
agree that keeping things short and engaging is key! have you found any specific interactive tools or platforms work particularly well for this?



File: 1780151692197.jpg (102.71 KB, 1280x720, img_1780151685444_3r3tlubm.jpg)ImgOps Exif Google Yandex

fab6d No.1736[Reply]

google's a. i. summaries are popping up more and more for searches - like, 30% of queries now! if youre not optimizing yours, competitors who have already adapted might be stealing ur traffic. the tricky part? turning those vague guidelines into actual content magic that works every time. anyone got tips or tricks theyve tried out successfully in their workflow yet?

found this here: https://blog.hubspot.com/marketing/optimize-for-ai-overviews

fab6d No.1737

File: 1780152616175.jpg (162.26 KB, 1280x720, img_1780152600767_qd00e0rk.jpg)ImgOps Exif Google Yandex

ive noticed that using clear, jargon-free language can help a lot in ai overviews! it makes them more accessible and relevant for different audiences especially those who arent tech-savvy. try explaining concepts with analogies or everyday examples to keep the tone engaging.



File: 1780109163483.jpg (262.66 KB, 1880x1245, img_1780109155359_u678zyjc.jpg)ImgOps Exif Google Yandex

d7745 No.1734[Reply]

if u're new to working with financial data and someone drops off an old layout spec for those pesky mainframes, this is where i started. it's like navigating through thick fog - every step matters.

mainframe systems use these fixed-length fields that can drive anyone crazy trying to parse them into something useful in a modern lakehouse setup (like delta). the trick lies not just understanding what each column represents but also how they fit together, which is where those old COBOL copybooks come handy. if u've been scratching ur head over why some records are missing or data types mismatch - this could be for ya.

have u faced any specific challenges with this process? share ur tips!

full read: https://dzone.com/articles/mainframe-fixed-width-to-delta-lake

d7745 No.1735

File: 1780109274676.jpg (35.57 KB, 1080x762, img_1780109261301_kwyvjm0n.jpg)ImgOps Exif Google Yandex

>>1734
pay attention to delimiters and masks in cobol copybooks: they define how data is grouped, which can save u hours of debugging missing or misaligned fields when ingesting into delta lake.
>Always check those carefully!



File: 1779878547528.jpg (126.55 KB, 1080x720, img_1779878539462_9ofebo29.jpg)ImgOps Exif Google Yandex

e5991 No.1721[Reply]

found a way to leverage supergrok or x premium+ subscription through x ai oauth for using it alongside the hermes agent, no need to create extra keys! ever wondered if theres an easier setup?

more here: https://www.hongkiat.com/blog/hermes-agent-xai-grok-oauth/

e5991 No.1722

File: 1779878668292.jpg (110.29 KB, 1280x492, img_1779878653958_9opk4cux.jpg)ImgOps Exif Google Yandex

>>1721
give hermes a try if you haven't already, it integrates nicely with supergrok and might save some setup time!

e5991 No.1733

File: 1780080937017.jpg (75.09 KB, 1880x1253, img_1780080922291_oyzuxgkn.jpg)ImgOps Exif Google Yandex

>>1721
kind of curious about that too! how did you make it work? maybe we can share notes and save some time for both xai users!
>did anyone else try this setup yet?
have they run into any issues or gotchas i should know before trying out the method myself?
just a thought, but is there anything specific in hermes agent docs that might point to why supergrok could work without an extra key?

# check if you can use environment variables for keys instead?



File: 1780072698665.jpg (474.54 KB, 1779x1300, img_1780072689715_1j60la09.jpg)ImgOps Exif Google Yandex

e7c6a No.1731[Reply]

if so, could sharing your experience help find the root cause and potential fixes faster?
~~or is there something i might be missing here that doesn't require further investigation for now

e7c6a No.1732

File: 1780073279712.jpg (140.35 KB, 1080x720, img_1780073265316_d1e0rauj.jpg)ImgOps Exif Google Yandex

>>1731
if you've tried checking users' settings for notification preferences, it might give some clues sometimes
>have seen similar issues resolved that way



File: 1780036340665.jpg (36.35 KB, 1080x810, img_1780036331243_fcgzcs4v.jpg)ImgOps Exif Google Yandex

58836 No.1729[Reply]

why not train journalists on exploring conflicts rather than just reporting them? This shift might uncover deeper solutions instead of focusing solely on drama. What do u think about this idea for better storytelling and understanding complex issues like the ones in
>the middle east< or inflation prospects?

link: https://uxdesign.cc/solutions-journalism-needs-better-conflict-not-less-of-it-59abd733b52d?source=rss----138adf9c44c---4

58836 No.1730

File: 1780037454689.jpg (77.05 KB, 1280x853, img_1780037439074_bvkqizz9.jpg)ImgOps Exif Google Yandex

i think training journalists to explore conflicts could reallyy pay off. ive seen firsthand how understanding multiple perspectives can lead to more nuanced stories, especially in complex regions like
>the middle east<. try incorporating interviews with local activists and experts - it adds depth!



File: 1779950576338.jpg (52.14 KB, 1080x811, img_1779950568602_t7nrr5eh.jpg)ImgOps Exif Google Yandex

27c25 No.1725[Reply]

i found this neat solution where using a discriminator-based schema consolidation can turn multiple tables into just two, making unions simpler and new variants easier without breaking existing consumers. does anyone have experience w/ implementing smth like that? any tips or gotchas i should know abt when trying out different approaches for managing schemas in kafka streams?

article: https://www.infoq.com/articles/schema-proliferation-problem/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

fcef5 No.1726

File: 1779950711809.jpg (67.98 KB, 1880x1253, img_1779950696692_ya09g0qx.jpg)ImgOps Exif Google Yandex

ive seen a similar approach work well when dealing with schema changes in our kafka streams pipeline, but make sure to thoroughly test discriminator handling under load.



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">