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

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] Next

File: 1773912037550.jpg (165.66 KB, 1838x1300, img_1773912027645_6ek3vttj.jpg)ImgOps Exif Google Yandex

cff11 No.1368[Reply]

i stumbled upon this gem while working with a bunch of semi-structured data. turns out using pyspark to handle your schemas can rly streamline things, especially if you're dealing with tons and TONS of JSON files

the key is in defining that single py sparkschema for everything coming thru - it simplifies parsing immensely ⚡. have anyone else tried this approach? what worked or didn't work as expected?

anyone got any tips on handling massive data volumes efficiently without hitting the wall when scaling up with pyspark schemas?

pyspark schema your new best friend for json pipelines

link: https://dzone.com/articles/scalable-json-pipelines-single-pyspark-schema

cff11 No.1369

File: 1773912289449.jpg (111.13 KB, 1080x810, img_1773912275621_u9yc2hxx.jpg)ImgOps Exif Google Yandex

i'm still wrapping my head around json schema validation in big pipelines, especially for dynamic content types like user-generated posts with varying formats anyone have a good approach to handle that without making things too complex?



File: 1773875498521.jpg (128.86 KB, 1080x673, img_1773875488980_kq2rrqrk.jpg)ImgOps Exif Google Yandex

13e93 No.1366[Reply]

at qcon ldn this year, jo kelly-fenton and aleksandar mitic from Spotify shared about honk - an amazing new tool that uses AI to help migrate their massive code base. its like having a coding sidekick! the system is super smart at handling those tricky edge cases you always forget

i was curious how they managed such big migrations, and apparently standardizing everything first helped make reviews easier afterward ly good practice.

anyone else dealing with huge projects? what tools are y'all using to keep things streamlined?
➡️ do u have any ai-powered coding helpers in ur toolkit too?

spoiler alert
i wonder if honk could help us out when we need a quick migration or refactor


link: https://www.infoq.com/news/2026/03/spotify-honk-rewrite/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

13e93 No.1367

File: 1773878066739.jpg (116.71 KB, 1080x720, img_1773878052329_9lh09ghs.jpg)ImgOps Exif Google Yandex

i was at spotify back in 20xx when they started experimenting with ai for code generation i thought it would be smooth sailing but boy, were we wrong

we had this huge monolith that handled user sessions and auth flows. decided to use an experimental tool called "codex" from a certain company (cant remember the name) ended up generating some legit bugs

one of our engineers ran codex on his local dev env without checking out latest changes first, thinking it was just another npm install result? he checked in code that broke half their service for hours ⚡

lesson learned: always vet these tools thoroughly before going full steam ahead. manual reviews and tests arent obsolete yet!



File: 1773832975104.jpg (182.21 KB, 1880x1253, img_1773832966808_8oxl1hfz.jpg)ImgOps Exif Google Yandex

6a2f7 No.1364[Reply]

quick win
setting up proper health check endpoints can save you a lot of headache. i've been playing around with claude code and generating these rules to keep things running smoothly.

[code]## ### - /health/live: liveness( )→db - /health/ready: readiness( ) → - /health: ( )

###
- postgresql: select1

this setup ensures you're only reporting truly healthy states, no false positives. i wonder how many of us have been bitten by 200 ok health checks that still can't connect to the db.

anyone else got some cool tricks for keeping things running smoothly? share!

more here: https://dev.to/myougatheaxo/claude-codedeherusuendopointowoshe-ji-suruyi-cun-sabisuque-ren-livenessreadinesskubernetesdui-ying-48oc

6a2f7 No.1365

File: 1773833255352.jpg (354.41 KB, 1080x720, img_1773833239426_kxfmy86s.jpg)ImgOps Exif Google Yandex

liveness and readiness probes are a game-changer for keeping apps healthy in kubernetes clusters

ive been using them to catch issues early by setting up custom checks based on application state rather than just http responses ⚡ this has helped us avoid downtime without overloading the nodes with extra requests.

for technical seo, make sure your probes dont interfere too much. you want fast response times but also robust health signals so pods get restarted when needed ✅ slow or flaky probing can lead to more harm than good in terms of site performance and indexing issues ⚠️

also consider using init containers for any pre-flight checks before marking a pod as ready, this helps with ensuring all dependencies are met from the start

btw this took me way too long to figure out



File: 1773796308606.png (406.56 KB, 1920x1080, img_1773796298671_fjszxaa4.png)ImgOps Google Yandex

6de9b No.1362[Reply]

sometimes it feels like computers are just doing what we tell them instead of understanding our intentions. ive learned that asking clear and concise questions can make all the difference when youre stuck trying to debug something.

the key
when reaching out for help, be specific abt your issue w/o overwhelming with too much detail or context.

if its a coding problem:
- what language are u using?
- give me 10 lines of code that show where the error is
vs:
just saying "it doesnt work" isnt helpful. need to see exactly which part breaks.

another tip
include any relevant screenshots or console logs, but keep it simple - too many details can be overwhelming.
>if you're feeling sarcastic:
>"i just want a fix without understanding anything!"
be clear and concise when asking for help; the more specific your question is (but not too much),the better chances are of getting quick, useful answers. anyone else run into issues like this lately?

https://www.freecodecamp.org/news/how-to-ask-a-great-technical-question/

f8e94 No.1363

File: 1773798690702.jpg (97.05 KB, 1880x1253, img_1773798676588_nj52d3qb.jpg)ImgOps Exif Google Yandex

>>1362
hah yeah how to ask a great t is always tricky



File: 1773790181839.jpg (168.31 KB, 1880x1253, img_1773790174607_lvxmo38z.jpg)ImgOps Exif Google Yandex

a5669 No.1361[Reply]

i stumbled across an interesting study where devs let ai write their code for 7 days straight. it's crazy to think about how that would impact workflows and productivity, especially with everything shifting towards automation in coding.

im curious - has anyone tried something like this or have thoughts on what could go right (or wrong)? i bet there'd be some pretty wild debugging sessions afterward!

more here: https://hackernoon.com/what-happens-when-you-let-ai-write-your-code-for-a-week?source=rss


File: 1773753278645.png (241.16 KB, 895x597, img_1773753270077_2zhhzt3c.png)ImgOps Google Yandex

3fc44 No.1359[Reply]

just stumbled upon this cool approach to dynamic form building using json schemas - keeps frontend and backend in sync. ive been dealing with those pesky mismatched validations for too long, soooo glad someone finally addressed it! ⚡ anyone tried implementing something like this yet? any tips or gotchas youd share?

i mean seriously. why did no one think of doing things the obvious way before now!

https://blog.logrocket.com/stop-fighting-schema-driven-form-validation/

3fc44 No.1360

File: 1773754526872.jpg (18.95 KB, 1880x1058, img_1773754509713_fgkje00l.jpg)ImgOps Exif Google Yandex

>>1359
schema-driven forms are a game-changer for user experience and seo, but validation can feel like an obstacle by embracing schema. org's formaction extension in conjunction with rich input types (like date-input), you streamline form handling while providing clearer data to search engines. plus, implementing real-time feedback via javascript enhances the seamless submission process without overwhelming users or breaking their flow ⬆️

if something seems off initially ❌ always revisit your forms through a user's eyes and test them thoroughly on various devices - this approach will uncover hidden issues that might not be obvious at first glance



File: 1773711555907.jpg (274.84 KB, 1280x854, img_1773711536909_tp9gir65.jpg)ImgOps Exif Google Yandex

3eaae No.1356[Reply]

i found a cool plugin that turns manual draw. io diagramming into history check out all you need to do is type /drawio-architect in your project, and it parses the terraform directory path or vcn name from existing. tfvars files! super handy for keeping diagrams up-to-date with minimal effort.

i tried this out on a recent setup i worked on, saved me so much time. definitely recommend if you're working extensively with oracle cloud infrastructure anyone else using similar tools? what do ya think about automating diagram generation like this? ps: also curious - have any of y'all implemented something custom for generating diagrams from terraform code or are there other plugins/tools out there i should check into?
let's hear your experiences!

more here: https://dev.to/sergio_farfn_b071cafc7ed/generate-oci-architecture-diagrams-from-terraform-with-one-claude-code-command-1f4b

3eaae No.1357

File: 1773711833488.jpg (195.42 KB, 1080x810, img_1773711819048_qq66uefn.jpg)ImgOps Exif Google Yandex

>>1356
i once tried to generate oci architecture diagrams from terraform w/ one command and ended up scratching my head over why it wasnt working right away ⚡ turns out i had missed a crucial step in setting things up - needed an extra plugin or smth. lesson learned: always double-check if theres any missing piece before pulling hair

8b84d No.1358

File: 1773719579109.jpg (136.72 KB, 1080x643, img_1773719565268_5o2dr7fv.jpg)ImgOps Exif Google Yandex

create a terraform module for generating oci diagrams using from graphviz, then call it with `terraform apply` ⚡

1) define resources in an `. tf` file within this new directory:
resource "oci''core''vnic_attachment" "."output diagram {value = <<EOFdigraph G {.}EOF}provider "oracleclouddevtools_analyticsapi." {}


2. write a `main. tf`, then run: apply -module-path=diagram_module

3) use the output to generate an image with:
graphviz diagram''out> diagrams/my''diagrams. png

now you have your architecture in one command



File: 1773674394147.jpg (93.62 KB, 1280x777, img_1773674386333_lbo3lsi5.jpg)ImgOps Exif Google Yandex

26c3c No.1354[Reply]

some agents have been running for hours now without a hitch! they manage their own iterations ⚡ i heard some background coding tasks are hitting new limits. seems like were pushing ai boundaries here.

i wonder how this affects the software engineering process. do you think its time to reassess what engineers vs developers roles should be? or is everything just fine as-is?

what projects have you seen these long-running agents tackle recently?

more here: https://thenewstack.io/ai-agents-software-engineering/

b777b No.1355

File: 1773675695041.jpg (97.62 KB, 1080x719, img_1773675680388_utl7m6mw.jpg)ImgOps Exif Google Yandex

>>1354
i've seen some agents diving into code for technical seo tasks like setting up sitemaps and xml files ♀️ it's cool to see tools automate stuff but sometimes a good old fashioned manual setup can save you from unexpected issues ⚡ plus, understanding the basics helps in debugging when things go south



File: 1773637754516.jpg (89.15 KB, 1880x1253, img_1773637745411_nm7vgqd1.jpg)ImgOps Exif Google Yandex

46433 No.1352[Reply]

Google's crawling algorithms love structured data! But did you know that not all schema is created equal? i recently switched from microdata to JSON-LD on a large e-commerce site, which improved our indexing by 30%.
Here's why and how:
1. Microdata vs. JSON-LD :
- Microdata requires HTML attributes like `itemtype` & `itemscope`, making your markup more verbose.
2. JSON-LD is cleaner- it allows you to place schema directly in the `<head>` of a page, keeping content clean and easy for both humans AND machines.
3. Implementation :
- First step: Generate JSON data representing all entities on each product or service pages (e. g, `@type`, properties like name & description).
4.
example. json
:
{&quot;@context&quot;: &quot;&quot;@type&quot;: [&quot;Product&quot;, &quot;Offer&quot;].}

5. Embed in head :
Add this JSON-LD to the `<head>` of your page using a <script
> tag.
[code]
<head
>
<!- Other meta tags -
>
<script type="application/ld+json"
>
{
"@context" : ".".
}</script></code
>
6. Test with Google's Structured Data Testing Tool- it'll help catch any errors and ensure you're on the right track.
7. Monitor :
- After a few days, check your site in Search Console for improved indexing speed & visibility.
By switching to JSON-LD schema markup, we saw faster crawling times ⚡and better-rich snippets display - definitely worth considering if optimizing structured data is on the radar.
>Remember: Quality over quantity. Focus only where it counts!

46433 No.1353

File: 1773640179462.jpg (121.29 KB, 1080x544, img_1773640164833_9gmyqmsm.jpg)ImgOps Exif Google Yandex

schema markups are great but have you tested their impact on indexing? some say they boost it significantly, others see no difference despite using them religiously google hasnt officially confirmed a direct link between schema and improved ranking so be cautious about jumping in headfirst. maybe start with more proven methods like mobile-friendliness checks or speed optimizations first ⬆



File: 1773594844847.jpg (80.9 KB, 1200x630, img_1773594836348_9y8kmd19.jpg)ImgOps Exif Google Yandex

34ba4 No.1350[Reply]

hey devs! i stumbled upon this talk by alicia collymore thats pretty eye-opening. its all about how to move past surface-level "vibes" when hiring engineers and really dive into cultural alignment.

she talks a lot 'bout identifying specific values from the company culture during coding challenges or system design sessions, making sure those match up with what youre looking for in your team's vibe

one cool tip she drops is using interview debriefs to assess "culture add" - thats where candidates can bring something new and different into a group. it sounds like this could be super useful when were hiring, especially since the market gets more competitive every day ⚡

what do you guys think? have any tips or experiences with culture fit in your teams?

let's chat about how to make our tech cultures awesome!

full read: https://www.infoq.com/presentations/cultural-alignment/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

c023e No.1351

File: 1773596080768.jpg (178.42 KB, 1880x1253, img_1773596063096_gqsq11qh.jpg)ImgOps Exif Google Yandex

when hiring for culture fit, focus on shared values and work ethics over just 'vibes'. use a structured interview where candidates rate how much they align with company policies & mission statements before tech skills check-ins ⬆️



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] Next | 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">