AboutEx-computer science student at Leibniz Uni Hannover. Music enthusiasts (deadmau5, Madeon, Porter Robinson, etc) and hobby producer. I love sci-fi like Stargate, Dr.Who, Steins;Gate, Rick and Morty. LEDs make everything better.
Joined devRant on 8/17/2017
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
At first I wasn't crazy about it,. but I think I'm hooked now. I am a big fan of fira mono. I switched my xterm to use it, and it's really distinct and helpful. I highly recommend giving it a try.
devCredits - a simple way to make a credits page for your devrant community project [more details]40
25 phrases you wish you could say at work more often
(Warning: Contains naughty words...:-)))
1. Ahhh...I see the fuck-up fairy has visited us again...
2. I don't know what your problem is, but I'll bet it's hard to pronounce.
3. How about never? Is never good for you?
4. I see you've set aside this special time to humiliate yourself in public.
5. I'm really easy to get along with once you people learn to worship me.
6. I'll try being nicer if you'll try being smarter.
7. I'm out of my mind, but feel free to leave a message...
8. I don't work here. I'm a consultant.
9. It sounds like English, but I can't understand a word you're saying.
10. I can see your point, but I still think you're full of shit.
11. I like you. You remind me of me when I was young and stupid.
12. You are validating my inherent mistrust of strangers.
13. I have plenty of talent and vision. I just don't give a damn.
14. I'm already visualizing the duct tape over your mouth.
15. I will always cherish the initial misconceptions I had about you.
16. Thank you. We're all refreshed and challenged by your unique point of view.
17. The fact that no one understands you doesn't mean you're an artist.
18. Any connection between your reality and mine is purely coincidental.
19. What am I? Flypaper for freaks!?
20. I'm not being rude. You're just insignificant.
21. It's a thankless job, but I've got a lot of Karma to burn off.
22. Yes, I am an agent of Satan, but my duties are largely ceremonial.
23. No, my powers can only be used for good.
24. You sound reasonable... Time to up the medication.
25. Who me? I just wander from room to room18
@JoshBent and @nikola1402 requested a tutorial for installing i3wm in a windows subsystem for linux. Here it is. I have to say though, I'm no expert in windows nor linux, and all I'm going to put here is the result of duckduck searches, reddit and documentation. As you will see, it isn't very difficult.
First things first: Install WSL. It's easy and there's a ton of good tutorials on this. I think I used this one: https://msdn.microsoft.com/en-us/...
Once you got it installed, I guess it would be better to run "sudo apt-get update" to make sure we don't encounter many problems.
Install a windows X server: X is what handles the graphical interface in linux, and it works with the client/server paradigm. So what we'll do with this is provide the linux client we want to use (in this case i3wm) with an X server for it on windows. I guess any X server will do the work, but I highly recommend vcXsrv. You can download it here:
for i3 just "sudo apt-get install i3"
Configurations to make stuff work:
open your ~/.bashrc file ("nano ~/.bashrc" vim is cool too). You'll have to add the following lines to the end of it:
export DISPLAY=:0.0 #This display variable points to the windows X server for our linux clients to use it.
export XDG_RUNTIME_DIR=$HOME/xdg #This is a temporary directory X will use
sudo mkdir /var/run/dbus #part of the dbus fix
sudo dbus-daemon --config-file=/usr/share/dbus-1/system.conf #part of the dbus fix
Ok so after this we'll have a functional x client/server configuration. You'll just have to install your desktop enviroment of choice. I only installed i3wm, but I've seen unity and xfce working on the WSL too. There are still some files that X will miss though.
*** Here we'll add some files X would miss and :
With "nano ~/.xinitrc" edit the xinitrc to your liking. I only added this:
Then run "sudo chmod +x ~/.xinitrc" to make it an excecutable.
Then, to make a linking file named xsession, run:
"ln -s ~/.xinitrc ~/.xsession"
Now you'll be able to run whatever you put in ~/.xinirc with:
"dbus-launch --exit-with-session ~/.xsession"
There's a ton of personalisation to be done, but that would be a whole new tutorial. I'll just share a github repo with my dotfiles so you can see them here:
SHIT I ALMOST FORGOT:
Everytime you open any graphical interface you'll need to have the x server running. With vcXsrv, you can use X launch. Choose the options with no othe programs running on the X server. I recommend using "one window without title bar".10
Today at work, still laugh thinking back to it!
We were on lunch break but the linux support engineers who are on the phones as well have to pick up calls anyways (very small team).
*engineer walks to the table, sits down: Ahhh rest, finally!*
*engineer pulls a face like 'oh for fucks sake' and walks back to his desk*
*puts headphones on and clicks the answer button just as it disappears*
"really!?! Alright lets finally eat now"
*sits for literally one second*
*Engineer seems quite pissed off now. walks to his desk again, puts on headset, clicks the answer button JUST as the call stops again*
"Mother of god, fucking really?"
*stays as his desk for a minute or so, walks back, stays hovering above his chair for a little and finally sits down again*
"MOTHERFUCKER. THESE GUYS TIME IT OR SOMETHING!?!?"
*walks back to his desk very frustrated this time*
*puts on headphones very quickly and presses the answer button*
*answer works but the call is literally dropped the second he starts it (it was a real client)*
"OH FOR FUCKS FUCKING FUCKING FUCKING SAKE FUUUUUUUUUUUUUUUUUUUUUUCK"
*walks back to table again and sits down. Takes sandwich and....*
"FUCKING COCKSUKING MOTHERFUCKING PIECES OF WHAT THE FUCKING FUCK EVER"
*gives a deadly look to another engineer: "I am NOT going to take it this time! En-fucking-joy."*
We laughed so hard xD16
De-google your life
-duck duck go look up the founder
-yandex (putin botnet)
-https://kek.gg/i/3g2z6d.png (superior list)
-https://kek.gg/i/67YQQx.jpg (for furfags)
-ether pad (eg: notes.typo3.org or etherpad.net)
-microsoft office online (lol)
-gnu social (for freedom loving patriots)
-mastodon (for proprietary loving gook pedos and sjws)
Google CDN avoidance
Ad and script blocking
Share links without gibbing clicks
How to hosts file (lol, just block google bro):
If Programming Languages Were Girls:
Java: Your current girlfriend, you've been going steady for a while now. Things are okay.
Kotlin: The girl Java finds you cheating on, she's just amazing, and you wish you'd met her sooner.
Visual Basic: The girl you accidentally started a relationship with because you didn't know how to say no. But quickly realised your mistake and regretted it.
Python: A bossy, manipulative girl who quickly turned things sour. But everyone else loves her because of her huge libraries.
My and a co worker were joking the other day about what programming languages would be like if they were girls. This is what we came up with (Original inspiration: the Distracted Boyfriend meme (Feel free to add your own!)).51
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!205