81 karma · joined June 9, 2017
There are methods of examining and translating our physiological visual experience into an abstraction we call a "drawing" that were developed over hundreds of years. They are very good methods. Don't be intimidated by their age or some imagined importance of an old approach. Anyone can learn to draw given the correct system of reasoning and evaluation.
All that said, don't waste time on anything you do not think is beautiful or inspiring.
Finally, nude figure classes are a great challenge and motivator.
The UX of 'damn I have to look that one weird query up again' to look up some metadata is not as good as it could be.
Raise your hand if you've committed the PostgreSQL to memory for looking at the DDL for a table, or identifying slow queries. Too many database management operations require highly specialized knowledge about a given database's internals.
Folks are far too willing to spend huge money on expensive licenses for db analytics tools to tell them when queries are slow or suboptimal.
Love the idea of making the db responsible for migrations. Downside there could be that db lock-in becomes a concern, and it might add cognitive overhead connecting application code to the current schema. How do you know if app code is up to date with the db without a live connection to prod?
Any mid-life career change carries risk, so I recommend speaking with your family and/or loved ones to make your intent clear. I also saved money for a while before joining a bootcamp to take pressure off of my wife during the training and to ease the job search after finishing.
Most important tip: talk to people. Ask software engineers about their work, lives, interests, practices. Whether you take some formal schooling or not, learning about how people work and why they make decisions will help you move forward more quickly. Without that context it's easy to get lost in a sea of details.
If that doesn't help, move on. Life is short and bad practices will be a drain on your energy and your long term career trajectory.
I think the biggest problems had to do with migrations and backups. We maintained multiple distinct versions of the application, and each had a unique DB schema, so there was frequent drift in the actual schemas across accounts. This was painful both from a maintenance POV, and for doing things like change data capture or ETLs into the data warehouse for data science/analysis.
Another big problem was dealing with backup/restore situations.
I suspect this decision was made early in the company's history because it was easier than figuring out how to scale an application originally designed to be an on-prem solution to become something that could be sold as a SaaS product.
Anyway, I think choosing a solution that nets your business fewer, larger database nodes will probably avoid a lot of maintenance hurdles. If you can think ahead and design your application to support things like feature flags to allow customers to gradually opt in to new versions without breaking backwards compatibility in your codebase, I think this is probably the better choice, but consider the safety and security requirements in your product, because there may be reasons you still want to isolate each tenant's data in its own logical database.
If the appeal is about free usage under 40k monthly active users, you probably don't need an external complex managed auth solution in the first place.
Does it look like an unmaintanable untestable mess?
I started off in a 2x/week one-on-one coaching relationship, and after a few weeks (basically once I had some basic understanding of the main powerlifting exercises) I started attending small group classes 3x/week.
Take your time, focus on form, and work with a knowledgeable coach. You might look for gyms that feature classes in powerlifting or olympic weightlifting.
https://www.barbellmedicine.com/ might be a good resource to check out if you don't have coaches in your immediate area, and you want to have expert guidance.
I found that strength training has radically changed my life, and I've certainly plumbed the depths of profound depression and anxiety in my own life. So far, nothing has come close to helping me as much as strength training. Working out regularly gives me a way to care for myself, and I can walk around knowing that I'm doing work that will have a lasting benefit for all aspects of my life. It's a lot less about looking perfect or weighing some ideal amount and more about caring for myself, and celebrating those small victories in the gym as evidence of personal resilience and growth.
Excersize may not be the magic bullet for your situation, but the same experience of caring for yourself might come from other experiences, like volunteer work, studying a new skill or hobby, etc.
By the way, I've certainly let mediocre therapy go too long. Nothing wrong with exploring other therapists, it's a deeply personal search, and needs also change over time. Trust your instincts on whether you are receiving the right care for you. The worst that can happen is that you try someone else and realize you prefer your former therapist.
You are worth it! Best of luck.
My employer is also allergic to open source, even though we are a huge publicly traded software company, so we're reinventing wheels for things that are already solved problems.
Toxic hell, I should be gone in weeks.
Seems pretty disturbing that so many engineers are piling on to recommend abandoning adherence to some really basic (and easy to understand and apply) ideas about design. Glad I don't work with you! :-P
Chances are, the code is a mess because nobody who knew better was empowered or motivated to advocate for a better way, but you have a hidden opportunity to be that hero.
Good luck!