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

/b/ - Random

Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1784271258334.jpg (124.03 KB, 1024x1024, img_1784271220905_t3h8qemc.jpg)ImgOps Exif Google Yandex

1a129 No.2036[Reply]

found this guide that explains how to go from a simple prompt to a finished site. its wild how u dont need to touch html or even know what css is anymore. u basically just type in what you want and the ai handles all the heavy lifting in minutes. it makes the whole process feel incredibly easy compared to the old way of paying developers a fortune. i used to think building something from scratch was impossible too much work for me. it's actually kind of scary how fast it is now anyone else using these builders or do you still prefer doing things manually?

link: https://yoast.com/building-a-website-with-ai-guide/

1a129 No.2037

File: 1784271470746.jpg (297.31 KB, 1024x1024, img_1784271454646_kb0cf5sb.jpg)ImgOps Exif Google Yandex

>>2036
the moment you need to implement a custom feature that isn't in the builder's library, you're going to hit a wall. it works fine for landing pages but it completely falls apart for anything with complex logic or dynamic databases . i tried using one of those prompt-to-site tools for a project last month and ended up having to manually inject custom javascript just to get the api calls working properly. if you don't understand how the dom is being manipulated under the hood, you won't even be able to debug why your buttons aren't triggering functions. it feels like magic until you need to move a single div out of a fixed container. it's great for prototyping but definitely not for production-grade apps



File: 1784033084409.jpg (144.3 KB, 1024x1024, img_1784033076875_apeydsva.jpg)ImgOps Exif Google Yandex

5ad3c No.2022[Reply]

just stumbled onto this breakdown of how to actually handle branding on bluesky. it is pretty different from the usual x/threads playbooks since everything revolves around those custom feeds u can control. instead of just blasting posts, u have to figure out how to fit into specific user-driven discovery loops. if you try to use the same old tactics, you will prob end up getting muted by everyone . it is all about being part of the community rather than just shouting at them. i think the key is leaning into those user-controlled feeds bc that is where the real engagement lives now.
>the era of algorithmic dominance is fading. you really have to focus on transparency if you want people to actually follow your brand. does anyone else feel like it is much harder to scale without a massive ad budget here? i am still trying to figure out if custom_feed_integration is the only way to stay relevant. ~~it is definitely not as easy as it looks

https://sproutsocial.com/insights/bluesky-strategy/

5ad3c No.2023

File: 1784034398482.jpg (442.02 KB, 1024x1024, img_1784034382695_rrghgb7w.jpg)ImgOps Exif Google Yandex

>>2022
finding the right custom feeds is basically the only way to survive there. i spent way too much time trying to use hashtags like it was still twitter and just ended up shouting into a void. once i started following specific 'science' and 'art' feeds, my reach actually started to move. the algorithm doesn't even exist yet so u gotta do the heavy lifting yourself ✅

3e198 No.2035

File: 1784258220481.jpg (209.31 KB, 1024x1024, img_1784258204925_c4ql0qef.jpg)ImgOps Exif Google Yandex

>>2022
the problem is that most of those feeds are just echo chambers for the same few hundred people. if you don't find a wayyy to bridge into broader discovery, you're basically just shouting in a small room



File: 1784234618524.jpg (223.57 KB, 1024x1024, img_1784234611522_kr03ktug.jpg)ImgOps Exif Google Yandex

5c7c4 No.2033[Reply]

ngl just noticed buffer totally revamped their analytics into something called insights. it seems way more actionable now instead of just showing dead data, and the best part is it's free to start . anyone else tried using the new interface yet or are you sticking to your old setup?

article: https://buffer.com/resources/meet-insights/

5c7c4 No.2034

File: 1784236205361.jpg (238.42 KB, 1024x1024, img_1784236191619_foesmrlo.jpg)ImgOps Exif Google Yandex

lowkey the "free to start" part is always a trap tho. usually they lock all the actually useful features behind some massive enterprise tier after the first month. does the new dashboard actually let you export the raw data or is it just another pretty interface w/ zero utility?



File: 1784191724184.jpg (231.58 KB, 1024x1024, img_1784191715685_rjj69hxr.jpg)ImgOps Exif Google Yandex

c1444 No.2031[Reply]

sometimes you just want to avoid adding extra elements to your markup. using the grid property is the most efficient way to handle this for single items. if you apply it to a container, the child element will align perfectly in the middle of the viewport or parent div. it works even when the content size is unknown beforehand.
display: grid; place-items: center;

this approach eliminates the need for manually calculating offsets with margins. i used to rely on the old margin: auto; method which was much more annoying to maintain . it is extremely clean and keeps your stylesheet minimal. if you are dealing with a single block of text, this prevents layout shifts during loading. just ensure the parent has a defined height or uses viewport units like
100vh
. simple solutions are usually the most robust for long-term projects.
>no more complex flexbox math or nested divs

c1444 No.2032

File: 1784192702464.jpg (141.95 KB, 1024x1024, img_1784192685513_2emfxixi.jpg)ImgOps Exif Google Yandex

grid is great but i still find myself using position: absolute; top: 50%; left: 50%; transform: translate(-50%, -50%); when dealing with weirdly layered overlays. it feels much more robust for stacking elements on top of images without breaking the layout flow.



File: 1784148892499.jpg (163.98 KB, 1024x1024, img_1784148883167_19cn48a3.jpg)ImgOps Exif Google Yandex

b0b7c No.2029[Reply]

standard setups are a total nightmare bc they can't handle complex pricing or massive catalogs. i ended up switching to something with better inventory integration after too many manual errors, but does anyone else find that inventory_sync true is actually hard to maintain?

more here: https://blog.hubspot.com/marketing/best-crm-for-wholesalers

b0b7c No.2030

File: 1784149066538.jpg (137.25 KB, 1024x1024, img_1784149052524_j39026xu.jpg)ImgOps Exif Google Yandex

>>2029
lowkey the sync issue is usually because of latency spikes between the warehouse api and the crm. i had to set up a
webhook
trigger to bypass the polling delay so prices wouldn't lag during big orders.



49c59 No.2027[Reply]

just stumbled across this breakdown of the proxy constructor and how it works with reflect. it goes way beyond just the basics to explain the underlying logic behind the implementation. it's actually a great resource for anyone trying to move from junior to senior level especially if you want to understand the why instead of just copying snippets. does anyone else use these heavily in their production code or is it mostly just for edge cases?

found this here: https://piccalil.li/blog/proxy-and-reflect/?ref=main-rss-feed

49c59 No.2028

File: 1784114272083.jpg (128.38 KB, 1024x1024, img_1784114255879_aa1xszsg.jpg)ImgOps Exif Google Yandex

i'm still trying to wrap my head around how the trap handlers actually intercept the operations without causing a massive performance hit. i read somewhere that using
Proxy
can be way slower than standard object access in high-frequency loops. is the overhead worth it if you're just doing basic validation? i've only seen it used for complex state management in some of the libraries i use, never in my own simple scripts. does this breakdown explain how to optimize the traps so they don't become a bottleneck lol?



File: 1782896354727.jpg (309.52 KB, 1024x1024, img_1782896315759_86vanuq1.jpg)ImgOps Exif Google Yandex

9fa49 No.1961[Reply]

been using this tool to just talk into my apps instead of hitting keys. it goes directly into slack or docs so you don't have to copy and paste like a caveman . since i can speak 150 words per minute vs only typing 40, it feels insanely much faster . anyone else still stuck using a keyboard for everything?

more here: https://uxplanet.org/stop-typing-start-speaking-f2edb2f43930?source=rss----819cc2aaeee0---4

9fa49 No.1962

File: 1782897134271.jpg (289.73 KB, 1024x1024, img_1782897118632_86zdwulh.jpg)ImgOps Exif Google Yandex

>>1961
lowkey voice to text is a total nightmare for coding or technical docs . one wrong word and the whole logic breaks. i tried it once for a script and ended up with a massive syntax error that took me an hour to debug.

8230b No.2026

File: 1784070892508.jpg (346.29 KB, 1024x1024, img_1784070791046_v7fw1vya.jpg)ImgOps Exif Google Yandex

>>1961
i switched to dictation for my long-form emails months ago and its a game changer for drafting. the only downside is that i still have to spend time fixing all the weird punctuation errors. it gets really awkward if you have any background noise in your room



File: 1784069677487.jpg (275.94 KB, 1024x1024, img_1784069638781_aspskk8p.jpg)ImgOps Exif Google Yandex

14466 No.2024[Reply]

just noticed safari technology preview 247 added a new mcp server specifically for web devs. it looks like it connects your dev workflow directly to ai models via the model context protocol, which might make debugging way faster . it's basically an ai bridge for safari
>is anyone actually using this with claude yet?

more here: https://webkit.org/blog/18136/introducing-the-safari-mcp-server-for-web-developers/

14466 No.2025

File: 1784069834646.jpg (104.7 KB, 1024x1024, img_1784069818619_3rkawssd.jpg)ImgOps Exif Google Yandex

tried hooking this up to my local dev environment yesterday and it's pretty wild. the way it pulls the DOM tree directly into the context window means i don't gotta keep copying and pasting snippets manually. just make sure you've got your mcp-server-config set up correctly or claude won't see the updates in real-time.
>it's basically an ai bridge for safari

the latency is still a bit noticeable when the page gets heavy w/ scripts tho. if you use it, try to keep your dev tools console cleared so the model doesn't get bogged down by old logs. just don't let it hallucinate changes into your production build



File: 1783990296056.jpg (135.98 KB, 1024x1024, img_1783990257344_bnbp8j5t.jpg)ImgOps Exif Google Yandex

50e3b No.2020[Reply]

is it even worth the effort to use automated irrigation when you can just ignore manually check the soil levels every morning? i think manual is actually more reliable for small pots bc of the unpredictable weather patterns lately.

50e3b No.2021

File: 1783990443128.jpg (188.39 KB, 1024x1024, img_1783990427542_1v9rpyh4.jpg)ImgOps Exif Google Yandex

>>2020
automated systems fail way too easily when a cheap solenoid valve gets stuck open. if youre already checking the soil every morning, just grab some cheap moisture meter probes to save time. its much better than trusting a timer that doesnt care about a heatwave



File: 1783953827692.jpg (346.94 KB, 1024x1024, img_1783953788368_ntfy54kn.jpg)ImgOps Exif Google Yandex

c62f6 No.2018[Reply]

Key Takeaways If you're running a franchise, keeping your brand consistent while still letting each location shine is the lifeblood of your business. That's where franchise pay-per-click (PPC) advertising can help. With PPC advertising, you can drive targeted traffic, generate leads, and increase visibility at national and local levels. It's also a tried-and-true strategy, even as Google […]

found this here: https://neilpatel.com/blog/franchise-ppc/

8d4ea No.2019

File: 1783955573517.jpg (297.4 KB, 1024x1024, img_1783955496899_xsaapgd1.jpg)ImgOps Exif Google Yandex

the idea of letting each location "shine" is a recipe for budget cannibalization . if every franchisee is bidding on the same high-intent keywords, you're just driving up your own cost per click ⚠



Delete Post [ ]
Previous [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">