fernandotakai

some social media grifters are boasting this amount of work -- mostly young ai startup founders.

the trouble is, for the amount of work these people claim they are doing, i'm not seeing actual things being shipped.

orbstack is absolutely amazing. not only the docker side works much better than docker desktop but their lightweight linux vms are just beyond great.

i've been using an archlinux vm for everything development over the past year and a half and i couldn't be happier.

almost the same reason i started using arch: i wanted to install linux into my macbook, and the only wiki with enough info to make it work was arch's.

django is the framework that made me fall in love with software development 18y ago.

everything just worked out of the box (compared to using java + spring and their endless xml config files), the orm was (and still is!) lovely compared to other solutions, and there were so many things included, that i never really had to go integration hell.

kind of of topic, but i had to google to find out which female part rhymed with dolores, because it made no sense to me (as an ESL).

(for people wondering, it's clitoris).

https://seinfeld.fandom.com/wiki/The_Junior_Mint

https://seinfeld.fandom.com/wiki/Dolores

i don't know about you, but i would never EVER submit a PR that fails to compile. not tests are failing, those happen (specially flaky ci), but not compiling.

that's literally the bare minimum.

you can also use stern for that!

https://github.com/stern/stern

you can use double dashes to symbolize an em-dash (i prefer to using an actual em-dash, which is option+shift+- in macos).

https://en.wikipedia.org/wiki/Dash#Approximating_the_em_dash...

uh, really?

i really like using em dashes -- for some reason, it feels "better" in my head than using something like a comma or a semi-colon.

for me, atuin's history sync is a huge must since i use 5 different machines across my house.

yeah, android authority has said that 2025 is the last year of old google assistant. i dread having to use gemini every single day.

https://www.androidauthority.com/google-killing-assistant-35...

if people want more info on these devices, russ from retro game corps does a ton of reviews on them, from the cheapest (that are less than 30 euro) to the really expensive ones (600+!).

i myself own a retroid pocket 5, one trimui brick (which my wife adores) and a steam deck (yes, it's an amazing retro gaming machine).

(retro catalog also has a ton of technical information, including ratings)

https://www.youtube.com/@RetroGameCorps

https://retrogamecorps.com/

https://retrocatalog.com/

>In fact I'm afraid they'll break it by shoving down Gemini.

i have a pixel 9 with gemini. i absolutely hate it. google assistant is miles ahead.

and btw, i'm not the only one complaining https://www.reddit.com/r/GooglePixel/comments/1jdpvnq/gemini...

>Some people are really fetishizing iterative failure - but just because you are wandering in the desert does not mean there is a promised land.

i guess you didn't follow the falcon 9 failures right? here's two minutes of failures https://www.youtube.com/watch?v=bvim4rsNHkQ

and guess what? they finally got it right and now falcon 9 is not only extremely reliable but quite cheap for everyone.

NASA (with the shuttle and saturn V) had a completely different idea on rocket development (and blue origin seems to follow their mindset), which is fine. but to say that this is "failure fetish" when spacex has an amazing track record is just hating for the sake of hating.

i would recommend, if you have the time, the book liftoff, by eric berger https://www.amazon.com/Liftoff-Desperate-Early-Launched-Spac... -- it was the book that opened my eyes to why spacex works like they do.

i still can't believe they can actually catch that first stage. it makes no sense, but works!

another solution for fuzzy finding is telescope.nvim https://github.com/nvim-telescope/telescope.nvim

the thing i like the most about it is the amount of plugins you can add (including things like looking at nvim's paste ring).

i felt for ding, even though i was cheering for gukesh.

i was so sure it was going to go into tiebreaks.

from my own experience, running stateful services in k8s is not easy and prone to errors.

so unless your devops/sysops/whateveryouwannacallitops has a lot of experience, it's just not worth it when things like RDS/ElastiCache exists.

i worked at a place that was 100% k8s, but all stateful things (redis, mysql, rabbitmq) were either hosted or in VMs.

>That doesn't mean that no one should ever ask questions like that. If the candidate explains that they can't think of the answer at the moment and why, and if the interviewer doesn't hold that against them (as long as the explanation is valid), then it's okay.

that's totally ok for me. that's why those are only two of the questions i usually ask, not all of them. i think saying "i don't know" is just as valid as any other thing.

as i mentioned elsewhere in this thread, these questions are "conversations starters" and the good data comes from the subsequent questions.

so if you said: "i can't come up with anything" i would probably ask about the last interesting project you worked on. or what was the last programming language you tried to learn.

interviews are not only for probing for tech knowledge, they are also about getting to learn about each other :)

i disagree with you 100%.

maybe for the jobs you are applying this is true, but for the places i've been searching for candidates, there are only answers and those answers will tell me (and other people in the pipeline) what to think of you.

for my own process, answers are only data points and the whole point of interviewing is looking at datapoints and getting to an answer. it doesn't mean "the person that get everything right gets the job".

once, i got a person that was incredibly smart, but they where not a cultural fit. we ended up hiring someone with less experience, but that person fit perfectly within the team.

the first person answered everything perfectly, the second didn't.

you totally got it btw -- because questions should be conversation starters, not just "question -> answer" ad infinitum.

when i ask about a bug, i just want to know how you go debugging, understanding logs, dealing with other frustrated developers... you know, how you deal with things in a day-to-day basis.

the first one: depends on experience! i had a guy answer with a kernel nevel bug that honestly, i didn't understand the fix.

the second one: i think most (if not all) developers have at least one strong opinion -- even if it's just "i don't like javascript".

see, interviewing, for me, is not about right answers, it's about getting to know the person and getting to see how they approach different problems. these are just two of the things i might ask, depending on how everything is going.

>Does that say anything about me, according to your filters?

i don't know, i never saw your resume, i don't know your experience and we've never talked before. maybe it just means we have to have a 15min talk before i could ask those. and there's something i always tell every single candidate i've ever interviewed: there are no wrong answers -- if you don't know, you don't know.

i disagree. i've been a dev for about 17 years now, and i remember a bunch of random stuff that i had to fix that were super interesting.

and honestly, it's not about the specific answer: it's about creating enough conversation that you can understand the person. i usually use these two with senior+ engineers, but if i'm interviewing someone more junior, i will ask something different (like, what are you learning right now? what do you wanna understand over the next 12 months? is there anything that you currently do not like in tech?).

> Agreed. What are the questions you ask to determine their detective abilities?

in my experience, talking to a candidate across a couple of rounds and asking some generic question that can create discussions, will get some answers. sometimes, designing a system together can help a lot (as always reminding the candidate that there are no wrong answers).

at the end of the day, interviewing is a flawed process and you will get it wrong -- the question i don't see being asked is: what do you do if you get wrong?

my two favorite questions for interviews:

"what's the favorite bug you've ever fixed?"

and

"what's your strongest opinion in tech?"

why? because they are open answers and 99% of the time they bring really interesting discussions to the table, which can lead to understanding the candidate better.

also, they are good filters: if they say "none" and "none", i know what to expect.

i was actually playing with hetzner and k3s over the weekend and found this https://github.com/vitobotta/hetzner-k3s to be super useful.

you are talking about two different things here: availability vs cuisine.

it's super easy to go to albert heijn and get really tasty ingredients and cook amazing food. it's also super easy to find great restaurants that are not dutch, and get incredible food (shout out to tacolindo, in amsterdam west).

but dutch food is incredibly bland, focuses way too much in things like mashed vegetables with sausage. you can only eat so many stamppot until you are done with it.

even dutch people say that while yes, you can cook literally anything you want (my wife and i cook brazilian food literally every day), natives in general do not do that.

sometimes, i want to share a script with a friend or with a coworker and setting everything up from scratch is such a pain.

this makes everything SO much easier.

when i moved here, people told me the greatest issue with the country was not the weather, it was the food. and i remember saying "there's no way it's that bad".

after being here for 2y, holy shit it's true. one dutch coworker said "we just eat for fuel, not for taste".

thankfully it's quite easy to buy amazing ingredients and just do really tasty home meals.

> (don't complain about our pannenkoeken or stroopwafels though, unless you're looking for a fight).

i would also say dutch bar/finger food is delicious. it's impossible not to have bitterballen while having a beer.

> Following a nominal ascent and stage separation, the booster successfully transitioned to its boostback burn to begin the return to launch site. During this phase, automated health checks of critical hardware on the launch and catch tower triggered an abort of the catch attempt. The booster then executed a pre-planned divert maneuver, performing a landing burn and soft splashdown in the Gulf of Mexico.

from here https://www.spacex.com/launches/mission/?missionId=starship-...