I don't know if it would help you to hear this from a stranger, but try to calm down and clear your mind through meditation. Before going to sleep, set clearly achievable goals for the next day. Wake up early, meditate, work out. Obtaining a lucid state of mind is the best thing you can do for yourself right now. If it helps, go somewhere you normally wouldn't go where you can be very in-the-moment for a time, to snap you out of your current environment and allow you to reset.
If you assume the outcome of your thesis is a foregone conclusion, this can enable you to work without hesitation. Many fighting chances have been born during last-minute, no-hope efforts, and if yours doesn't come along, treat that as a bridge to cross when you get there.
I know, easy to say when everything feels like it's doomed. I took a shot at building a MVP for a product to start a company with and failed because I spent over half the time messing around, working on what wasn't important.
Six months in, running out of time and money, I started these habits even though I thought to myself that it would be too late for them to matter. I became very productive especially towards the end as a result, and I could keep to my new routine since I figured "at least I'll be getting something out of the whole ordeal".
At the same time, I felt like the situation was beyond salvaging, and the product indeed never saw the light of day. The silver lining is that the habits I picked up when I set myself straight, both professionally and personally, have been immensely useful in the years that followed.
Give it your best. I hope things work out for you.
I don't think any of the below are too exciting, but the effects they have probably show up in the bottom line:
- I invested a lot of time into speeding up our customer-oriented websites after I noticed we were regularly loading in 4-10 seconds. It wasn't seen as a major priority - however, past a certain load time for each page, you start losing users. We started off way past that certain load time and managed to end up at something between 1 and 3-second loads in most cases.
- This wasn't my idea, but a marketing manager I respect a lot once mentioned that people were spending a huge amount of time filling their date of birth while signing up. Something like 30 seconds or more. The reason was that we had been using a date picker that defaulted to the current year, so people would have to click back i.e. 30 times to select their year of birth. On his request, I replaced it with 3 lined-up fields of selects, and the time spent on average went down to 2 seconds.
- I had the chance to do a major rewrite of some legacy systems that worked fine, but weren't built to scale and lacked standardization - the company had a few hundred users in one country when they were made, and when I worked on it there was a locally-modified copy of the system for each country we were in.
The reason for it was that some of our integrations would cease to work due to third parties, and we had to implement a major upgrade, so I built a service to handle requests and standardized the old servers to only make requests to the service without being smart about how they're processed.
In the process, since everything was liable to break anyway if I didn't get it right, I updated every dependency (whether it was for the code or the server) that I could find. Not fixing what wasn't broken was a value that had served us up to that point, but we were racking on technical debt and it was a good chance to get rid of it. Sure, lots of things -did- break, but solutions were found. Technically, it'll help both me and future devs entering the project, and practically, since the integration chiefly targeted contract processing for our customers, the fact that we can still do contracts and nothing broke on the surface is a success.
- I implemented log aggregation across all our servers (using ELK) and it's been helping us track errors and server states a lot. We could have used something like Sentry, but we have millions of events going through on a regular basis, so it's cost-effective.
- We use an internal time tracker that works based on office card access events. I was always curious about racked up overtime, so I added in a calculation for it in the API and returned it in the response when loading a user's info without adding it to the frontend. I mostly used it for myself and told a few colleagues about where to look if they wanted to check. A few months later, overtime calculation was added into the tracker as a feature.
Predictions are fun! Here's hoping I come back to read this in 2030.
1. There will be a breakthrough in VR gaming. Kits with similar features to today's most expensive will start going on offer for prices lower than or comparable to consoles, and new high-end kits will offer full motion tracking without needing treadmills or the like. VR cafes, similar to the Internet cafes of old, will become a mainstream choice for entertainment, especially for teenagers and young adults. Half-Life: Alyx will be a major contributor in establishing industry conventions that other developers will build upon.
2. Piracy will drastically increase for video content following the fragmentation of streaming services. A subscription to have access to all streaming services will appear, and we'll have completed the loop back to cable television.
3. Electronic voting will be adopted in a few more countries. One will have an election hacked, resulting in a different party being elected than the one people actually voted for. A major scandal following that will halt the trend.
4. Web development will continue to remain highly fragmented. There will be fewer and fewer individuals that understand all the layers of applications due to continually exploding complexity. Containerization will be taught as a core competency in any development course. Firefox will gain 10% of market share, but Chromium-based browsers will remain king. JS will lose market share but will remain at the top.
5. There will be a rising trend in using neural networks to prepare APIs and interfaces for the most common app types, and it's going to be advertised as magic. It will result in a decrease in entry-level freelancing jobs, and a decrease in the revenue of companies based on providing no-code websites - unless they're the ones that offer the service.
6. A new standard for designing apps will appear from one of the tech giants and be adopted into the mainstream after 2 or 3 years, similar to Material.
7. There will be a massive push in many major cities to discourage personal vehicle ownership, proposing the use of public transportation or bikes/electric scooters instead. Part of the push will be in decommissioning lanes, the other in taxes.
8. Gen Z will turn out as a generation of extremes. To the surprise of many, tech illiteracy will be a serious problem.
9. There's going to be a global scare due to a superbug, i.e. a virus that is resistant to antibiotics. It may get as far as having border lockdowns.
10. China will continue its rise to power, and individual freedoms will continue to decrease. On a related note, Hong Kong will be subdued in a subtle manner, and a history rewrite will be attempted.
11. There will be an economic recession within three years. Many companies will feel the effects on their bottom line from decreased sales and will try to automate entry-level positions in response.
12. Mirroring what another poster said in this thread, deepfakes will become so commonplace that only lived experiences will remain fully credible; and yes, there will be an industry based around trying to sell content as being fully unedited.
13. Open offices will finally start fading out, remote work will become more mainstream. Despite experiments in several countries, the 8-hour workday will remain the norm.
14. Again mirroring other posters in this thread, crypto won't have a massive breakout, though it will continue to rise in popularity. Investors will start wincing when they hear about crypto startups, the already established ones will start seeing some mainstream use.
15. And the one I'm most sure about: we'll still be playing videos using VLC in 2030.
During my first job, my boss introduced me to HN. I doubt I would've found it so soon otherwise, as the only other person that knew about it before I mentioned it is someone I only met this year.
My first boss was a great guy to work with and I'm grateful he told me about it. Even though I learned a lot from him professionally, the impact of that one-time five-minute conversation about the site might have added up to more over the years.
I'm thankful that I was lucky enough to be exposed to computers at the very young age of 6. Until I became around 11 or 12 years of age, most people only had routine access to them when working government or highly technical jobs (Eastern Europe in the 2000s), so I am aware it was a very kind gift from my parents.
They actually worried that I spent so much time playing video games afterward, but games taught me English, made me competitive for the first time, gave me a few tips on empathy, and helped me develop a passion for solving problems and understanding systems, which I tried to use to make my own games, which ultimately led me to pursue a career as an engineer (which eventually led me to HN, and eventually to this post. Ha!)
Full-stack developer with around 4 years of experience.
I've worked with several startups in bringing their web products to life from scratch, and have worked on all sides of the problem (sometimes even helping them with market research).
I really enjoy working for companies that put an accent on improving the lives of their customers and afford their team the trust they need to get things done.
Very into optimizing code and usability when I get the chance. I've been the sole developer for a course website since 2016 (mostly pro-bono during my spare time) where I've been using a mixture of Google's services and internal tools to max out speed, and we handle a decent traffic load on the web hosting equivalent of a toaster as a result.
I also maintain a browser extension that counters GDPR/privacy spam, and that's brought on a slew of fun performance problems to tackle as well.
Location: Cluj-Napoca, Romania (GMT+3)
Remote: Yes.
Willing to relocate: No.
Technologies: PHP (Laravel 5.x), Javascript (jQuery, Vue.js, learning React), some DevOps (setting up and securing servers via VPS or AWS, setting up CI/CD /w Docker images + Gitlab/Bitbucket/Your Service of Choice and monitoring), design sketches and implementations (PS -> CSS).
If you assume the outcome of your thesis is a foregone conclusion, this can enable you to work without hesitation. Many fighting chances have been born during last-minute, no-hope efforts, and if yours doesn't come along, treat that as a bridge to cross when you get there.
I know, easy to say when everything feels like it's doomed. I took a shot at building a MVP for a product to start a company with and failed because I spent over half the time messing around, working on what wasn't important.
Six months in, running out of time and money, I started these habits even though I thought to myself that it would be too late for them to matter. I became very productive especially towards the end as a result, and I could keep to my new routine since I figured "at least I'll be getting something out of the whole ordeal".
At the same time, I felt like the situation was beyond salvaging, and the product indeed never saw the light of day. The silver lining is that the habits I picked up when I set myself straight, both professionally and personally, have been immensely useful in the years that followed.
Give it your best. I hope things work out for you.