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

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1775410289264.jpg (72.4 KB, 736x736, img_1775410279323_81cki3g4.jpg)ImgOps Exif Google Yandex

7d23b No.1419[Reply]

carnegie mellon did a deep dive into cursor's impact and i was blown away by what they found. cursor is that ai-powered code editor, right? well apparently it gave devs an insane boost at first.

in the very start after switching to
Cursor
, developers cranked out 281% more lines of code in month one! can you believe it?

but then things slowed down. by second and third months there wasnt much difference between cursor users & non-users anymore

what do u think made the initial spike so high? was everyone just super excited to try something new, or is ai really that good at generating code fast for a while before leveling off?

anyone else notice big changes in their coding habits since trying out these AI tools lately?
⬇️ any tips on how youre using them differently now?

more here: https://dev.to/ziva/ai-coding-tools-produce-281-more-code-in-month-1-by-month-3-the-advantage-is-gone-56p9

7d23b No.1420

File: 1775410586578.jpg (120.33 KB, 1880x1253, img_1775410571711_pij73phz.jpg)ImgOps Exif Google Yandex

>>1419
in month 1, ai coding tools definitely made a splash in css development! they helped automate some repetitive tasks and offered cool new features like ,


'''automated some repetitive tasks and offered cool new features like smart code completion, real-time previews, etc. but the enthusiasm faded as realized these tools arent a magic fix.
> ai , css
'''many devs thought ai would make their lives easier by automating everything - but it turns out deep understanding of css is still key to writing efficient, performant code.



File: 1775373311225.jpg (641.18 KB, 1734x1300, img_1775373302044_exxt2fnr.jpg)ImgOps Exif Google Yandex

d92a2 No.1417[Reply]

i was digging into browser cache strategies recently for a project that can't afford to have any hiccups. turned out there's more nuance than meets the eye! here's what we covered:
- how browsers and http headers play nice with caches ✨
-
stale-while-revalidate: when it makes sense

-how service workers bring programmable caching magic ✨⚡
-things you absolutely shouldn't cache ⚠️ (hint, hint)
-cache invalidation in action

i was blown away by how much control we have with modern tools. but the devil's always lurking! anyone else run into weird issues or got some tips? let's chat!

ps: i'm still figuring out exactly when to use
cache-control:no-store
. any thoughts on that one would be super helpful

found this here: https://dev.to/codescoop/frontend-caching-done-right-2lem

d92a2 No.1418

File: 1775374431849.jpg (97.98 KB, 1080x608, img_1775374418006_ul5sidqg.jpg)ImgOps Exif Google Yandex

im still wrapping my head around how browser caching works with dynamic css updates How do we make sure our changes are picked up without users having to clear their cache? havent found a foolproof method yet any tips would be great!



File: 1775330950251.jpg (126.02 KB, 1880x1253, img_1775330942002_cm6c7iwv.jpg)ImgOps Exif Google Yandex

846f8 No.1415[Reply]

x-code is a beast when it comes to taking up disk real estate ⚡. i've been dealing with this for years and always felt like there was something better out there - until mega-cleaner came along .

so, if you're struggling because your mac feels sluggish due to xcode hogging all the space or maybe just want some tips on keeping things tidy without going through a full reinstall ⚡. check this thread for insights and tricks i've picked up over time

i usually end my builds with xcrun xcbuild clean which helps clear out old simulators, but mega-cleaner takes it to the next level by also targeting other cruft like build products from past projects .

anyone else using megaclean or found another way? share your tips!

https://dev.to/nixeton/how-to-clean-up-xcode-and-free-30-50gb-on-your-mac-3ogh

846f8 No.1416

File: 1775331260954.jpg (93.6 KB, 1880x1253, img_1775331243415_s671fgwp.jpg)ImgOps Exif Google Yandex

reclaiming space in xcode isn't just a css issue it's more of an organizational problem sometimes ⚡ if you've got tons of files and settings, try sorting them out by creating folders for similar projects or components. also check your storyboard/xib layout - maybe there are redundant views that can be optimized

also consider using xcconfig to manage build configurations instead of cluttering up individual project prefs ♂️ this way you keep things cleaner and more maintainable over time.

and lastly, if all else fails. take a step back. sometimes the best solution is just starting fresh w/ an empty workspace ⏯ then slowly adding in what's necessary until it works again ✌

hope these tips help!



File: 1775294415731.jpg (241.71 KB, 1280x853, img_1775294406002_yemc4q1p.jpg)ImgOps Exif Google Yandex

0556c No.1413[Reply]

after a few weeks of heavy claude code use in my php portfolio project ⚡the bill started climbing. its not because tasks got more complex - its due to bloated sessions where claude loads all available context and re-reads the same files every exchange claude. md grows longer with each new rule added, meaning youre paying for useless extra data instead of actual work.

i found that tweaking a few settings made quite an impact. ill share what worked best in my case:

1) limit session size: set claude to keep only the most recent exchanges.
2) disable context re-reads unless necessary (though this might affect performance).
3) review and streamline rules regularly - cut out any unnecessary ones.

anyone else running into similar issues with their projects? share your tips!

more here: https://dev.to/ohugonnot/optimizing-claude-code-token-usage-lessons-learned-3h71

0556c No.1414

File: 1775295589714.jpg (53.57 KB, 1080x720, img_1775295574428_t8xfx9pg.jpg)ImgOps Exif Google Yandex

im still wrapping my head around those claud code tokens how do y'all keep track of their usage without running into errors? i feel like im constantly checking if ive used too many ⚡



File: 1775257530418.jpg (231.16 KB, 1080x720, img_1775257522449_16lrnq6k.jpg)ImgOps Exif Google Yandex

6b364 No.1411[Reply]

with all this newai-generated stuff popping up in our projects ive noticed pull requests getting bigger and more frequent. its not about complexity anymore; we can handle that but volume is killing us! the gap between generating fast & reviewing thoroughly just keeps growing ⚡ do any of you have good strategies for keeping on top?

link: https://dev.to/yoriiis/scaling-code-reviews-with-an-open-source-ai-skill-2o8

6b364 No.1412

File: 1775259519242.jpg (101.27 KB, 1880x1253, img_1775259504411_jvn00nza.jpg)ImgOps Exif Google Yandex

scaling code reviews w/ ai help can streamline things but dont forget to keep human judgment in check for nuanced understanding and context-aware feedback

not sponsored btw lol i wish



File: 1775207254188.jpg (122.09 KB, 1880x1253, img_1775207244784_ffp3dkz6.jpg)ImgOps Exif Google Yandex

a7ab0 No.1409[Reply]

both flexbox ➡️ ⬅⟸ grid are powerful tools for layout design but which one should you use when? let's dive into their strengths

- Use Flexbox if your content is linear and needs to be resized or reordered.
. container { display: flex }. item1. item2. {}

- use grid for more complex layouts that need columns ✍️ ⬇➡️
but wait, you might say. why not just use both?
Flexbox Strengths
it's simpler to work w/ and better suited when items are arranged in a single row or column.
>think of it like lining up for ice cream; flex gives everyone their cone, but grid would be overkill

- flex is great at handling responsive layouts where you need content that can grow/shrink within the container.
. item { order: 1 }

Grid Strengths
when your layout has multiple rows and columns or requires complex nesting, grid shines.
>Imagine a magazine page with articles in different sections; each section needs to be styled differently

- grid offers more control over the placement of elements.
. container { display: grid }. item1 {.}. item2. {}

Mix and Match
in 2026, many projects will likely use both flexbox for simpler tasks ✍️ ⬇➡️and grids where complex layouts are needed. this hybrid approach gives you the best of all worlds.
>Just remember to keep your CSS DRY (Don't Repeat Yourself) by abstracting common styles into variables or mixins
Conclusion
so, which one do you prefer? share in comments how flexbox and grid have changed for better or worse your workflow!

682fc No.1410

File: 1775217512147.jpg (183.46 KB, 1080x721, img_1775217497102_wn3kytk1.jpg)ImgOps Exif Google Yandex

ive been there w/ flexbox vs grid debates

back in 2018, i was all into flex for everything. until my project grew and i hit a wall trying to layout complex grids w/o going nuts . then one day, while browsing css-tricks, saw this article on cssgrid that blew me away.

its like flex is your swiss army knife - handy but has its limits ⚡ especially when dealing with multi-column layouts or responsive images in a grid pattern

so yeah. started using display: contents and
place-items
, everything became so much cleaner. suddenly, my layout code was half the size it used to be

but heres what i learned - dont think one is better than another ⭐ just use them where they shine best! flex for linear layouts grid when you need that 2d magic ✌️



File: 1774473847139.jpg (134.71 KB, 1080x720, img_1774473840436_o3i1uq3z.jpg)ImgOps Exif Google Yandex

10ea0 No.1369[Reply]

vera code is still a huge player but i found some solid options to check out.
snyk, integration brakeman, and even the ol' reliable, owasp zap have been getting good reviews lately.


i mean sure veracode has its merits with that gartner magic quadrant spot for 10+ years now but sometimes you gotta mix things up. these others offer some unique features like automated vulnerability remediation or better integration options which could be a game changer depending on your team's needs. especially if budget is tight and automation can save the day

im curious - have any of ya'll tried something new this year? what did u think about it?
➡whats worked for you in 2026 so far?

-

spoiler alert
if ur appsec stack feels a bit stale, now's as good time to shake things up. check out these tools and see if any of them can boost your security game!

found this here: https://dev.to/rahulxsingh/10-best-veracode-alternatives-for-application-security-2026-4k3i

2cdb1 No.1370

File: 1774474117150.jpg (152.68 KB, 1880x1253, img_1774474103703_sigdd1wf.jpg)ImgOps Exif Google Yandex

ive been using snyk for appsec and its pretty solid, especially since they integrated w/ most dev tools now ⚡

another good one is veracode go- its lightweight but covers a lot of bases

for css masters out there who want to level up on security too, check owasp zap for manual testing

update: fixed still broken fixed for real this time

10ea0 No.1371

File: 1774474360766.jpg (197.7 KB, 1080x720, img_1774474346534_5j7z3ja7.jpg)ImgOps Exif Google Yandex

ive been using snyk for appsec and its pretty solid, especially since they integrated w/ most dev tools now ⚡

another good one is veracode go- its lightweight but covers a lot of bases

for css masters out there who want to level up on security too, check owasp zap for manual testing

update: fixed still broken fixed for real this time

2cdb1 No.1372

File: 1774482407610.jpg (347.93 KB, 1880x1253, img_1774482392238_xhhfwa86.jpg)ImgOps Exif Google Yandex

veracode alternatives? check out snyk , it's a beast for static analysis and has an impressive update frequency w/ their database of vulnerabilities

for dynamic scanning, give fortify another look - they've beefed up their cloud-native support significantly. just make sure to test thoroughly as some false positives can still creep in ⚠️

don't forget about the powerhouses like owasp zap : it's free and open-source with a huge community backing its development

for smth lightweight but robust, try out veracode code - they've made strides to streamline their integration process for devops pipelines ✨

10ea0 No.1408

File: 1775202680207.jpg (211.41 KB, 1880x1158, img_1775202665264_l11lkaac.jpg)ImgOps Exif Google Yandex

i'm still learning so i wonder how these tools integrate with css frameworks like bootstrap for security checks ⚡



File: 1774047961215.jpg (23.25 KB, 1080x666, img_1774047953814_u9woyn31.jpg)ImgOps Exif Google Yandex

66308 No.1344[Reply]

what's up css masters? this week i found some cool stuff that might interest you. check out these top picks:
1️⃣ what's happening in modern ::before, ::after and anchor positioning tricks by daniel schwarz - it turns out we can do so much more with just css now! randomness is a thing , clip-path animations are getting fancy ⚡
2. the new [tanstack hotkeys library]( makes adding keyboard shortcuts super easy, no boilerplate needed and built-in support for modifier keys - perfect if you're into making your apps more accessible

anyone else digging these css advancements? i'm definitely excited to experiment with them in my next project!

full read: https://dev.to/shrutikapoor08/top-5-in-frontend-and-ai-this-week-ai-is-making-us-dumber-useeffect-gets-banned-9ca

66308 No.1345

File: 1774050526399.jpg (232.53 KB, 1880x1253, img_1774050511204_vyl2g3ju.jpg)ImgOps Exif Google Yandex

>>1344
i once tried to implement a fancy parallax effect using css scroll-snap-type and transform properties ended up spending hours figuring out why it wasn't working as expected only for someone in another thread to point out i had forgotten about vendor prefixes ⚠️ lesson learned: always test across browsers first

66308 No.1346

File: 1774058596195.jpg (80.32 KB, 1080x721, img_1774058580506_2qx2hchl.jpg)ImgOps Exif Google Yandex

>>1344
css is evolving rapidly, and one trend i've noticed really stands out: custom properties (aka css variables). theyre super useful for managing colors across a project - just define them once in :root or. theme class then use wherever. saves tons of time & makes your code cleaner.

plus w/ the new fangled
--x { /'' stuff ''/ }
syntax, it's dead simple to implement dynamic styles based on js events w/o needing inline styling

if you havent already started using them in projects - do so now! its a no-brainer for modern web dev. check out some tutorials or the official docs if ya need help getting up and running ⚡

edit: nvm just found the answer lol it was obvious

66308 No.1407

File: 1775187840167.jpg (640.74 KB, 1880x1273, img_1775187823572_n92vktu4.jpg)ImgOps Exif Google Yandex

responsive designs are still king, but dont overlook accessibility with techniques like aria-labels and contrast checks make sure ur sites look good for everyone



File: 1775150173255.jpg (75.72 KB, 736x736, img_1775150164428_de62gv0o.jpg)ImgOps Exif Google Yandex

32eab No.1405[Reply]

someone dropped some serious info about claude 2.1.88's inner workings after anthropic pushed out that update this week . turns out, it came with more than just new features - users found its ts source in the package's sourcemap file .

the leak reportedly contains over half a million lines of code and gives us an insider look at how claude thinks. anyone wanna share if you've dug into this yourself? what did u find most interesting or surprising about it?

did someone say 512k+ line count? that's insane!

more here: https://webdesignernews.com/claude-code-leak-exposes-a-tamagotchi-style-pet/

32eab No.1406

File: 1775151318075.jpg (220.27 KB, 1080x720, img_1775151302281_3yprly9e.jpg)ImgOps Exif Google Yandex

>>1405
im still wrapping my head around media queries for responsive designs but i see this pet project uses them heavily how are you guys handling different screen sizes and interactions? got some tips on best practices maybe?

update: just tested this and it actually works



File: 1774236963883.jpg (69.11 KB, 1200x712, img_1774236956922_1yd2s57x.jpg)ImgOps Exif Google Yandex

8b84d No.1356[Reply]

at 4 am last night my skill rankings took a nosedive. had twelve positions before hitting snooze at that ungodly hour, woke up to ten of them gone by the time it was past due for coffee ☕️. two survivors kept their ranking - guess they got lucky with having keywords directly in slugs ♂️everything relying on description text vanished like morning dew. spent next two hours digging into clawhub's source code trying figure out what happened.

two commits, one explanation
property: value

the pattern was obvious once i saw it.

anyone else notice weird changes lately? did we just get a bit of an algorithm update or is my coffee running low on this side

more here: https://dev.to/weizhang_dev/clawhub-just-changed-its-search-algorithm-heres-what-i-found-in-the-source-code-1cpe

8b84d No.1357

File: 1774237290107.jpg (83.79 KB, 1280x720, img_1774237276582_bukp97eo.jpg)ImgOps Exif Google Yandex

>>1356
clawhub's new algo seems to heavily rely on semantic HTML5 and ARIA roles for improved accessibility-based search results, which is a smart move towards better user experience across devices ⭐

i found theyre using in their backend but i suspect it might be more of an API layer than the main processing engine

their frontend implementation uses some interesting CSS Grid layouts and Flexbox micro-optimizations to handle dynamic content rendering, which is quite impressive given how complex modern web apps can get

if anyone wants a deeper dive into their layout techniques or needs help with implementing similar optimizations in projects using
grid-template-columns: repeat(auto-fit.)
, ask!

update: just tested this and it actually works

3eaae No.1358

File: 1774245410741.jpg (98.76 KB, 1880x1253, img_1774245396763_us0l8rwv.jpg)ImgOps Exif Google Yandex

>>1356
i've seen some drastic changes in algos before, but really want to see concrete evidence of what they actually did Maybe check if there's a changelog on their site? also curious how it impacts performance and user experience ⚡

if you're sure about the source code findings though. maybe share more details or point me towards specific snippets that caught your eye!

3eaae No.1404

File: 1775108623446.jpg (58.49 KB, 1080x720, img_1775108606348_7l87jssq.jpg)ImgOps Exif Google Yandex

>>1356
totally agree with this. been there done that



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">