226
submitted 6 months ago by to c/webdev@programming.dev
 
 

There exists a peculiar amnesia in software engineering regarding XML. Mention it in most circles and you will receive knowing smiles, dismissive waves, the sort of patronizing acknowledgment reserved for technologies deemed passé. "Oh, XML," they say, as if the very syllables carry the weight of obsolescence. "We use JSON now. Much cleaner."

227
 
 

A UX strategist is supposed to bridge business goals and user needs through high-level planning. They’re meant to answer questions like “Should we build this?” and “Which problems matter most?” before anyone opens Figma.

In practice, most I’ve worked with excel at one thing: not committing to answers.

“Should we prioritize mobile or desktop?” “It depends on your user base.”

“Which feature should we ship first?” “It depends on your business goals.”

“When should we launch?” “It depends on market conditions.”

Every answer buys them more time to conduct another research phase, run another workshop, build another framework. They become professional question-deflectors who get paid to suggest you need more information before making any decision.

And here’s the thing – they’re not wrong. Everything in product development genuinely does depend on context. But when “it depends” becomes the primary output of someone earning $120-180 per hour, you’re not getting strategy. You’re getting expensive procrastination.

228
 
 
229
230
 
 

Looking for recommendations for developers who have been around a few years and stagnating a bit. Searching around I just get the same recommendations over and over so please don't say "Clean Code" or "Pragmatic Programmer".

231
232
233
 
 

Can you recommend a CSS framework that feels lean and modern like Pico CSS but isn’t only targeting small form sites?

234
 
 

It's easy to prevent it client-side, but does anyone know of a server-side solution because we should not be trusting data from the client?

235
 
 

Lmk lol

236
237
238
239
240
241
242
243
244
 
 

Most SPAs seem to only serve one or two 'soft' navigations after the initial 'hard' navigation (the one that loads the entire app upfront), meaning the cost is not being amortized across many requests, negating the whole point of the architecture.

245
246
Rethinking SVG icons (olliewilliams.xyz)
247
248
249
250
view more: ‹ prev next ›