"Solve this problem in whatever language you LIKE" - Dylan Beattie but many programmers HATE TypeScript, because it does affect how you think. it's a kind of mental strait jacket. so unfortunately the language does matter and the crimson on accordion analogy is good, just the other way around. i didn't see any accordions behind you, but many guitars instead...

I'm re-writing our bank's COBOL backend in Rockstar 2.0 Beta.

Thank you, both, for the amazing mock interview. I wonder if it is okay to answer the question about availability the way Alexander did. He did not mention the solution availability estimates.

Thank you for yet another amazing explanation!

Reaper is pretty awesome, runs on linux. Resolve does video..blender does...fusion or nuke depending on your needs. I don't really like adobe.

Thank you for the video! Great explanation, took notes

38:45 damn, perfectly described my experience 🥲

Yeah, many now decided that it's a blue collar job that just happens to pay well. We went from "it's an art", because of the super capable high IQ individuals to "it's a trade", because the rest of the population really wants to believe they can do it too. Get it? Still no? Sorry, it's just SO funny. Need to go change oil before the mechanic at the garage has left. Oh, I'm sorry, "automotive industry engineer".

Yes!

Cool 🎉

no need to be

I've always been a bit weary about frameworks and very rarely it's actually helping. In my experience it often ends up creating more problems than it solves.

Inspired by x.com/d_feldman/status/1837180399916573002

So Dylan has not written a line of Java code in "20 years" and he first heard about Firebug in 2004. Sounds like a great new tool ended his career.

мне кажется ты бы сильнее выстрелил если вел интервью на русском и а не на криж-английском

wait, you don't use emojis in your corporate slack?

Wow, surprised to see Kot here! Thanks for the video

Would be great if you gave more details as "why mongodb cost more?" and "what's the alternative?"

Always good to know about failures, we learn here, thx

Please, more videos

Disaster Recovery Interview with Misha Druzhinin: kzbin.info/www/bejne/iIGXe41niaaKbNU

Art is in the details. Yes, paintings that have no other use than to be looked at is often considered art but that's only because it lacks another classification. Art is in the eye of the beholder and there's as much chance now that someone somewhere sees art in software as there always has been. Outside of old men waxing poetic about how good things used to be nothing has changed in that aspect. Don't get me wrong, many things have gotten objectively worse over time but software as art hasn't died just because it is no longer the domain of the sweaty neckbeards. That's not a jab, I'm probably in that category myself. The main difference is that technology has gone from enabling people to do wonderful things to a tool used to oppress. Software today is just as capable of producing wonderful and unique masterpieces but the pressure to get on the hamster wheel has never been stronger. In fact it might even be more capable since open source software is one of the last ways disrupt societal norms by providing alternatives when companies overstep.

what a show, i really enjoyed that. Dylan reminds me of myself.

This video came at a perfect time for me, so much value in this knowledge. Thanks!

@33:50 I literally have winamp open, been using since 1998

Great tips ❤

Nice!

Thanks! Very useful.

thank you! really useful tips

My main tip: go to companies which don't ask system design. Works pretty well on senior and below positions.

Anymore? I think it wasn't art since we stopped using assembly exclusively.

really nice video

Really helpful advice in the video. Thank you, appreciate it. I recommend it for every developer

👀👀👀

❤❤❤

15:30 is a great point. When I got my current job I struggled for a while because I wasn't familiar enough with the industry. Then people talk with specific jargon, use acronyms and specific terms and you are there writing them all down so you can try to decode later what was communicated :D Languages, frameworks etc. are tools, and the domain knowledge is way more valuable in my opinion than knowing the tools.

These sound kind of interesting and I'd say I can already do a lot of it, for what kind of jobs would this be an interview for? This is one part of what is taught to software engineers in academia, so would it be software engineering jobs? Or perhaps something more higher level like architecture?

Great video! I've been struggling with architecture interviews. These tips were super helpful.

A very interesting episode, thank you !👏

18:55 - Wait, but I might be traveling and would like to order a ride for my teenage kid who is in my home city but needs to go to school - a pretty valid situation but will be recognized as a fraud.

This was an excellent discussion, lots of this resonates

I think focus is too much on the technology. I'm a .NET developer, 10 years of experience, and I see that a lot of devs still struggle with technology and producing code - and they are not even nerd who live for programming. They struggle to finish tasks, not delivering features that matter. They never grow past that and have the interesting conversation about software design and so. I rarely find someone who I can talk deeply about software development or even the technical side. And now companies seem to look for these people that I mention since they are the ones delivering without questioning the meaning of what they do.

Software Engineering is never an art. It is what it always was, is and will be - ENGINEERING

Didn’t use VS/Windows for 7 years. Rider, Mac, Linux

"yeah ! programming is awesome ; just it sucks when you do it for a living" So true !

Software is not a art, its software. Yes, it can be like a art, but it was meant to run computers, not make you feel like the next Michelangelo.

not buying for a second that a guitar player could learn accordion faster than a master accordion could learn all those songs...

You should see some of the massive, profit generating, and quite scalable systems I have written using... BASH. No, it's not the only language I know by a long shot, but depending on the domain of the problem, it can be all the tool you need, when used properly. Tools are just that. Sometimes good old tie wire is better than a custom fabricated bracket or zip ties, also.

I keep agreeing! I often get asked for C++ projects as freelancers. And my first question always is: “what is it that they are developing?” Because my background is in medical, graphical and low-level systems/embedded. I don’t know about simulation of traffic and tunnel emergency systems. That was the last requests, and the head hunter (they should not exist absolutely useless middle man)) was like but C++ is C++… And I couldn’t make him see that C++ was just a tool. I can have a screw driver and be a luthier that doesn’t mean I know how to build for example houses. We are technically both carpenters and some knowledge translates but they are two very different domains of carpentry. We both use viles, saws and routers but we use them so differently.

Oh man web dev in 1995, that was when I started to hate the web. Perl cgi-bin, mSQL. Capturing the HTTP request to get the tokenized arguments ugghhh…. And using tcpdump to see what dynamic sql was generated and what web requests came in and out. React and C# Blazer improved it but it’s still not as flexible and robust as just desktop software. I still hope WASM will take off, where we can just developed desktop applications (that are blazingly fast) with whatever library and it would be smart enough to abstract that into wasm. But…. The problem is the fact that each OS has a different way of professing graphics and to cross compile say Qt (I love it) to then have some web graphic abstraction is really hard. We should have a unified Graphics api that works on everything and is really simple like we used in DOS, just a memory block you write your data into per pixel. Your graphics/ui libraries can actually compile to render that and wasm can then easily use that. We went too far with idiotic abstractions. Why is it so incredibly hard to just render a single pixel through hardware these days?! All the proprietary GPUs uggghh