motherfucker windows10

Java: String foo =“bar”;
C#: var foo = “bar”;
Go: var foo string = “bar”

I just started learning Go and I’ve been cringing since.

Sometimes I leave comments to myself at the end of the work week to remember on monday where I left off
Anyone else does this? 🤔

!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!

Just gonna leave this here.

Don't complain if you refuse to speak up. You don't like how something is going? But you don't want to do something about it? Then shut. The. Fuck. Up.

Getting sick of these fucking coworkers who bitch and whine about everything they don't like but when given the opportunity to speak up and voice their shit they just fucking clam up.

Context: nobody was saying anything during today's retrospective but were talking shit about the project the whole sprint. Gee I wonder why NOTHING FUCKING CHANGES. I'm the only one outside of our product owner and tech lead who even speaks out on problems/issues during the sprint. This dev team I'm on is just.. urgh.

They expect me to have their back, but they don't have mine. For months I've been carrying them. Fine. Enough is enough. The next time they need help from me they'll just get the obligatory "have you googled it because I don't have an answer" response.

While scraping web sources to build datasets, has legality been ever a concern?

Is it a standard practice for checking whether a site prohibits scraping?

Workplace starts using slack (or other chat app);

Now you can use channels: now your inbox has inboxes and you don't know where to look.

Now channels support threads: now your inboxes have inboxes have inboxes.

1,000 books on productivity and research show how important deep work is and time boxing your email:
Now your inboxes that have inboxes thst have expect your attention every moment of the day.. And I still don't know where to look.

By constantly fucking around with things that interest me. If a topic fascinates me i will either lool for shit around youtube, read proper documentacion or buy specialized books for it.

Most recently it has been compiler design. I wanna write my own language, for testing and learning more than anything.

I dunno, it keeps shit fun and interesting. Now, much of that shit ain't applied to what I do in web. But it does help to keep the mind fresh as well as giving me the chance to eventually invent my own language. Write a large system with it, use it at the institution and have them pay me obscene ammounts of money to maintain it.

It will be like VB6 or VbScript, but with {}s, immutable values by default and no looping, cuz I am evil AF

Consistently evaluating myself. Assessing where and what I lack and writing goals to work on. Not being comfortable for so long. Doing interviews help in the skill assessment.