retired electrician

@shipilev Sounds like a very very weird way to make GIFs

Hα Sun time-lapse, the first of hopefully many. 1 hour of data acquisition (modest 30K frames, 130 GB raw), 8+ hours of processing (includes a few false starts). Full-size video, workflow details, etc: app.astrobin.com/i/59uc7v

Печёнка это праздник.

a moment in time

1980s Sony compact cassettes are forever cool.

@mr_mig_by Нахуя быть умным? Я слышал кожаные мешки от ума только страдают)))

Считаю, что человека можно назвать умным только если он сдал эпистемологический минимум IQ, эрудиция, степени не считаются Не умеешь отличить “я знаю” от “мне так кажется” - ну штош…

@nikalaikina @kado4nikov Интересно, а как определить свежесть писи? 🤔 Какие там метрики? Просто интересно)

@kado4nikov Сиси к сожалению предложить не могу

Что она может предложить мужчине с зарплатой больше 10 тыс долларов? Пися (не первой свежести), две сиси, возможно киловатты космической энергии, поддержку и мотивацию.

Блять

Mood

HIGH-QUALITY APPS WITH JUST A PROMPT!

@nikalaikina Не. Не боюсь)

Мне нравится когда мне говорят "ты просто хочешь детей потому что боишься смерти" ну да?? А ты не боишься или что??

@nikalaikina I like your style you make me smile

Почему вы меня любите

Когда словил клода за жопу!

I've been coding for 40 years. Here are the top 5 things I wish I knew when I started. 1. 90% of the job is debugging and fixing, not creating new code. Which is still fun if you're good at it. I used to think programming was mostly writing fresh, clever stuff. In reality, most of your time is spent in other people's (or your own past self's) messy code, chasing down why something that "should" work doesn't. Get really good at debugging early. Learn assembly reading, call stacks, and kernel debuggers. It pays off hugely. The best engineers I saw were absolute magicians at this. 2. Manage complexity from day one (ie: don't write slop and "fix it later" if it goes somewhere). Very early on, I'd hammer out code and refactor afterward. Big mistake. Now I start with clean, skeletal structure (minimalism first) and flesh it out carefully, with AI or not. Messy code compounds and becomes unfixable. Upfront discipline on architecture, naming, and simplicity saves enormous pain later, especially in large systems like Windows. 3. Tools and processes matter more than you think We suffered with basic diff/manual deltas instead of modern source control like Git. Branching, testing, and good tooling would have made porting and collaboration way smoother. Invest in your environment, automation, and reproducible builds early. Good tools amplify your output; bad ones (or none) drag everything down. 4. Understand the problem and existing code deeply before writing Don't jump straight to coding. Map out the problem, study what's already there (you'll inherit a lot), and plan. Low-level knowledge (hardware quirks, alignment issues on different architectures like MIPS/Alpha) was crucial. Also: assert early and often. It forces clarity. 5. People, politics, and "the right tool for the job" beat pure tech arguments. Brilliant engineers still argue endlessly. Sometimes it's about ego, not merit. Learn to spot the difference and "steer" the conversation rather than "winning" it. Bonus from experience: Side projects like Task Manager (started at home because I wanted the tool) can become your biggest hits. Ship small, useful things often. If you're just starting, focus on fundamentals, patterns over syntax, and building resilience for the long haul. It's going to be a wild ride, but the fundamentals still matter.