i am taking some pills for hemorrhoids and yesterday i was combined them with my third coffee. Somehow i was full of energy and i started coding like f crazy. I was literally writing code withe the speed and tension you see in movies, or if you like it, like our non tech bosses are thinking we work 8 hours a day for granted. I did not know what was happening, i was typing correctly, fast, and i want to live it again. Dope, adrenaline, aggression!
The code must fear us, not we the code!

I have couple dev ambitions some of them are:
- to become better in what I am doing and get a higher position.
- to build my own product.
- to educate young programmers.

a very polite recruiter in linkedin after our connection asked me why i choose this kind of career. I answered this and i hope i did not ranted a lot :)

i was trying to figure out what profession would make me more happy than others. I was always felt comfortable with computers, i was installing cracked games, exploring folders to paste the cracks etc. later in school when i learned the first algorithms like bubblesort i was knowing that i liked it. I also like working in silence while searching for solutions. That is the first part, the second is that i made a search about what industries would give me a safer future and international opportunities without having to be stuck in my country only. By working and getting more experience i felt in love with my job and trying to learn everything i missed and give to my boss or customers professional results with quality. I like it as a lifestyle, it combines a magic feeling of spells with the logical procedures of science. So why not? it combines all my loves together: creative thinking, technology, mental work, internet, music at the workflow, job demand, opportunities, and money! I hope i helped you my friend i am at your service for every question you have :)

Dear wordpress developers,
You have my sincerest apologies. I used to think developing with wordpress is what people do when they are feeling lazy and dont want to work with code and frameworks. But no... wordpress,shopify and all those shitty ready CMSs are by far the worst methods of developing websites or web applications. I have spent countless hours in my new job in the past two months simply trying to resolve issues caused by wordpress websites suddenly deciding to stop working after one of the billion plugins required to do the simplest of tasks was updated. The money i need to spend on premium plugins alone makes developing the website no longer profitable in the first place. And god forbid the client asks for a very simple frontend edit that the theme doesnt offer in the theme options menu. Even tho doing the feature from scratch would take next to no time at all if you do it yourself... you end up trying out a hundred plugins just to achieve something in a ways that feels very forced. Nothing will ever top cakephp for me

Push people to review my PRs to merge before a teammate so I don't have to rebase my branch

"Please disable AdBlock to view the content."

No. I'll just leave. Bye.

!rant

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.

5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.

6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.

7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.

8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.

9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)

10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...

These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!

Good idea though

I made the mistake my first year as a programmer to start sim racing. It was a disaster. I was continuing staring at a screen. The next step was buing woods and knifes for woodcarving. Still a disaster. It was demanding the same concentrations in very small pieces for my eyes, just like code. Now, i learned. I get a motorcycle and i hope riding soon. I believe it is the ultimate anti-stress activity. Nothing to do with high speeds, just the feeling of riding, and doing something not mentally