792 karma · joined November 22, 2018
Level up your skills by reading my blog: https://www.debugandrelease.com
(contact) https://www.debugandrelease.com/contact/
I love to cook and this is such a fun combination of using my skills with web technologies and food in such a happy marriage.
I'm building a recipe editor online, one where you could enter in the details, and then get a printable file [to become an index card, for example]. I just started so I still have some ways to go but progress is good so far.
Granted, it still suffers that it's not a human translator, but it doesn't require a LLM.
If it wasn't for this thread I probably wouldn't have gotten past step 3. However, I have no clue how to move past step 4. I get the HINT we need to make a request, but I can't figure it out based on the instruction on the page. The page I tried is a 404. I'm not sure what <code> blocks are trying to convey, it's not clear to me. It would be fun to try to get to step 20, but if the clues get more vague at each step, there's no way I'll make it to the end.
1) Relentlessly pursuing all that I could to learn 2) Having a come-to-terms moment that yes it was okay to not know and not feel bad for asking questions
Work is different than school. In work, it is more important to be self-motivated. What this tangibly means is that if I'm working on something that I have questions about, I go to the person who has the answer to my question to ask them. I'll do this many times throughout my day if I don't already know the answer. If you are feeling afraid to feel "dumb", I don't know exactly how to force it, but you need to have a moment where you accept the fact you will not know things and will have to ask questions to get the answers you need. It becomes easy to ask questions once this moment happens.
Also, be the one who initiates change. Don't wait for your manager to tell you what to do [once you have a good idea of your tasks]; be self-motivated and say yes to everything and dive into everything and learn as much as you can. The more you do this, the more you are exposed to, involved in, and talk with others and can pick up enough "background noise" to understand more of the big picture [without explictly asking what the big picture is]. I would say after about 2-3 years you get a good intuitive understanding of your job and role, but I assume that runway depends on various factors that vary by individual.
It's fair to believe this, given there's so much material out on the web affirming the fact. I've written about this at length in other places; applications with Electron pre version 5 [0] (released April 2019) were not secure. It's entirely possible and easy to build a secure Electron app today. I started building a secure app Electron template in 2020 [1] (that I still maintain) to address this security issue. I've also written about a history of the framework [2] and steps to build your own Electron app with today's best practices [3].
[0] - https://github.com/electron/electron/releases/tag/v5.0.0 [1] - https://github.com/reZach/secure-electron-template [2] - https://www.debugandrelease.com/the-ultimate-electron-guide/ [3] - https://www.debugandrelease.com/creating-a-simple-electron-a...
So true, this resonated deeply with me. Being busy is also a safe/acceptable/normal response that can hide or shield us from fear. Am I too nervous or self conscious or fear rejection? I have no need to fear any of that if I'm never around anyone else, and it's perfectly acceptable to be "busy" and reject social gatherings because being productive == good.
I noticed this underlying fear in someone else and I tried my best to help them and to accept the person they were, but they remained closed off. Someone will only make the change when they are ready to do so and you can't force it even if it's of good intentions.
- An Electron template with built-in secure features. I regularly maintain and update the template so it's supported with newer versions of packages. - A collection of free, public-domain recipes. I've wanted to do some version of this for _years_, but am finally getting around to do it again. This time, I'm paying chefs to create recipes for me that will be licensed as public domain.
[0] - https://github.com/reZach/secure-electron-template [1] - https://github.com/reZach/open-recipe-project
-Is the time spent writing worth to me? Yes - I find it's helpful to jot information down so that I can refer to it later. It's a bonus point to get known within a topic or when others come and say that my material is helpful
-Did it help me find opportunities? I've been approached once for an opportunity to work based on my work online
-Did I learn something new from it? Yes. Writing down my work is a great way for me to learn as it tells me if I have holes in my knowledge when I go to explain my thoughts.
I write mostly about Electron [with Ghost]: https://www.debugandrelease.com/https://www.debugandrelease.com/how-i-gained-1k-stars-on-my-...
Tauri (https://github.com/tauri-apps/tauri) uses less memory, but relies on a different browser so your app may be inconsistent cross-platform.