miccah

This interactive intro to DSP is also great for gaining an intuition.

https://jackschaedler.github.io/circles-sines-signals/index....

Behind every success is countless failures.

I think taking the negative connotation out of "failure" will remove any mental barriers for all creative subjects.

As the post says, someone who has not failed has not learned. I wish school systems were more supportive of this in the classrooms.

I agree, I always feel like tracking every single TODO takes more time and effort than actually doing some of them. It was a bit too rigid for me - that sort of system is designed for a computer, except I was the computer doing the task.

What works for me now is writing my most important TODOs on a whiteboard and not erasing it until I complete it. The limited space forces me to prioritize. It's also obvious which items have been there the longest, either indicating lower priority or mental blockages. It helps that the ink is harder to erase the longer it sits there too :)

> simple tools I can fully build and understand myself

This reminds me of an excerpt from PoC||GTFO.

"[W]hen you’re tooling around with a from-scratch tool and your neighbors tell you to use this or use that, look ’em in the eye and say, “I’m building my own fucking birdfeeder.”" [1]

[1] https://q3k.org/birdfeeder.pdf

This is my preference as well! I even wrote an Android client app / Python server to control it from my phone.

https://github.com/mcastorina/mpv-remote-app

I use Jellyfin as an open source alternative to Plex. I personally don't have any audio books on my home server, but it has support for them.

I also learned Dvorak after many years of vim, and relearning the muscle memory was the most frustrating part. Not much you can do but stick with it though, and eventually it gets easier.

Not DCT, but this website [1] has been on my TODO list for awhile. It explains DFT using interactive visualizations.

[1] https://jackschaedler.github.io/circles-sines-signals/index....

This looks like a really nice and polished app, thanks for releasing it!

Is there an option to only generate the yaml instead of generate and deploy altogether? This would allow me to create a lot of boilerplate while still having the option to fine tune the configurations if needed.

I also didn't see any information on rollbacks.

I agree. I was taught FSMs in my introductory electrical engineering courses but never once in any CS course.

FSMs can work really well for software, but perhaps the complexity of a program would result in a massive number of states. I have also found it is harder to reason about the entire operation of a FSM.

While I agree that you have influence over how you feel about things, I also think it's okay to quit and do something else when you are no longer interested in the subject.

This could mean a temporary break or more drastically, career altering. Many people have the power to shape their life, but they choose to keep going in one direction because of how much time they invested. Even when that direction no longer aligns with them.

> Rust has:

- monadic constructs (Option & Result) - the error propagation operator - the From trait, to automatically convert errors on propagation

> The combination of the three features above makes up the best error handling solution I saw in a language, being simple, sound, and maintainable at the same time.

I absolutely agree with this. The error handling in Rust is fantastic to work with.

Once I learned about bullet three, error handling became less of a chore and more of non-issue while staying confident that any errors would be handled correctly.

Really cool! How do you determine the topics for an article?

I also see some topics on the full list that probably shouldn't be there - a gmail address and a random string of numbers.

Sometimes you need a different type and you don't care about the intermediate values. Parsing a string into an integer is a good example. Once you have the integer, generally you don't care to use the string anymore.

  let num = String::from("10");
  let num: i32 = num.parse().unwrap();

As a beginner to Rust, this blog post has been excellent, and it has really helped me understand the idiomatic way to handle errors.

https://blog.burntsushi.net/rust-error-handling/

Thanks for the tip! If anyone is curious I found the list of commands here: https://github.com/ajaxorg/ace/blob/master/lib/ace/keyboard/...

I appreciate the vi mode editing. `:w` will compile and run the program, but that is the only colon command I have discovered.

> You got your first software development job. The idea of being interviewed made you feel very anxious, but you studied hard and aced the whole thing. Finally, you arrive at the office on your first day and...

> And it's terrifying. Suddenly, you feel like a Jon Snow who knows nothing, and self-doubt starts to creep in.

I was very fortunate in my first position to not have any imposter syndrome, and I think it is partly because I did not ace the interview. I was honest when I didn't know an answer and showed I was willing to learn.

If including code snippets, it would be great to easily export it to an online playground or other sandbox.

Often times I find an example or documentation, and I copy it to a playground to tweak it / experiment with whatever feature I am implementing.

+1 for Matt Estlea. I find his content very watchable, and I like that he explains the theory before showing you how.

I'm investigating the same. The upload endpoint uses secure_filename to get the filename used in that func. I'm not familiar with it, but the docs say it could return an empty string.

One technique that keeps me motivated is thinking from the point of view of the future. I ask myself how much further along will I be if I start now?

This looks really nice, congratulations!

Slack has something similar during video calls where anyone can draw on the screen and the annotation automatically fades after a few seconds. Might be a good addition to your product.

I always read & as "at" mentally when reading code :)

I wrote a very, very simple Makefile awhile back utilizing the arduino CLI options.

https://github.com/mcastorina/laptop-remote/blob/master/Make...

Haven't used it since then, so YMMV.

I use Zim Wiki [1]. I like the hierarchical structure plus the ability to link to any other page internally. It does a good job of staying out of your way and has support for check boxes, searching, and various plugins. It also saves to disk in plaintext so I can version control it.

[1] https://zim-wiki.org/

I have one similar to your "newsh" called "new" which does `mkdir "$1" && cd "$1"`

I also have another one called "store" which does `mkdir "${@: -1}" && mv $@`. I basically wanted an easy way to move everything into a new directory ("store * backup").

I've actually never encountered that issue, but because Zim is a wiki style editor, you could create links to different pages for asides. It's still another page, but at least it can be all grouped together.

I have found Zim to be a great tool for note taking and creating a personal knowledge base. I can create a link to a more detailed explanation from any page if needed, or write down examples separate from theory.

This looks very cool! I noticed some typos on the home page that should be corrected:

> Beeing a small dev team

> suffer less cognetive load

Perhaps an identifier can be used so the user can quickly verify the email matches the page.

It could be something like a sequence of 3 emojis because matching numbers is hard.