I'm having a fun time expanding my knowledge about vite, react, and building a webpage for my business where I'm trying to make it on Etsy selling laminated recipe cards.
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.
I solved this in a repository I made a few years back. By switching languages, .missing.json files are generated with the words that don't have the other-language equivalent. Then, you run this script which calls the google translate API to generate the translations. https://github.com/reZach/secure-electron-template/blob/mast...
Granted, it still suffers that it's not a human translator, but it doesn't require a LLM.
FYI, navigating to the jobs page currently shows is unavailable: The website that you're trying to reach is having technical difficulties and is currently unavailable.
Neat idea. I had this page saved because I wanted to try it later.
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.
Yes! And if you have problems with anxiety, it may be helpful to simulate your vagus nerve to help calm your body down. Taking cold showers, massaging your ear, eating probiotics are all things that I've personally been doing and I feel a general improvement of my own anxious feelings. It's such an easy/accessible way to manage anxiety; I would think it should be more mainstream.
At the start of my current job, I too felt I didn't understand enough and certainly did not know what the big picture was at work. I credit two things that have helped me see the big picture at my job:
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.
> 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.
I need to staple this (or maybe the whole answer) to my wall and read it many times a day. Thanks :)
I have come to the conclusion that you accidentally described all the reasons why, and how you actually never did see the big picture and how to busy oneself enough to stop looking for one.
> #6 - Security "Tauri is very secure by default, on the other hand I can't say the same about Electron... With Electron you have full access to Node APIs, so a hacker could easily exploit the very powerful Node APIs."
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].
It's _possible_ to build a secure Electron app, but it's also very easy to build an insecure Electron app. Even if you follow best practices regarding context isolation, it's very easy to introduce a subtle security issue like
If you're loading first-party content into the view, then it's no less secure than running, e.g. a Node.js script (or Python, Ruby, C++ program, Rust program, etc.) as the current user. A program you downloaded being able to do things it's supposed to do is generally a feature, not a bug.
If you are loading third-party content, then sure, it's a completely different ball game.
