luuuzeta

>I wanted to hear more stories about the early days of startups, so I started working on a book of interviews with startup founders. The book was called Founders at Work, and was published in 2007.

I might've to give Founders at Work a read. A book with a similar theme is Coders at Work, a series of interviews with some well-known people in the computer science and programming world. Highly recommended!

I'll be looking at your notes and see if I can find some inspiration. I've thought about such a system but instead of a flat README, I'd have a directory for each note with a README and accompanying assets (code and images). In the root directory, I'd have a table of contents linking back to each particular directory.

My main issue with taking/making notes is that now I must worry how to store and organize them. Back in college I'd take them in a notebook, review them for exams, and then get rid of them by the end of the semester. I've tried blogs (static site hosted on gitlab), markdown files with Vimwiki, Obsidian, and now I'm using Notion. The common thread among all of them is worrying about how to organize them (e.g., file structure, tags, by topic, etc).

The YouTube channel "Think Before You Sleep" has some videos related to this topic.

>A possible solution would be an app with no chat component whatsoever, strictly just matching for dates in real life - you have to take seriously.

How do you exchange info though? What about an app where people match and they're only alloted a single message (e.g., to exchange contact info, meetup place, etc), after which they cannot chat with the other person anymore?

Funnily enough Z-Library made it easy for me to buy physical copies of books I wouldn't have bought otherwise.

That would be creepy and next level.

Isn't that what Musk's Neurolink is trying to achieve?

I'd be so self-conscious with my speech being recorded roughly 24/7 by myself. I'd probably get used to it but it'd take some time.

Oh no, I manage to squeeze more activities into my days and I've a hard stop by 4:30PM-5PM. I exercise, read, watch stuff, run errands, etc. after I'm off.

Oh these are good ones.

>When you do work, demo it to your team and ask for feedback.

I always ask for feedback for my PRs, however they're small enough they can be covered with a few screenshots or simply looking at the code. So do you think it's still worthy to schedule demos for them?

>Cameras on when other people have them on - I'm not the biggest fans of cameras but it would be good for a junior for people to put a face to a name.

Me neither but I always try to have my camera on.

1. Great! This is something that might team does. We've alternate async and sync stand-ups.

2. Right, always on Slack during work hours. Also be available to jump on quick Hurdle/Zoom meetings.

3. My PM encouraged me to do this more often. I was hesitant because being a junior I didn't think my opinion held any weight, but I'm trying to do this more.

4. Gotcha! I'll keep this in mind :)

5. Thanks for mentioning this, and this is something I like about my team. I'm the most junior among all the devs in my team but they're always willing to help.

6. Certainly!

Thanks a lot for your advice :)

Thanks for your video! After I finished watching it and going to your channel's page, all I could think about was "Wow I hit jackpot".

Funnily enough "The Story of React" started playing right after, and I didn't even notice I was listening to another video.

Mathematical proofs didn't click for me, so much so that I ended up failing my Discrete Math class because of it. Before I retook the DM course again, I took a Proof Workshop but I doubt I would've done good without the following books:

* Richard Hammack's The Book of Proof [1]

* Mathematical Proofs by Chartrand, Polimeni, and Zhang

[1]: https://www.people.vcu.edu/~rhammack/BookOfProof/

I'll check it out. Thanks for the recc.

You're welcome! Rewatch Philip's video as many times as you need until the concepts sink in, before you move into learning promises and await/async [1]. Similarly for Jake Archibald's video.

Good luck!

[1]: from what I gather asynchronous programming using callbacks isn't used anymore but it might be instructive to start with it, understand the issues with it, and why promises replaced this style.

Thanks a lot, I'll keep this in mind and try to write as much async code as possible.

>One day you'll realise it's second nature.

This is great but then the curse of knowledge hits you hard haha

I've realized it's so easy to read or watch something and fool yourself into thinking that you know the topic.

For example, coming up with your examples helps a lot. For instance, I found most of the examples quite underwhelming and confusing so I ended up creating my own asynchronous functions to demonstrate the concepts as I go along.

I've your blog bookmarked and I'll be reading it this weekend haha. Thanks for putting it together!

>Callbacks are not asynchronous by nature, but can be used for asynchronous purposes.

Glad you mention this because some people make it since like callbacks are a de-facto asynchronous-based concept. Callbacks are simply anonymous functions or lambdas that you pass to asynchronous functions so you can work with the produced values. Correct me if I'm wrong though.

Wow small world! Thanks to you for taking the time to explore this topic and putting such a great presentation together. I'd wager it's a must-watch for anyone who keeps asking "what the heck is the event loop anyway?" haha

If you liked Stephen King's "On Writing", give William Zinsser's "On Writing Well" a read. It's not a memoir but more like a manual addressing different types of writing from corporate writing to sports to academic.

Wow this is well hidden. Thanks for the tip!

I'd argue that you cannot understand asynchronous programming in JS without knowing how the call stack in the JS engine, web APIs (provided by the browser or NodeJS as far as I know), the callback/(macro)task queue, microtask queue, and the event loop all fit together. The JS engine is a small component of that entire environment, and not being aware of it is like walking in the dark with dim candle.

The fact I didn't know about these concepts is the reason why I always struggled to understand examples involving setTimeout, setInterval, etc.

Most videos on YouTube, even from well-known personalities in the programming YouTube community, simply jump into things without context at all even when the videos are titled "for beginners". Even some books and docs simply describe the spec without providing context and motivation.

Edit... Forgot to say Philip does an outstanding job in that video. He's even humble enough to admit it took him a few months to grasp what was going on.

Nope. I don't watch the World Cup regardless.

Unintentional boycott?

>C is all about minimalism and simplicity. I think there is a niche for a C like language with memory safety that retains the simplicity of C.

Isn't that the aim of Carbon, the Google-backed language whose specification was announced a few months ago? I might be wrong.

I don't understand why you're being downvoted. Even though it might not the case with all tech companies, there's the possibility there might be significant bloat with some of them.

I hope he also turns off the one that takes half the screen on mobile and asks me to sign in with a Google account. So annoying.

I've read the book partially (which reminds me I need to pick it up and finish it) and it's amazing yet frightening to realize how naive I am when it comes to economics. I like his arguments about how politicians use people's naivety and ignorance to peddle policies that aren't possible if we're to believe that economics is about "scarce resources with alternative uses".

In my book, Sowell is a national treasure.

I've been struggling with wrapping my head around asynchronous programming with callbacks, promises and async/await in JS, however I think it's finally clicking after watching these YouTube videos and creating a document where I explain these concepts as if I'm teaching them to someone else:

* Philip Roberts's What the heck is the event loop anyway? - https://www.youtube.com/watch?v=8aGhZQkoFbQ

* The Story of Asynchronous JavaScript - https://www.youtube.com/watch?v=rivBfgaEyWQ

* JavaScript Callbacks, Promises, and Async / Await Explained - https://www.youtube.com/watch?v=JRNToFh3hxU

* Async Javascript Tutorial For Beginners (Callbacks, Promises, Async Await). - https://www.youtube.com/watch?v=_8gHHBlbziw

* Jake Archibald: In The Loop - setTimeout, micro tasks, requestAnimationFrame, requestIdleCallback, - https://www.youtube.com/watch?v=cCOL7MC4Pl0

Edit... I've been rewatching these videos, reading the MDN docs, the Eloquent JavaScript book, javascript.info, blogs about the subject, etc. This further proves you shouldn't limit yourself to a single resource, and instead fill up the laguna with water from different sources if you will.

>work on your core product instead of this autofellatio

The autofellatio is more likely less work than doing real work. Mozilla's goals nowadays are about tangential matters and publishing feel-good blogs every so often.

Educational material: Despite all the educational material available online (e.g., YouTube), channels with good educational material in the area of software engineering are far and between.