if the app is properly tested memory issues won’t happen
yeah, no, not really
https://security.googleblog.com/2024/09/eliminating-memory-safety-vulnerabilities-Android.html
the percentage of memory safety vulnerabilities in Android dropped from 76% to 24% over 6 years as development shifted to memory safe languages
Read/Inspect and contribute to FOSS. They'll be bigger and longer lived than small, personal, and experimental projects.
Study computer science.
Work, preferably in an environment with mentors, and long-/continuously-maintained projects.
Look at alternative approaches and ecosystems. Like .NET (very good docs and guidance), a functional programming language, Rust, or Web.
That being said, you ask about "should", but I think if it's useful for personal utilities that's good enough as well. Depends on your interest, goals, wants, and where you want to go in the future.
For me, managing my clan servers and website, reading online, and contributing to FOSS were my biggest contributors to learning and expertise.
They were prevalent. Then they started with adware. Then they bundled adware without developer consent.
Eventually they were bought with a goal of deshittyfication. So theyre fine and have good offerings, but the UI and UX is much worse than other platforms (never improved).
https://en.wikipedia.org/wiki/SourceForge#Adware_controversy
In highlighting the need to understand the requirements before development begins, the research charts a path between Agile purists and Waterfall advocates. ®
Random trademark symbol. What's the registered trademark here? The dot? "advocates"?
It's not POSIX either, but I'll answer your closing question: My current shell of preference is Nushell.
I would have expected that at least all the frameworks were using the same database, but no. Some frameworks use MySQL, others use PostgreSQL. Some framework implementations are ultra-optimized and others are what you would expect in your average web application. Some frameworks are using proper templating libraries, others are using Sprintf.
While it doesn't provide an SQL interface, I've been using Nushell as my shell, which has native data operations.
I tried querying the same, and I'm still not fluent (this was my third or fourth bigger/practical data querying), but it works well and fast too when you know the syntax:
http get https://api.github.com/orgs/golang/repos | each {|x| get license} | get key | group-by --to-table | update items {|x| $x.items | length }
I've used Nushell for reading en-mass json files, generating command json files for stuff saved in excel files (you can natively open those too), and most recently to query log files for specific information and usage analysis.
you can completely understand how the page will look just by reading the html
You lose being able to read meaning and structure though, and you also lose technical accessibility.
I like to add css hacks to websites. But I can't if they don't have useful, identifying, and stable selectors.
Static typically refers to static pages. Which can have dynamic elements, but no backend.
IE: you can’t have a contact form without paying a 3rd party.
Unless you open an email client or other url to forward the contracting I don't consider that (purely) static anymore.
Given that, I'm not sure what you even want "static gen" for? You may be looking for the wrong thing.
OCI does the platform hosting and development. OCF does the non-profit org work. OCF pays the OCI.
At least that's what I read from it.
I wouldn't be surprised if only weeks from now involved people announced a competing/new platform without this setup.
From your description, my view is limited, there is no correct solution. Any choice is viable and fine, and any decision you make will be due to the reasons you chose with.
You didn't disclose what the alternative opportunity and field is, and also not your view on the field and you in it. So it's difficult to assess and put into relation.
You didn't disclose what you did before work, but two years is not that much experience for an engineer. Especially if it is not a particularly nourishing environment. You gain such expertise through experience and exposure over time. Depending on the project and environment it's also not enough to fully understand and intuitively know a big project.
At my workplace we separate role from [personal] development level. As a developer one's role may be developer or lead developer. The development stages are Trainee, Junior, Professional, Senior. If you can work on tasks mostly self-reliant (asking and collaborating is still open of course; knowing when to ask is a skill too) and can put tasks and work into context, you are a Professional. A Senior can support and guide the team. It is perfectly fine to settle for Professional.
Not being exceptional is not a good reason to quit. If you work and bring value, that's still value. Don't decide whether you are valuable or good enough for others. (This leaves out the question of what it means for yourself of course. Tackle those questions individually.)
You say you get your work done. Continuing to do that at a Professional Developer rather than Senior level is fine. You still bring value.
I want to know if that’s what it sounds like to people who’ve seen that before. If you were in my position, would you walk away and just be a hobbyist programmer or stick it out and hope to be a mediocre engineer one day?
I really can't answer that specifically.
You said your team environment is not the best. I assume you don't do retrospectives or personal feedback. Is feedback something you could ask [of some of] your team members, lead, or seniors? (Take care not to poison your question for open feedback with your negative assumptions of yourself and your work.)
Where would you like to be? Separating what you think is expected of you from your expectation and view of yourself and from what you enjoyed and where you think you would feel comfortable settling, how would you lay those out?
Have you considered switching project or employer? You have only seen and experienced that place. A different work environment could be very different - even in the same field.
A strength of the GPL is that the community can fork projects, and "take them over" that way.
At the same time, and this instance is such a case, on a centralized platform, projects can be taken over instead of be forked.
They developed and published a plugin. Now it's been taken over by someone else, on the primary distribution and discovery platform, and they have no control over it. Worse than that, the takeover now offers their sold functionalities for free.
This makes the "open source but not free, but after two years true FOSS licensed" licenses look very useful if not necessary for businesses and developers that want to monetize. At the very least when they [have to] use centralized platforms.