382 karma · joined October 11, 2012
Every day she works till late at nights or awake 5am to continue working. She now thinks that working like that over the pas few months has reduced the chances of her being laid off but she's is completely fed-up and I think she's risking having a burnout.
Seeing this reminds of the time I was spending to understand these concept and use them. Quite funny that the whole React ecosystem is turning into a classic server rendered mechanism with core functionalities being deprecated. I'm glad I stayed away.
How did I get out? I knew for sure that if this ends, then everything turns for the better. So started to to think about the life after the thesis.
First went to the uni counsellor and sought therapy/help. Requested a refund due to mental health issues (luckily one year granted).
I knew I needed one final leg of work to be done to finish. Tried to write a few words every day and possibly created the worst draft of a thesis. Sent it to the supervisor and convinced them to set a date for the defence. The date was two days before my visa expired.
Did a terrible defence which they reluctantly agreed to give me the accepting grade. Tried to finalise the graduation stuff that day to make it to visa appointment the next day. Missed that so had to postpone but eventually turned out fine.
Directly went to a company I used to work part-time and asked them to hire me full-time. Requested a month of salary in advance to be able to pay the rent.
Started working immediately and paying off my debt. Life started to get better. Moved out of that town after a year and didn't step on the campus for the next 7 years.
Not sure if there's much for you in this story. But the only thing that kept me going was the certainty I had that once this thesis is over, my life will change for the better. Crawl your way out of it whatever it takes. Quitting was not an option for me (legal/visa reasons). I understand you might not want to quit a PhD as well. So just try to finish it with bare minimum quality. Don't shoot for the stars and if you're high on some achievement one day don't let that change the goal of only finishing it.
Wishing you the best and rest assured, better days come after this.
ok I made it up.
Focused on simplicity. More info below.
Tech: Fullstack Python, Django, FastAPI, Cloud hosting.
Hi, I have 15 years of dev experience and I used to run a software agency and I have extensive experience in building custom software mainly in Fintech but also in other domains.
I can build end-to-end product MVPs using Python, Django and TailwindUI. Classic web. No React, No FE framework. Very little Javascript but effective server rendered apps.
I mainly focus on the business case and try to write as little code as possible and keep the stack as simple as possible. The goal is to reduce maintenance costs and technical debt.
You can read my philosophy to FE dev here (the tech I use is a bit different now): https://world.hey.com/nasir/the-modest-frontend-c21aceef
Email nasir[at]semicolon[dot]io for more info and CV.
I told him this really does not mean anything. You need to have concrete steps toward this goal which is only 3 years away.
I think those who really wants to achieve the so-called "success" will just go figure it out rather than constantly reading those success story. Yeah perhaps at the very beginning of the journey you get inspired by reading a few of those.
But the rest is basically taking concrete steps and trying stuff out until it sticks. And the best way to do that is to go figure out HOW those people in the success story did it.
At least at the end he was happy with the answer.
And once you come to that realisation, you can start living off some of those savings just to chill out and not be "productive". While in reality that's probably what you need.
Worst case scenario for the OP is probably finding another gig in a few weeks.
Once you're not in this race, you will probably engage yourself with other things and you will start developing a clarity in thinking about this whole feeling.
But this is definitely something you need to implore otherwise it can negatively impact your mental and physical health.
The main point is: * I do want to use React components for composability. * I don't want to deal with global state management.
Remix seems to address those issues for me so I'm planning to give it a try.
Remix seems to use an approach similar to Hotwire Turbo Frames and a syntax of React JSX. This allows creating composable pages and loading partials in a page while still being able to create React components.
The main use case for me is web3 where almost all libraries are in Javascript. And I want to have the least friction for this move. It basically encapsulates the server and client side of an HTTP request in a single component and handles the json parsing operations under the hood.
You can argue that it might not necessary and a template engine can come much handier. I believe NestJS handles that but if you need the React JSX and reusable components it can be quite practical.
Fast-forward today, most of the people I know who were in electronic have switched to software.
No website yet but you can follow me on twitter.com/n4cr if you're interested for the release.
Another project is https://speqt.co where it helps you automate fetching digital invoices from your SaaS providers.