Untitled

[tomasbucek]

incognito mode doesn't hide your browsing. it just doesn't save it locally. your ISP knows. your network knows. the websites know. you're not invisible, you just didn't write it down.

but sure, proton everything on one side, chrome incognito on the other. we are not the same.

[tomasbucek]

CSS interviews will ask you about things you've definitely googled at work and will google again.

the ones that actually catch people: position absolute vs fixed, display none vs visibility hidden, em vs rem vs px. not because they're hard but because the difference only clicks when something breaks in production and you have to care.

flexbox and grid aren't rivals. one direction, flexbox. both directions, grid. done.

[tomasbucek]

Valid troubleshooting method honestly. Have you tried telling it everyone likes it.

[tomasbucek]

UX and UI get used interchangeably by people who have never had to sit in a room where both teams disagree.

UI is what you see. UX is whether what you see makes any sense. a product can look immaculate and still make you want to throw your laptop across the room. that's a UX failure dressed up in a good UI. the reverse also exists: something functionally brilliant that nobody uses because it looks like it was designed in 2009 and never updated.

the brain split is actually pretty accurate. UI lives on the surface: visual design, layout, components, making sure the button looks like a button. UX lives underneath: why is the button there, who is clicking it, what did they expect to happen, did it happen, would they do it again.

one without the other is either a pretty thing that doesn't work or a useful thing nobody wants to touch.

[tomasbucek]

We survived predators. now we have a panic attack when the wifi goes out.

[tomasbucek]

the bug was on line 47. you spent three hours on lines 1 through 46.

[tomasbucek]

cloud engineering looks like a lot until you realize it's really just a few questions asked over and over. where does this live. who can touch it. what happens when it breaks. how much does it cost.

everything on this roadmap is just a more specific version of one of those questions. networking is about where things live and how they talk to each other. IAM is about who can touch what. monitoring is about knowing when something breaks before your users tell you. infrastructure as code is about not having to answer all these questions manually every single time.

start with the fundamentals, pick one cloud provider and actually use the free tier, get the AWS Cloud Practitioner cert first because it forces you to learn the vocabulary before the technical depth. the rest builds on itself faster than it looks.

[tomasbucek]

there's a version of the "learn to code" boom that nobody really talks about. somewhere around 2012, coding bootcamps started selling a very specific promise: six months, a career change, six figures. the pitch worked because it was true often enough to be repeatable.

then it stopped being true as often. not because the skills became worthless, but because supply caught up with demand faster than anyone predicted. a generation of career-changers all arrived at the job market at the same time with roughly the same portfolio projects, the same tech stack, the same bootcamp credentials. junior developer roles started getting hundreds of applications. hiring bars quietly rose. the entry-level job that was supposed to be the finish line kept moving.

the bootcamp industry didn't really acknowledge this. the ads kept running. the enrollment kept happening. the promise stayed the same even as the outcomes got harder to replicate.

it's not that learning to code is a bad idea. it's that the industry built around teaching people to code had a financial incentive to keep selling the 2015 version of the job market in 2023. and a lot of people made expensive decisions based on that.

this pattern has a name in other industries. in tech we just keep acting surprised every time it happens.

[tomasbucek]

python lists are one of those things that look simple until you realize you've been doing them wrong for six months.

append() adds one thing. extend() adds many things. insert() adds something exactly where you tell it to. remove() deletes by value. pop() deletes by position and hands it back to you on the way out. sort() and reverse() do exactly what they sound like, except they modify the list in place, which will bite you if you're not expecting it.

that last part is the one people learn the hard way.

[tomasbucek]

the thing nobody tells you about breaking into tech is that "where do i even start" is actually the hardest part. the learning resources exist. the roadmaps exist. what's paralyzing is that there are four completely different directions you could go and none of them are wrong.

web dev if you like seeing things you build. data analytics if you like finding patterns in chaos. cybersecurity if you have a slightly adversarial relationship with systems and want to get paid for it. app dev if you want something in people's pockets.

pick the one that sounds least boring and start there. the fundamentals overlap more than people think anyway.

[tomasbucek]

The waterfall kids planned for six months, built for six months, and shipped something nobody wanted anymore. the agile kids shipped something broken in week two, fixed it, broke it again, and somehow ended up with a product people actually use.

there's probably a life lesson in there but we're a software blog so we'll leave that alone.

agile vs waterfall isn't really about methodology. it's about your relationship with being wrong. waterfall assumes you can think your way to the right answer before touching anything. agile assumes you can't, and builds that assumption into the process.

One of these is more honest about how humans actually work.

[tomasbucek]

The open-source education pipeline is unhinged in the best way. free courses, free books, free everything. devs are out here building the future and asking for nothing but stars.

[tomasbucek]

I think realistically, the thing that breaks the music industry's back isn't piracy. It never was. The real culprit is something quieter and harder to litigate against.

For context: when Napster got shut down in 2001, the industry celebrated. They'd won. Except revenue kept falling anyway, straight through the 2000s, through iTunes, through legal downloads, through all the solutions they'd fought for. The piracy argument was always a little too convenient — it gave the industry a villain to sue instead of a structural shift to reckon with.

The structural shift was this: music became ambient. Background. Infrastructure. Something that plays while you do something else.

Streaming finished what mp3s started. Not by stealing music but by training an entire generation to expect it everywhere, frictionlessly, for almost nothing per listen. Spotify pays rights holders somewhere between $0.003 and $0.005 per stream. The maths only work at a scale that maybe a hundred artists on the planet can achieve. Everyone else is treading water and calling it exposure.

Now look at what's happening to writing. And visual art. And soon, probably, a lot of other things people used to be paid to make.

The threat isn't that AI is stealing work, exactly. The threat is that it's making creative output ambient. Functional. Background noise that costs almost nothing to generate and therefore becomes worth almost nothing to pay for. You can argue about copyright law all you want. The industry fought piracy in court for a decade and won every case, but lost the war anyway.

I don't think this one ends differently.

[tomasbucek]

Why think… when you can prompt?

#AI #Productivity #Tech

[tomasbucek]

when I say I work with models I mean it differently than you think 💀

[tomasbucek]

okay so for anyone who's ever looked at a cloud architect job posting and thought "what does ANY of this mean" — this is for you.

it's actually not as chaotic as it looks. you start with the basics (Linux, networking, a little Python), work your way up to actual cloud platforms like AWS or Azure, learn how to stop doing things manually with Infrastructure as Code, get into containers and DevOps, and eventually you're designing the kind of complex systems that keep entire companies running.

it's a long road but it's a real one. step by step, no gatekeeping.

save this if you're even 5% curious. future you will know what to do with it

[tomasbucek]