https://github.com/byanko55/ptsd
https://github.com/byanko55/ptsd
Last synced: 8 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/byanko55/ptsd
- Owner: byanko55
- Created: 2024-04-26T02:35:29.000Z (over 1 year ago)
- Default Branch: master
- Last Pushed: 2024-06-19T08:38:43.000Z (over 1 year ago)
- Last Synced: 2025-01-14T20:22:31.627Z (9 months ago)
- Language: Python
- Size: 35.2 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# PTSD ('P'ytorch 'T'riggers 'S'omeone's 'D'epression)
A repository that makes its owner crazy and powerless like living with '***post-traumatic stress disorder(PTSD)***', 😥 😥
## Where does happiness come from? Find true happiness
> **"Happiness occurs when we contribute our actions and lives to what we find ``meaningful``."**
Human beings want to find purpose and meaning in their lives. What is more realistic is that our purpose and what we find meaningful may not remain static all our lives. They’ll grow and evolve as we do.
Here are the things that you can do here:
1. **Know what you want to be**
2. **Don’t compare yourself to others**
3. **Choose goals according to your values in life and not others’ expectations**
4. Boosts yout self-confidence
5. Respect yourself and set boundaries with people when they cross them
We often struggle to put these wisdom into practice. Doing more of what you love will help bring more joy into your life.
Unfortunately, there will always be things we don’t enjoy doing but have to do. The trick is to limit these activities, and if we cannot do so, to take some major steps to change your situation may be necessary.
Of course, these changes can be scary, but sometimes they are necessary to find true happiness. **Don’t be afraid to make changes in your life if you feel they are necessary for your happiness.**
## Skills of a 'Peaceful'(~~Successful~~) Software Engineer
### 1. Your code doesn't need to be perfect
As a new engineer, you won't be expected to write elegant and beautiful code from the get-go. That's something that will take years of practice to master.
So don't worry too much about being perfect.
### 2. Writing Readable Code Is Essential
We, software engineers, spend much more time reading code than writing it.
A new software engineer must write code for humans, not machines. Get into the mindset of writing code humans can read because even though programming means giving instructions to computers, your present and future colleagues will interact with the code. Make it easy for your colleagues to read your code.
Follow your company's coding standards, indent your code, and give meaningful names to variables, methods, fields, classes and tests (yes, even tests need to be named appropriately).
### 3. Get Your Code to Work
When you're assigned a task, focus on writing working code.
You can think about the initial version of your code as a prototype.
You can (and you probably will) refactor and optimize your code later.
### 4. Try Not Over-Engineer
There is this ongoing saying that in software engineering, simple is best. For the majority of the time, I agree with this.
Over-engineering means creating complex solutions to simple problems. A great strategy to avoid over-engineering is to take a step back, think objectively about what you're doing and look at the bigger picture.
### 5. Learn How to Fix Bugs
Everyone hates bugs, but the reality is that we engineers are the ones to introduce them unintentionally.
An approach to deal with bugs is to use a Root Cause Analysis (RCA). When encountering a bug, you need to understand these three things:
1. Why is the bug happening?
2. How to solve the bug.
3. What you can do to prevent the same issue from happening again?
*Related:* [10 Career Advice for New Software Engineers](https://techwithmaddy.com/10-career-advice-for-new-software-engineers)
## Contributing
If you'd like to contribute to this project or fix a bug(~~Hold on, Are you serious~~ **\`Φ ∇ \`Φ?**), please open an issue and make a dicussion with me.
Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue.