brunooliv

Ohh damn... Mixed feelings now I'm super happy that you liked the pasta!! And I'm super sad the numbers are cropped! I did do a layout check... I'll investigate. If I can fix it, I'll send you a free copy. I'd just need your address. Thanks so much for buying and for having liked!!! My email is olivbruno8 at Gmail so if you drop me your address I'll ship you a fixed copy when I get to fix it! Thank you for this!! You and family loving it is a great, great way to start my day. Thanks!

I hope you'll enjoy the recipes!! Lmk! Thanks a lot!

Thank you!!! I hope he will like it! A review could also help with increasing discoverability maybe

Here it is: https://www.amazon.pl/dp/B0CNNLCPZ4

My guess is that probably the search bar isn't indexing all locations properly as I've checked all the checkbox I needed... This might be a problem for discoverability, I'll need to investigate

Hey, There are definitely recipes there, I'd wager even closer to 10 recipes, that meet your requirements :D And I honestly think you'll love the book given your requirements ;)

PS: I'm also a programmer eheh

Hey thanks!!! This is my first time ever publishing a cookbook so this type of feedback is really good!! Thank you!! If you'd like I could send you or email you a free copy of the book, while I work on a better blurb

Thank you! Indeed, it was a huge effort and after around 6 or 7 shorter stories on which I've given up many times before, this finally made it to the end!

Make sure there's more to your life than only work. Work to live, don't live to work. I used to think this was bs, but, after scaling back on work hours and filling them up with time for my own hobbies and side projects all not work related, I think I'm even more productive at work than before

Haven't read the article yet. Whenever I'm working on a feature branch, I always tend to "merge master into the feature branch". The effect of this obviously being that I want to have the latest changes incorporated into my work to avoid conflicts and/or to proceed with my own feature work. This has always worked well for me and never failed me.

If I understand what rebase does correctly, it just adds all my commits in my remote feature branch to the HEAD of the branch that's being rebased onto. That's why after doing it and finishing it, one needs to do a push force because the head of the remote feature branch would diverge. But... Why? How is this better or different than just merging master into the branch? Gitlab for example and Intellij show all the branch changes and commits with their hashes so it all can be cherry picked or reverted if needed quite easily...

Has anybody who used to "merge master into" and now uses rebase that has a much different view on it being better?

People who live for short tenured stays at FAANG companies and optimize their time and skills exclusively for interviews?

I've always enjoyed cooking a lot, and, for a while, I've been thinking on how to turn all my recipes I've ever cooked into a format that's easy to share with others and maybe, inspire someone else's cooking journey!

The cover, font choices and overall layout were hashed out together in long chats with ChatGPT-4. I am happy with how it turned out!

I'm not a lawyer and have no experience with the area.

What I can at least advise here, as someone who is a developer, but, also used to writing a lot of “copy” for my company, is that you hire someone who is a professional copywriter and who can fully proofread your texts.

I'm speaking as a European, non-native English speaking/writing person: there is something that feels extremely “sketchy” when reading English written content that doesn't feel “native”-ish. Maybe this is just my perception as a foreigner, but, it can truly, really affect the traction you get versus what you expect or could get.

Interns and new grads are different from "externally" applying to a "junior developer" role which just doesn't exist. It goes from there to medior

Not my experience at all: ALL levels, besides maybe junior which kind of doesn't really exist in Big Tech, require system design, so I can't really relate to this. Algorithms are usually about specifics of what the company itself does, so expect graph traversals, networking, file system stuff etc, disguised as a puzzle depending on the company. Nobody will ask you about "generic algorithm questions" and actually the "topics" are quite narrow.

What I'd like to know and see written down is how you truly prepare for system design when you DON'T HAVE or CAN'T GET experience with large scale systems at your DAYJOB. The chasm here is that when competition is other 20 engineers who just memorize things, even if their actual relevant skills are objectively worse than yours in practice, you'll never, ever get the job. It's a very tough game and I admit there is real skill in knowing how to game the system :) it is what it is.

PS: I know exceptions are everywhere but I'm sure that the quality of the ones who get in vs rejected will be basically the same. It's just a process optimized to minimize false positives, so, only the median will get in, really good ones will be rejected and only maybe a very small fraction of the ones who make it through will be "The real deal".

Cheers!!

Claude Shannon maybe?

Damn. If you're producing this type of content at 17, I can't even imagine the amazing things you'll be able to do it you choose to pursue the field professionally. Absolutely amazing!!

What are the implications in general of room temperature superconductors? I just know that they needed typically ultra low temperatures right? But what would be the practical implications?

I think this hits the nail in the head for the argument I was trying to make: if you as a candidate feel the process is too long or daunting for you, you don't have to attend. It's that simple. Why would you expect compensation if people will do it for free or because they just want to take a shot at the job? To me it truly feels like entitlement... And of course the vast majority of us, myself included, can apply to "lesser known" companies, be done with interviews in a couple of days and it'll all also be good... Obviously compensation will come according to the effort... Demanding money for providing just a signal is useless

Why do you expect employers would pay you? I mean, what if you don't pass it, or even worse, what if the company offers you a job that you decline near the end? Where would the money go? Receiving a salary is not the thing you can expect when you're not doing the work... I mean cmon.. Plus the real salaries upon landing the job will be the top of the crop, so, I think expecting payment for interviewing is... Quite the entitlement.

I mean, would you pay money to a handyman if he'd show up near your roof and showed you how he uses his tools and how he WILL EVENTUALLY work, but, not really fixing it?

My stance is really not in favor or against using (or overusing) a word from a "blacklisted" set, it's more that usually the structure doesn't cater well to the audience and on top of that it adds a lot of unnecessary fluff. If I need to download X dependencies but two of them need to be version 1.2.3, by all means tell me it's all super simple to do, idc, really. But give me the exact dependencies that NEED that version for the thing to work. Worse than this unnecessary fluff and eagerness for simplicity or wtv is having incomplete instructions that lead to a non-working setup by the end. Proofread them by EXECUTING them and then, as long as it works, be a Shakespeare about it. There seems to be a lot the expectations of things being broken and a kind of tragedy of the commons being the standard.

Thanks for the reply and I meant it from similar experiences at my $DAYJOB where any initiative like this always uncovers a lot of dusty corners! Thanks for the great and polite reply, it's rare nowadays, so kudos!

Not to criticize your POV and argument directly, but, in the end, a lot of things, especially like these, are always easily subjected to the "we could do it, but just didn't bother to yet" kind of argument, and, when it comes down to the real work, things are much harder than they superficially appear to be. So yeah this isn't new... But... You know eheh

I will read this as it seems really good. However, it always feels like a catch-22 problem to me, in the sense that, if you've never worked at a large company before, you can't claim to have truly used or understood large scale systems properly to work on them or design them in production.

I got rejected from a large tech company after failing system design and this was exactly their reasoning: "you seem to know the concepts and the theory really well, but, it was obvious to the interviewers that you lack the real world experience and hiring you would be a risk".

Obviously I... knew or at least tried to know the theory because I PREPARED. I read books, articles, practiced mock problems, watched YouTube for a few weeks, etc, etc. I just tried to "drill" the knowledge that was not there into my brain for the purpose of passing the interview. I guess that's what a lot of people do.

So yeah, it left me really down for a few months and feeling bad about myself and like the world sucks. So, how are you all out there "faking it till you make it" in a convincing way?

Because I bet that no engineers at a FAANG will alone design a full scale system on their own ever, so I doubt the usefulness of the "signal" these interviews give, but, ofc, that's just me, someone who prepared for months and failed

Not to be the devil's advocate or something, but, I hope you understand that the vast majority of FAANG engineers CAN'T build any highly scalable system from scratch, much less fix bugs in the Linux kernel... So that argument feels really moot to me... If anything this just shows hopefully that gatekeeping good engineers by putting these LC puzzles as a requirement for interviews is a sure way to hire a majority of people who aren't adding THAT MUCH MORE value than a LLM already does... Yikes... On top of that, they'll be bad team players and it'll be a luck if they can string together two written paragraphs...

Damn, these articles are awesome!! I recall once, when I was still green in the field, while at university having read one of his articles and having been surprised at the way it was written even if I couldn't digest the technical content... Now that I've stumbled upon his articles, 8 years later, does anyone know if he has an archive of all his articles somewhere? I suspect I might be in for a very nice journey...

Will give it a try! Want to use it on top of replicas of our work production DB like in an exploration day setting and see what comes out of it, looks awesome!!

Can Datasette be used with a Postgres RDS database with hundred GBs? Feels like it's mostly designed for smaller things? Also if it can, how would I go about it and if it can't, any similar tools I can use? This looks really cool!!

The biggest one has to be design patterns in OO design!

I was fortunate to have a great teacher which taught OOP by focusing on design patterns, dynamic dispatch, composition over inheritance, etc, etc, the really foundational concepts.

I was too young and naive to fully understand all the concepts, I just thought writing Java was cool! Ah.

Many years later, I really realized how to apply design patterns to solve real problems in a large production codebase and it all clicked then and in retrospect that teacher was really amazing, I just was too naive to realize it back then...

How to run async workloads in Springboot