Pro Tip: You can drastically reduce keystrokes in any editor by using your brain before typing.

I was activating virtualenv in powershell when my younger brother came in.

Me: *all nervous* please don't think I'm hacking or trying to set off a bomb. (He always thinks I'm hacking and tells on me.)

Brother: *silent*

Me: *even more nervous* I don't want my laptop to get taken away. Don't tell on me and say I'm hacking, because I'm not.

Brother: Oh, I know you're not hacking this time.

Me: You do? *relieved.*

Brother: Yeah, because this time it's a blue background, not a black one.

Me: Oh, haha. So you're only scared of things such as these? *opens CMD and Git Bash* you know, just because it's dark themed, doesn't mean it's malicious. Besides it—

Brother: oooOooOh! You're hacking again! I'm telling on you!

*Note to self: Never use dark theme in front of the ignorant again.)

note to self: do not use super glue on your keyboard

note to self part two: do not listen to the internet and use nail polish remover to get super glue off your keyboard

Oh boy its actually embarassing...

I was in a cosplay event, when I realized I only have 30 minutes till I check in for my first day in the job as a support agent.

I never had the time to change because of traffic and I was commuting so I spent the next 9 hours in side the company premises wearing a japanese schoolgirl uniform.

...I got quite everyone's attention, even the HR... ( well at least the HR just reprimanded me about that >_<)

Note to self: remember to give yourself 30 minutes more of allowance....

I turned 40 yesterday. Here are some lessons I've learned, without fluff or BS.

1) Stop waiting for exceptional things to just happen. They rarely do, and they can't be counted on. Greatness is cultivated; it's a gradual process and it won't come without effort.

2) Jealousy is a monster that destroys everything in it's path. It's absolutely useless, except to remind us there's a better way. We can't always control how we feel, but we can choose how we react to those feelings.

When I was younger, jealousy in relationships always led to shit turning out worse than it probably would have otherwise. Even when it was justified, even when a relationship was over, jealousy led me to burn bridges that I wished I hadn't.

3) College isn't for everyone, but you'll rarely be put square in the middle of so much potential experience. You'll meet people you probably wouldn't have otherwise, and as you eventually pursue your major, you'll get to know people who share your passions and dreams. Despite all the bullshit ways in which college sucks, it's still a pretty unique path on the way to adulthood. But on that note...

4) Learn to manage your money. It's way too easy to get into unsustainable debt. It only gets worse, and it makes everything harder. We don't always see the consequence of credit cards and loans when we're young, because the future seems so distant and undecided. But that debt isn't going anywhere... Try not to borrow money that you can't imagine yourself paying back now.

5) Floss every day, not just a couple times per week when you remember, or when you've got something stuck in your teeth. It matters, even if you're in your 20s and you've never had a cavity.

6) You'll always hear about living in the moment, seizing the day... It's tough to actually do. But there's something to be said for looking inward, and trying to recognize when too much of our attention is focused elsewhere. Constantly serving the future won't always pay off, at least not in the ways we think it will when we're young.

This sentiment doesn't have much value when it's put in abstract, existential terms, like it usually is. The best you can do is try to be aware of your own willingness and ability to be open to experiences. Think about ways in which you might be rejecting the here and now, even if it's as seemingly-benign as not going out with some friends because you just saw them, or you already went to that place they're going to. We won't recognize the good old days for what they were until they're already gone. The trick is having as many good days as possible.

7) Don't start smoking; you'll never quit as soon as you'll think you can. If you do start, make yourself quit after a couple years, no matter what. Keep your vices in check; drugs and alcohol in moderation. Use condoms, use birth control.

8) Don't make love wait. Tell your friends and family you love them often, and show them when you can. You're going to lose people, so it's important. Statistically, some of you will die young, yourselves.

When it comes to relationships, don't settle if you can't tell yourself you're in love, and totally believe it. Don't let complacency and familiarity get in the way of pursuing love. Don't be afraid to end relationships because they're comfortable, or because you've already invested so much into them.

Being young is a gift, and it won't last forever. You need to use that gift to experience all the love that you can, at least as a means to finding the person you really want to grow old with, if that's what you want. Regardless, you don't want to miss out on loving someone, and being loved, because of fear. Don't be reckless; just be honest with yourself.

9) Take care of your body. Neglecting it makes everything tougher. That doesn't mean you have to work out every day and eat like a nutritionist, but if you're overweight or you have health issues, do what you can to fix it. Losing weight isn't easy, but it's not as hard as people make it out to be. And it's one of the most important things you can do to invest in a healthy adulthood.

Don't put off nagging health issues because you think you'll be fine, or you don't think you'll be able to afford it, or you're scared of the outcome. There will always be options, until there aren't. Most people never get to the no-options part. Or, they get there because all the other options expired.

10) Few things will haunt you like regret. Making the wrong choice, for example, usually won't hurt as much. I guess you can regret making the wrong choice, but my deepest regrets come from inaction, complacency and indifference.

So how can we avoid regret? I don't know, lol. I don't think it's as simple as just commiting to choices... Choosing to do nothing is still a choice, after all. I think it's more about listening to your gut, as cliche as that sounds.

To thine own self be true, I guess. It's worth a shot, even if you fail. Almost anything is better than regret.

Lads, I will be real with you: some of you show absolute contempt to the actual academic study of the field.

In a previous rant from another ranter it was thrown up and about the question for finding a binary search implementation.

Asking a senior in the field of software engineering and computer science such question should be a simple answer, specifically depending on the type of job application in question. Specially if you are applying as a SENIOR.

I am tired of this strange self-learner mentality that those that have a degree or a deep grasp of these fundamental concepts are somewhat beneath you because you learned to push out a website using the New Boston tutorials on youtube. FOR every field THAT MATTERS a license or degree is hold in high regards.
"Oh I didn't go to school, shit is for suckers, but I learned how to chop people up and kinda fix it from some tutorials on youtube" <---- try that for a medical position.

"Nah it's cool, I can fix your breaks, learned how to do it by reading blogs on the internet" <--- maintenance shop

"Sure can write the controller processing code for that boing plane! Just got done with a low level tutorial on some websites! what can go wrong!"

(The same goes for military devices which in the past have actually killed mfkers in the U.S)

Just recently a series of people were sent to jail because of a bug in software. Industries NEED to make sure a mfker has aaaall of the bells and whistles needed for running and creating software.

During my masters degree, it fucking FASCINATED me how many mfkers were absolutely completely NEW to the concept of testing code, some of them with years in the field.

And I know what you are thinking "fuck you, I am fucking awesome" <--- I AM SURE YOU BLOODY WELL ARE but we live in a planet with billions of people and millions of them have fallen through the cracks into software related positions as well as complete degrees, the degree at LEAST has a SPECTACULAR barrier of entry during that intro to Algos and DS that a lot of bitches fail.

NOTE: NOT knowing the ABSTRACTIONS over the tools that we use WILL eventually bite you in the ASS because you do not fucking KNOW how these are implemented internally.

Why do you think compiler designers, kernel designers and embedded developers make the BANK they made? Because they don't know memory efficient ways of deploying a product with minimal overhead without proper data structures and algorithmic thinking? NOT EVERYTHING IS SHITTY WEB DEVELOPMENT

SO, if a mfker talks shit about a so called SENIOR for not knowing that the first mamase mamasa bloody simple as shit algorithm THROWN at you in the first 10 pages of an algo and ds book, then y'all should be offended at the mkfer saying that he is a SENIOR, because these SENIORS are the same mfkers that try to at one point in time teach other people.
These SENIORS are the same mfkers that left me a FUCKING HORRIBLE AND USELESS MESS OF SPAGHETTI CODE

Specially to most PHP developers (my main area) y'all would have been well motherfucking served in learning how not to forLoop the fuck out of tables consisting of over 50k interconnected records, WHAT THE FUCK

"LeaRniNG tHiS iS noT neeDed!!" yes IT fucking IS

being able to code a binary search (in that example) from scratch lets me know fucking EXACTLY how well your thought process is when facing a hard challenge, knowing the basemotherfucking case of a LinkedList will damn well make you understand WHAT is going on with your abstractions as to not fucking violate memory constraints, this-shit-is-important.

So, will your royal majesties at least for the sake of completeness look into a couple of very well made youtube or book tutorials concerning the topic?

You can code an entire website, fine as shit, you will get tested by my ass in terms of security and best practices, run these questions now, and it very motherfucking well be as efficient as I think it should be(I HIRE, NOT YOU, or your fucking blog posts concerning how much MY degree was not needed, oh and btw, MY degree is what made sure I was able to make SUCH decissions)

This will make a loooooooot of mfkers salty, don't worry, I will still accept you as an interview candidate, but if you think you are good enough without a degree, or better than me (has happened, told that to my face by a candidate) then get fucking ready to receive a question concerning: BASIC FUCKING COMPUTER SCIENCE TOPICS

* gays away into the night

Just started watching Mr Robot and freaking love it.

Note to self, sometimes hype is justified.

str(int(3))

Note to self: don't code when you're drunk.

Note to self: Don't use npm in a Google Drive folder

KISS.
Keep it simple, stupid.

At the beginning the project is nothing but an idea. If you get it off the ground, that's already a huge success. Rich features and code quality should be the last of your worries in this case.

Throw out any secondary functionality out the window from day 0. Make it work, then add flowers and shit (note to self: need to make way for flowers and shit).

Nevertheless code quality is an important factor, if you can afford it. The top important things I outline in any new non-trivial project:
1. Spend 1-2 days bootstrapping it for best fit to the task, and well designed security, mocking, testing and extensibility.
2. Choose a stack that you'll most likely find good cheap devs for, in that region where you'll look in, but also a stack that will allow you to spend most of your time writing software rather than learning to code in it.
3. Talk to peers. Listen when they tell that your idea is stupid. Listen to why it's stupid, re-assess, because it most probably is stupid in this case.
4. Give yourself a good pep talk every morning, convincing you that the choices you've made starting this project are the right ones and that they'll bring you to success. Because if you started such a project already, the most efficient way to kill it is to doubt your core decisions.

Once it's working badly and with a ton of bugs, you've already succeeded in actually making it work, and then you can tackle the bugs and improvements.

Some dev is going to hate you for creating something horrific, but that horrific thing will work, and it's what will give another developer a maintenance job. Which is FAR, far more than most would get by focusing on quality and features from day 0.

Note to self: never ever touch the bugzapper that's busy zapping a mosquito! Always remember that there's well over a 1000 volts on there regardless of its power rating. Anything over 50V can kill you!

.. if only my drunken fool self would realize that. Seriously though.. the kick of a bugzapper's shock, it's amazing! Just like drugs however, don't try it at home. Oh well. At least not me but yet another mosquito has bitten the duster. Serves those parasitic bitches right!!!

Note to self: Never leave a non-dev person mid-way through a Windows installation. They'll find a way to fuck it up and then blame it on you.
//this one restarted his system mid-installation coz it was 'taking too long'.
Why is common sense in such scarcity?

note to self : don't be too humble.

Why?

I just got Roasted in front of Advanced Programming class by a person who got an A in previous class by 100% copying other's work and change all variable and function name to differ.

Note to self: avoid eyeglasses when pixelated.

This story starts over two years ago... I think I'm doomed to repeat myself till the end of time...

Feb 2014
[I'm thrust into the world of Microsoft Exchange and get to learn PowerShell]

Me: I've been looking at email growth and at this rate you're gonna run out of disk space by August 2014. You really must put in quotas and provide some form of single-instance archiving.
Management: When we upgrade to the next version we'll allocate more disk, just balance the databases so that they don't overload in the meantime.

[I write custom scripts to estimate mailbox size patterns and move mailboxes around to avoid uneven growth]

Nov 2014
Me: We really need to start migration to avoid storage issues. Will the new version have Quotas and have we sorted out our retention issues?
Management: We can't implement quotas, it's too political and the vendor we had is on the nose right now so we can't make a decision about archiving. You can start the migration now though, right?
Me: Of course.

May 2015
Me: At this rate, you're going to run out of space again by January 2016.
Management: That's alright, we should be on track to upgrade to the next version by November so that won't be an issue 'cos we'll just give it more disk then.

[As time passes, I improve the custom script I use to keep everything balanced]

Nov 2015
Me: We will run out of space around Christmas if nothing is done.
Management: How much space do you need?
Me: The question is not how much space... it's when do you want the existing storage to last?
Management: October 2016... we'll have the new build by July and start migration soon after.
Me: In that case, you need this many hundreds of TB
Storage: It's a stretch but yes, we can accommodate that.

[I don't trust their estimate so I tell them it will last till November with the added storage but it will actually last till February... I don't want to have this come up during Xmas again. Meanwhile my script is made even more self-sufficient and I'm proud of the balance I can achieve across databases.]

Oct 2016 (last week)
Me: I note there is no build and the migration is unlikely since it is already October. Please be advised that we will run out of space by February 2017.
Management: How much space do you need?
Me: Like last time, how long do you want it to last?
Management: We should have a build by July 2017... so, August 2017!
Me: OK, in that case we need hundreds more TB.
Storage: This is the last time. There's no more storage after August... you already take more than a PB.
Management: It's OK, the build will be here by July 2017 and we should have the political issues sorted.

Sigh... No doubt I'll be having this conversation again in July next year.

On the up-shot, I've decided to rewrite my script to make it even more efficient because I've learnt a lot since the script's inception over two years ago... it is soooo close to being fully automated and one of these days I will see the database growth graphs produce a single perfect line showing a balance in both size and growth. I live for that Nirvana.

Note to self : when a client say "we want to develop 'exact clone' of SomeFuckingBigCompany" - Say NO.

Note to self: It's NEVER that simple.

Note to self: ALWAYS cache API calls.

note to self: python won't write to a file if it is hidden in windows

!dev

To anyone suffering from chronic pain, especially lower back pain: Don't get fooled by shitty doctors. And don't expect doctors to magically heal you. If you want to stop your suffering, you need to be proactive.

What? But my herniated disc from 10 years ago... bla bla bla. So what? It's not going to get better when your only exercise is putting on your socks. Chances are 99% that your spine has shit to do with your pain. Go to a proper chronic pain therapy instead of downing opiods and getting sick notes.

Note to self: Do your sports every day you lazy bastard. Eat healthy, sleep regularly, don't stress out over every damn thing and don't forget to fucking relax!

Note to self:
Don't try to remove elements from a list using a for loop because the FUCKING LIST SIZE CHANGES!
Just copy required elements to another list and discard the previous.
Spent fucking 2 hours on this.
/Rant

Note to self: don't try to code during hangover

Okay.. I just did it. I had to reinitialize a server because I lost the single SSH keypair (probably the one from my BELOVED Windoze desktop that I recently had to reinstall) that was authorized to access the server, and I didn't add any of the other clients' keys to the server's authorized_keys.

Note to self: replicate all your fucking keys or (or rather, and) back them the fuck up into your keychain already!! Why else does that keychain USB stick exist, Condor, you bloody fucking moron?!!

Well, at least now the admin panel on Aruba Cloud doesn't say "Ubuntu 14.04" that's been upgraded to Ubuntu 18.04 anymore, but 18.04 as it should.. but that's about the only good thing.

Note to self: don't read devrant right before bed -you get too many breakthrough ideas and motivation and need to sleep instead!

Some companies are structured and work as cults.

Went to company party several days ago and felt as if I was 🧠 🧼. The way they talk about the company, people, “mission”, social structure of employees etc. I literally felt as the only one who’s seeing through it.

Note to self: If I were to start my own company, I have to read a bunch of books about cults.

Anyone else worked at cult-like startups?

Note to self: if you work on a logo concept that you know it won't work and it's hard to implement/loses meaning in monocolor, don't show it to your client as part of the first round of concepts.

Because that's the one they'll choose.

I think my server got hacked, yesterday I made a new server on scaleway for the sake of testing I made a user called dev, with password dev. Forgot to change password before I went to bed.

Logged in today to find that load is 5x.x and this (image) in my crontab

Note to self: You are a disgrace, who the hell uses 'dev' as password for ssh on port 22 -_-

Note to self : stop trusting everyone in group assignments.

It always becomes a catastrophe right before the deadline 😥

When will I fuckin learn that
a) customers lie
b) customers are sloppy
c) customers are wrong
d) customers do not do their work (properly)
e) customers want us to do their (dirty) work
f) possibly all of the freakinly above?! + khm....

They will fuckin aaaalwaaaays say sth is not working after the update..
And I will alwaaaays assume I fucked up something..even if I didn't touch that part of the code/data..
And almost aaaaalways it turns out that the bug they complain about is how the system worked (or didn't work) before the update and/or some fuckup from their side..

Anyhow, I rushed over, grabbed the files went testing in dev..wtf, output is different, mine is ok, theirs is..wtf is that shit?!

Transfer newly built dll to test..same shit as on prod..wtf?! How?!

I assumed they have thing A correctly linked to thing B.. ofc thing A was linked to thing C in their case and in another case (our test) to correct thing B..
I got chillies when grabbing files, that
I should have tripple checked that they didn't fuck up something on the link part, but I just assumed they know what they were doing & that they checked they linked correct files with correct content already, before being pissy that the update fucked up things.. riiiight!! :/

I wanted to find solutions to this fuckup asap so I disregarded my gut feeling..yet again!! Fuuuck!
I've spent too much time trying to find ways to fix a bug that wasn't even a real bug to begin with.. :/

Fuuuuuck!!

So yeah, always treat the customers like they are 3yrs old & have no clue what they are doing & check exactly wtf they were indeed trying to do..it will save you time & nerves..

And note to self: reread this shit daily!! And imprint it in your brain that everything is not always your fault!!

Note to my past self:

Thank you for taking care of me and assuming that out of no fucking sudden authorization token will be required to perform an API call!
You saved me so much refactoring and modifications with your tiny little assumption of how fuckups will think :)

Note to self:

Don’t use npm, use yarn!
Don’t use npm, use yarn!
Don’t use npm, use yarn!

Don’t use what??👂
Npm! Use yarn!

Well done!! Now repeat this 5 times a day.

Trilium notes are amazing. If you need a self-hosted note taking app, Trilium is a way to go.

That moment when you take a look back at your old portfolio websites...

I have to cringe and laugh at the same time rn. The way I styled it. OMG...

Self note: You will still cringe in the future, when you are going to look back at your current portfolio website.

Sometimes I wish I was driven by positive reasons, and not by self-loathing and sense of worthlessness. I didn't have an actual vacation for over 3 years.
I am now in Thailand with my parents, and I am working my ass off to meet IROS/RAL deadline instead of chilling. The urge to continue working is really compulsive. I am very tired.
On a brighter note, the early experiments I ran look promising

If anyone has been keeping up with my data warehouse from hell stories, we're reaching the climax. Today I reached my breaking point and wrote a strongly worder email about the situation. I detailed 3 separate cases of violated referential integrity (this warehouse has no constraints) and a field pulling from THE WRONG FLIPPING TABLE. Each instance was detailed with the lying ER diagram, highlighted the violating key pairs, the dangers they posed, and how to fix it. Note that this is a financial document; a financial document with nondeterministic behavior because the previous contractors' laziness. I feel like the flipping harbinger of doom with a cardboard sign saying "the end is near" and keep having to self-validate that if I was to change anything about this code, **financial numbers would change**, names would swap, description codes would change, and because they're edge cases in a giant dataset, they'll be hard to find. My email included SQL queries returning values where integrity is violated 15+ times. There's legacy data just shoved in ignoring all constraints. There are misspellings where a new one was made instead of updating, leaving the pk the same.

Now I'd just put sorting and other algos, but the data is processed by a crystal report. It has no debugger. No analysis tools. 11 subreports. The thing takes an hour to run and 77k queries to the oracle backend. It's one of the most disgusting infrastructures I've ever seen. There's no other solution to this but to either move to a general programming language or get the contractor to fix the data warehouse. I feel like I've gotten nowhere trying to debug this for 2 months. Now that I've reached what's probably the root issue, the office beaucracy is resisting the idea of throwing out the fire hazard and keeping the good parts. The upper management wants to just install sprinklers, and I'm losing it.

Working with assembly is just something different... note to self: keep a cheat-sheet with the labels and corresponding addresses at hand.....

Note to my future self:
A 2048Bit SSH key is minimum,
4096Bit is good enough
8182Bit is too much
16364Bit... why do I even bother about this size

Note to self: stop trying to write literally everything modular, it's not always the best thing to do.

Someone else disturbing me while I'm thinking about technicalities. Makes me lose my shit because recollecting everything afterwards is often more difficult than the problem itself.

Note to self: tell cleaning lady to keep disturbances to a minimum when I'm working, and turn notifications on the Fandroids off before starting work. No I'm not interested in that Telegram message right now. And God bless OnePlus for putting in a physical slider for that.. more phone manufacturers should start doing this.

This rant is not about avoiding bad company but instead: If you find your self in a bad company make sure to note what is bad in terms of:
1. What is wrong?
2. Is it wrong by your book or by everyone's book?
3. How things should be done if you were in charge?
4. Are you able to be productive if those "wrong" things where done correctly? For example if they should have used gitlab cli for auto deployment, do you know how to do that? No? Learn. Yes? Move to the next item in the list

There is no way to avoid bad companies unless you are really lucky, just make the best out of where you are now :)

Note to self:
Fucking comment your fucking code
So I finally got time to work on an old project and now I can't figure out what does what.

Legit have to control myself not responding to subtle sarcasm or passive aggressiveness in people's rant or comments with utter salt and shade. 😒😒😒

Note to self: Live and let die.

Note to self: never EVER buy iPhone again. “It won’t stutter after a year”, they’ve said.
Right now my 6s is just one big overheating piece of mess. Right now I have to charge it 3 times a day. Resprings randomly. Very often discharges 2% per minute. All the time lacks memory. iCloud picture syncing SUCKS. The Lightning cable is the worst excuse for buying overpriced cables which will break after a half of year. The only plus is a camera, how easy it is to update the iOS, included earbuds, iMesssage (but I use WhatsApp nonetheless) and battery widget.

And that’s it.

If someone says ever again that “iOS is the best operating system, it doesn’t have any issues whatsoever”, I would say “stop doping”, because I don’t see why it’s so great. Just while typing this rant my battery decreased from 25% to 15%

Note to self: never drink and format

Reinstalling my linux partition and... Oh whoops.. ... ...
That was the windows partition.. ...
*face palm*

Well I guess that's gone forever now...

I should have learned by now that I don't multitask well... Note to self: Don't talk on the phone and re inst... Scratch that... Note to self: Do one damn thing at a time dummy..

Note to self:

DO NOT listen to Albinoni's Adagio or you ain't gonna get shit done. 🤦

Note to self:
Fifty shades of gray is not about CSS or any other subject you care about. Delete mental association so as not to react like Pavlov's dog every time you hear/see title mentioned in mass media.

Squirrel!

Note to self: Pointing your tests at a non disposable DB will cause very very bad things to happen. No idea what the flying fuck I was thinking - but praise to the data gods it wasn't a production elastic!

"Our system has detected that this message is[nl]421-4.7.0 suspicious due to the very low reputation of the sending IP address"

Oh shit..

Note to self: Don't test on production servers. Gmail has now blocked my ass.

My manager insists I use a debugger. Note to self, next time lie and say I use a debugger

Note to self, don't fix a minor bug that will not effect the demo right before the live demo. My program that was working great didn't work anymore during the demo because of my quick bug fix I figured I had a few minutes to add to my code.

Note to self: if you have a tight deadline and need to rush a website / web app, use SASS because you're going to end up with 800+ lines of CSS because you suck at your job and you keep telling yourself you'll refactor everything but never get around it.

Not really a rant and not very random. More like a very short story.

So I didn't write any rant regarding the whole Microsoft GitHub topic. I don't like to judge stuff quickly. I participated in few threads though.

Another thing is I also don't use GitHub very much apart from giving 🌟 to repos as a bookmark. Have one hobby project there. That's all. So I don't worry that much. I'm that selfish and self concerned. :3

I was first introduced to version control system by learning how to use tortoisesvn around 2008. We had a group project and one of the guys was an experienced and amazing programmer unlike the rest of us. He was doing commercial projects while we were at our 1st and 2nd year. Uni had svn repo server. He taught us about tortoisesvn. He also had Basecamp and taught us how to use it as well. So that's how I learned the benefits of using versioning tools and project management tools. On side note, our uni didn't teach any of those in detail :3

After that project, I was hooked to use versioning tools. So until school kicked me out, I was able to use their svn server. When I was on my own, I had to ask Google for help. I found a new world. There are still free svn services that I can use with certain limited functions. That's not the new world; I found people saying how git is better than svn in various ways. It was around 2010,2011.

At first I was a bit reluctant to touch git because of all the commands in terminal approach. But then I found that there is tortoisegit. I still thank tortoisesvn creator for that. I'm a sucker for GUI tools. So then I also have to pick which git servers to use. Hell yeah, self hosted gitlab is the way to go man. Well that's what the internet said. So I listened. I got it up and running after numerous trial and error. I used it briefly. Then I came back to my country on 2012-2013; the land of kilobytes per minute (yes not second, minute).

My country's internet was improved only after 2016. So from 2013 to 2016, I did my best not to rely on internet. I wasn't able to afford a server at my less than 10 people, 12ft*50ft office. So I had to find alternative to gitlab which preferably run on windows. Found bonobo and it was alright. It worked. Well had crazy moments here and there when the PC running Bonobo got virus and stuff. But we managed. We survived. Then finally multi national Telecom corporates came to our country.

We got cheaper and faster mobile data, broadband and fiber plans. Finally I can visit pornhub ... sorry github. Github is good. I like it. But that doesn't mean I should share my ugly mutated projects to the rest of the world. I could keep using Bonobo but it has risks. So I had to think for an alternative. I remembered that gitlab didn't have cloud hosting service when I checked them out in the past. So I just looked into Bitbucket and happy with their free plans of 5 users and unlimited private repos. I am very very cheap and broke.

That's why I said I don't really care that much about the whole M$GitHub topic at the beginning. However due to that topic, I have visited GitLab website again and found out they have cloud hosting now and their free plan is unlimited users and unlimited repos. So hell yeah. Sorry BB. I am gonna move to cheaper and wider land.

TL;DR : I am gonna move to GitLab because of their free plan.

Note to my self: READ THE FUCKING WARNINGS!!!

So note to self, when creating random IDs, maybe generating 1,000 digit long IDs constantly is the source of that massive ram spike and subsequent crash...

note to self:
install the fucking network tools DURING the Arch installation, BEFORE you reboot and remove the install media.

wrote this handy dandy notebook guide up because i get tired of having to look up the archwiki

I'm looking at someone's shit code... and I have to remind myself... we all have the ability to be fucking stupid, especially when we're trying to do something in order to do something else so that we can do something else.

note to self: "always remember, they did the best they could with the resources they had at the time".

But that doesn't change the fact that I need to clean up the crap they left behind.

Note to self: never use Arch Linux as a server anymore

when i just read stuff about a programming language without putting any effort on it, after a month of vacation, every single thing i actually read and learnt over the past year came floating out of my brain and now i have to start over just so i can finish a programming challenge in time

note to self: time to get serious and keep up my pace in this devRace

Never include freelance as a budget source in daily expenses. Think of it as a reward only! Now, plans are cancelled T_T

Younger brother wanted to know how to work with users in Windows using cmd. I showed him a few things, told him PS is better but he can fiddle and just use net /? For the options he can use.

Go out for an hour. Come back and my user profile is gone. So the Padawan net user rangarr023 /del
My profile.

Time for some quickfix takeown commands haha.

Note to self. Let brother try things on his own pc, and next time use a vm.

I will give you the money for the server and the domain name (not caring about the conversion rates and transfer charges) and I expect the app delivered in record time. We can talk about payment later.
Note to self: “Never work with people you know.”

Hi everyone, I’m new here and this is also my first rant.

I’m in the job hunting boat once again and I’ve been looking at Junior front-end positions. I thought I’d rant about something that always annoys me when looking through the requirements.

Wait, so in order to land a Junior front-end job, I have to be a freshly graduated person with a Master’s degree in CS, with a minimum of 3 years working experience and all that just to come code in HTML, CSS and JS?

For the love of god, I’m one person damn it. It’s not like I’m a self-taught developer that taught myself those things and more in a shorter period of time after quitting college.

On a more serious note, I’m not by any means claiming that I know everything, but having a CS Master’s degree for these types of positions is clearly ridiculous in my opinion.
Sometimes I wonder if the people writing these things are making it up as they go or whether they’re actually serious.

So I have a dual boot Windows 10 / Ubuntu 16.04.
This evening, I finally decided to update Ubuntu to 17.10.

Note to self, never try to install Ubuntu from the live usb when trying the "demo", prefer to install on boot, because this fucker encountered an error, forced me to reboot then decided to occupy the whole disk and wipe Windows out.

I'm sure that Ubuntu 17.10 was made by DevRant, that's totally something you guys could do 😂

In our department, we've to send some reports at different times in the same month, for example, three the first day, one the fifteenth, three the last day...

This was a task assigned to my coworker, but it consumed a lot of time to modify and execute the required querys and write the reports in Excek with the results, so O was assignes to create a program that created the reports automatically.

I asked my coworker for the querys, a lot of times since he "forgot it", and once my program was fully completed him, I asked him to test it and tell me if he saw any errors, if the reports were done correctly, etc... And, twenty days later, when I asked him again, told me that everything was okay, so the whole months of July and August, the reports were done automatically.

Today we've receives a ton of emails about how the reports were not correct, how the information was incomplete and such.

Guess who gave me only half the querys requested. Now I've to do every single of them manually. While my manager rants.

Note to future self: Never trust that guy again, and always re-check everything he checks. This better be a lesson for the future.

Docker y u no mounting volumes on Windows anymore...?

World y u use Windows at all?

Note to self, y u no problem-solving instead of devrant posting?

Multi-continent low-latency auto-scaling eventually-consistent kubernetes-orchestrated and spark-powered multi-cloud data-plarform.

(Note to self: why do jargon words always come in twos?)

But seriously, the engine ELT's naval and logistical data from every continent and ocean and feeds a global analytics platform for less then 0.25 USD per ingested Gb across all systems.
And sometimes the PODs are even onboard en-route ships! Edge computing, y'all!

Tech project I'm most proud of.

Get an issue reported today stating that a report can't be submitted in a product we maintain. Taking their word for it I start investigating on our local copy of the product. Everything works as intended. Ok... strange. Take a look at the production copy aaaaand it was submitted. No issues at all.

Note to self. Don't believe the client.

NOTE TO SELF:

Verify with your coworkers about how you plan to attack a certain feature if you’re unsure, especially since you work remotely. If not, you’ll have to fucking redo a feature three times

My friend sent me this as WYSIWYG

/* A simple quine (self-printing program), in standard C. */ /* Note: in designing this quine, we have tried to make the code clear * and readable, not concise and obscure as many quines are, so that * the general principle can be made clear at the expense of length. * In a nutshell: use the same data structure (called "progdata" * below) to output the program code (which it represents) and its own * textual representation. */ #include <stdio.h> void quote(const char *s) /* This function takes a character string s and prints the * textual representation of s as it might appear formatted * in C code. */ { int i; printf(" \""); for (i=0; s[i]; ++i) { /* Certain characters are quoted. */ if (s[i] == '\\') printf("\\\\"); else if (s[i] == '"') printf("\\\""); else if (s[i] == '\n') printf("\\n"); /* Others are just printed as such. */ else printf("%c", s[i]); /* Also insert occasional line breaks. */ if (i % 48 == 47) printf("\"\n \""); } printf("\""); } /* What follows is a string representation of the program code, * from beginning to end (formatted as per the quote() function * above), except that the string _itself_ is coded as two * consecutive '@' characters. */ const char progdata[] = "/* A simple quine (self-printing program), in st" "andard C. */\n\n/* Note: in designing this quine, " "we have tried to make the code clear\n * and read" "able, not concise and obscure as many quines are" ", so that\n * the general principle can be made c" "lear at the expense of length.\n * In a nutshell:" " use the same data structure (called \"progdata\"\n" " * below) to output the program code (which it r" "epresents) and its own\n * textual representation" ". */\n\n#include <stdio.h>\n\nvoid quote(const char " "*s)\n /* This function takes a character stri" "ng s and prints the\n * textual representati" "on of s as it might appear formatted\n * in " "C code. */\n{\n int i;\n\n printf(\" \\\"\");\n " " for (i=0; s[i]; ++i) {\n /* Certain cha" "racters are quoted. */\n if (s[i] == '\\\\')" "\n printf(\"\\\\\\\\\");\n else if (s[" "i] == '\"')\n printf(\"\\\\\\\"\");\n e" "lse if (s[i] == '\\n')\n printf(\"\\\\n\");" "\n /* Others are just printed as such. */\n" " else\n printf(\"%c\", s[i]);\n " " /* Also insert occasional line breaks. */\n " " if (i % 48 == 47)\n printf(\"\\\"\\" "n \\\"\");\n }\n printf(\"\\\"\");\n}\n\n/* What fo" "llows is a string representation of the program " "code,\n * from beginning to end (formatted as per" " the quote() function\n * above), except that the" " string _itself_ is coded as two\n * consecutive " "'@' characters. */\nconst char progdata[] =\n@@;\n\n" "int main(void)\n /* The program itself... */\n" "{\n int i;\n\n /* Print the program code, cha" "racter by character. */\n for (i=0; progdata[i" "]; ++i) {\n if (progdata[i] == '@' && prog" "data[i+1] == '@')\n /* We encounter tw" "o '@' signs, so we must print the quoted\n " " * form of the program code. */\n {\n " " quote(progdata); /* Quote all. */\n" " i++; /* Skip second '" "@'. */\n } else\n printf(\"%c\", p" "rogdata[i]); /* Print character. */\n }\n r" "eturn 0;\n}\n"; int main(void) /* The program itself... */ { int i; /* Print the program code, character by character. */ for (i=0; progdata[i]; ++i) { if (progdata[i] == '@' && progdata[i+1] == '@') /* We encounter two '@' signs, so we must print the quoted * form of the program code. */ { quote(progdata); /* Quote all. */ i++; /* Skip second '@'. */ } else printf("%c", progdata[i]); /* Print character. */ } return 0; }

Note to self: Commit! God fuckin' damnit. COMMIT!!

After doing some self reflection today, I realized that I could finish college (I passed every exam), but the amount of time I spent for college (basically the whole day each day) is too much to handle for me.

Note to future me: If you blame yourself for why you didn't continue, it's because of the lack of time, freedom and calmness of your mind. Otherwise you would have went literally insane.

Trust me, your early version is in that phase right now, and I know it better than you do.

Note to self: Always do a dry run first when you have --delete-before using rsync.

Long story short I wanted to restore some folders from my external HDD to the home directory on my laptop XD I should have specified the exact folders 😹

#RANT_AHEAD

Almost everyone nowadays uses a PC, Laptop, Smartphone but sadly not even 60% of the total potential of the hardware is being used.
.
And no - you don't require custom cooling to use the whole 100% of the total potential, stock cooling is more than enough.
.
IRL "programmers" these days don't do any fscking effort to optimise their code and give it all up as some kinda shitty "hot patch" - code of their looks disturbing with no security features + optimisation. (wAnBlOwS products remain an example)
.
Even when you're using python you can push your project to limits. Instead of shoving face-size ASCII banners why don't chaps stress test their projects? Oh I forgot the community runs on show-offs and CVs ...

.
Note to Self : Optimisation is the key to integrate Technology with Nature.

Lua users, have you used moonscript?

It's a little language that has it's own interpreter or can be compiled down to Lua and it's absolutely lovely (currently using it with Love2d).

Of course, as with most things, what I love about it also royally pisses me off sometimes.

For starters local has to be declared for variables, unlike lua.
Otherwise the variable goes to _
Also note, that some tutorials literally tell you the opposite.

all variables are local by default
unless you don't declare them
then they go to _ (throwaway)
Some tutorials get this wrong too.

all variables have to be declared local
except tables. failure to declare a table WITHOUT a local will cause things like
table.insert to fail with "nil" values for no god damn reason.
No tutorial I could find mentioned this.

Did you know we call methods with '\'?
By the way, we call methods with '\'.
Why? Who the fuck knows.
Does make writing web routes more natural though.

Variables in the parameters of new are declared and bound for you. Would have loved to know this before hand instead of trying
to bind to them like a fucking idiot.

Fat arrows are used to pass in self for methods.
Unless you're calling a method. Then you use backwards slash. This fact is unhelpful when you're a beginner and dealing with the differences between the *other* arrow, the backslash, the fat arrow, and the fact that functions can be called with or WITHOUT parenthesis.
And on that note..

While learning all this other shit, don't forget parenthesis are optional!
Except when they're not!
..Like when you have a function call among your arguments and have to disambiguate which args belong to the outer call and to the inner call! Why not just be fucking consistent?

But on the plus size, ":" is now used for what it should have been used for in the fucking beginning: binding values to keys.
And on the downside, it's in a language thats built on top of another language that uses it for fucking *method calls*, a completely
different fucking usage.

And better still, to add to that brainfuckery thats lost in the mental translational noise like static on a fucking dialup modem, you define methods with the fat arrow. Wait, was that the single arrow or fat one? Yeah the fat one. Fuck. But not before you do THIS shit..

someShit: =>

yeah, you STILL include the god damn colon just so when you're coming from lua you can do a mental double take. "Why am I passing self twice? Oh right, because fuck me, I decided to use moonscript." It's consistent on that front but it also pisses me off.

A lot of these are actually quality of life improvements disguised as gotchas, but when you're two beers in to a 30 minute headscratcher it sure doesn't fucking feel like it.

Nevertheless, once I moved beyond the gotchas, it was like night and day. Sure moonscripts takes a giant steaming dump all over the lua output, like a schizophrenic alcoholic athena from the head of zeus, but god damn, when it works it just WORKS.

Locals that act like locals? Check.
Sane OOP? Check.
Classes, constructors, easy access to class methods, iterators? Check, check, check, check, check.

I fucking hate ceremony. Configuration over convention is for cunts. And moonscript goes a long ways toward making lua less cunty.
If you've ever felt this way while using lua, please, give moonscript a try.

You'll regret it, but in a good way!

Just finished fourth interview with a company (fuck me) for a solutions engineer position (I am a self taught dev that is transitioning to technical roles from a pretty "soft" background with the hope of being in a software engineer role within three years). Anyone have any experience with the solutions engineer role and some advice about it? Note: this IS an invitation to rant about solutions engineers so I know what NOT to do.

Note to self:
Close off ALL ways things could go wrong..

Long story short; I released a new feature, to be able to better follow up on any stock moves, their amounts, locations and even expiry dates. An older tool just bypassed that very verification and nothing was logged or taken out of stock.

~

Taking out an amount for a certain orderline has a shortcut in place to mitigate some of the mandatory steps that pickers need to take in order to verify what's being taken. This little tool only available, visible and possible for a very few select users.

I assigned some orders to one of these people, which made him think it was an urgent batch. It's only one product, for multiple orders, so he went to the location, took out the amount needed and then used the tool to quickly be able to prepare them for shipping.

This bypassed the new methods to check if the location actually had stock to take, which I had just enabled for 1 account.

Luckily I caught the miss-hap as I was monitoring that product first-hand and noticed the batch of orders was collected but the stock amount didn't update.

It was 5min before I was leaving work, so I investigated and then ran to the person in question to ask what he did; which was "I used that tool"

I facepalmed myself internally while blaming myself, as he couldn't know that it wasn't ready to use for that purpose.

The tools to fix this up are there already.. so I used that to fix some missing stock-takes manually.. Though I'll need to close that little tool for these kind of orders for sure, asap, probably when I get home, at least until I bring over its new logic to it.

Happy Tuesday? (:

So basically I am the computer guy in my office. If there is any hardware or software related problem, I am the guy who fix it or try to fix it in my own time.

Little bit of more backstory. Two month ago we got react native project from a client. My boss asked me if I want to do that project. he knew that I don't know react native but I want to learn it. So I said yes. I have worked over 12 hours per day to work on that project while learning react native ( I committed the final version to git today.)

Yesterday there was a meeting in our office about project deadlines and issue with current work and stuff. In that meeting one guy asked (this guy had personal beef with me) in rude way like why I am taking parts of pc and given other people. ( If there is any hardware issue, I use other parts from pc which are not currently in use. So basically a simpe resource allocation.)

I knew it was a targeted questio toward me but before I say anything, All people took his side. (I did all those repair after taking permission from my boss, so he did not take that question seriously.)

I spend lots of time fixing those problem so people work does not stop and this is the thank you I got in return. I did this over one and half year. Right now I am asking my self if I continue the work or not.

Note: I wrote this whole thing to get my anger out of me. Sorry for typos. I am little bit drunk and I am not good with English.

Remind me to finish the notebooks I've created in kaggle... 👀

Note to self: Next time remember to clean build when CMake is throwing an error, before you start whining to the library support team.

Debugging AWS IAM credentials wondering why they don't work for 5 hours.

Note to self: Check the clock first next time.

Note-taking app?

- viewed in browser
- server side self-hosted
- markdown for writing
- rendered pretty when viewing/next to markdown when editing
- folders/notebooks for sorting

Note to self: Always do private domain registrations. I've been getting emails for about a week now asking i want custom development services for the domains I registered 😡

Note to self: don't buy stickers to give to your coworkers, you'll end up wasting your money and time.

anyone ever try to create a self training two ai using a nn to play pong against each other ?

like what would happen ?

there is definately a cutoff point, everytime the other user scores.

on another note getting laid would make me feel better right now.

Note to self, selecting text to copy it into the paste buffer only works in the terminal. It doesn't work in chrome...

Note to self:
The power button on Ubuntu 16.04 while TeXstudio is open won't just open the panel for shutdown, lock,... it will also close TeXstudio... and shutdown my computer.

I have never been this serious with my life as a whole as I have since I started learning computer programming. I struggled to read one book a year (I mean non programming book like self improvement books e.t.c). Now I have finished two books in a little over a month and started reading a third book this month all while still studying programming. I started out with python and was honestly terrified of Java because of the semicolons, curly braces, parenthesis in front of if/else if/else statements but one day I decided to take a peek into a few Java programming books and found one "Learn Java the Easy Way" by Bryson Payne and it changed my life, quite literally. I read more now, I look forward to getting out of bed and any day I don't read, I just don't feel right. I need to read something and learn at least one new thing a day. If I feel awful at night, I just remind myself of the one new thing I learnt that day and that puts a smile on my face.

Side note, I am self-taught and started studying programming last year around November/December. Spent about two months on python and in January or February, I started Java. Been on Java since. Almost done with the Java book and looking forward to reading a more advanced book when I'm done.

Note to self: keep not trusting online tutorials and ALWAYS, A.L.W.A.Y.S take them with a grain of salt.

Now why do you fine lads think `nmcli networking off && nmcli networking on` over ssh is a bad idea? And how to quickly make it suitable for over-ssh-execution? Let's see who knows shell! [HINT: see tags for an almost-answer]

... when people not sure what shell characters mean are writing tutorials... FUCK!

Another 'fun' rant

Wrote a new server application and got the request from customer services to make it compatible with a slightly older DB version.

Today, CS asked me to install everything on the customer's test environment so I made a build and installed it there.

Wanted to run the service, no .Net framework 4.7.1 installed. Fine, download the installer ...

Start installing .Net framework 'unsupported OS'. Started looking into it. Customer is still running an old unsupported Windows Server 2008 ...

Asked some colleagues whether this was normal. Apparently, yes.

Seems CS isn't capable of telling customers to at least have a supported windows version when they want our software. As if security issues due to people here not understanding TCP/IP isn't enough, we now have security issues due to old, unsupported Windows versions.

Note to self: never trust anyone who says that 'security is the most important thing in our software enviornment'.

Sometimes I think that getting a degree was the biggest mistake I have ever done.

When professor wants to know why you did the work the way you did and you disagree as polite as you can, he calls you Arogant.. Like what the fuck, if you ask me 4 times why I did not expand the assigned task and I 4 times repeat that I want that shit as abstract as I can get. I already have it 5 times bigger as others god damnit, If you want me to focus on details, ask me to bring a tent..

A little bit of time later another professor assigns you a "Social network for schools"... Like wtf? U want facebook clone for free and in 4 weeks... What is this bullshit? You have mistaken uni for freelancer..

Because fuck you sideways... How dare you to have another classes?

Note for self... Next time open up a hotdog stand..

Note to self.. Check how your backup restore works before actually needing it...

Coworker got ransomware to his computer via targeted attack and managed to encrypt about 6000 files on Google Drive share... Which I have backed up. However there are a total of 100k files so total restore is not an option and with 60 users updating things can't do point in time restore either... And thanks to the backup softwares buggy cmd line interface I can't create command line script to restore the files one by one... So in the end I most likely need to restore via sluggish gui one by one...

Note: In this rant I will ask for advices, and confess some sins. I will tell my personal story- it will be long.

So basically it has been almost 2 years since I first entered the world of software development. It has been the biggest and most important quest of my life so far, but yet I feel like I missed a lot of my objectives, and lots of stuff did not go the way I wanted them to be, and it makes feel frustrated and it lowered my self esteem greatly. I feel confused and a bit depressed, and don't know what to do.

I'll start: I'm 23 years old. 2 years ago I was still a soldier(where I live there is a forced conscription law) in a sysadmin/security role. I grew tired of the ops world and got drawn more and more into programming. A tremendous passion became to burn in me, as I began to write small programs in Python and shell scripts. I wanted to level up more seriously so I started reading programming books and got myself into a 10 month Java course.

In the meanwhile I got released from army duty and got a job as a security sysadmin at a large local telco company. Job was boring and unchallenging but it payed well. I had worked there for 1 year and at the same time learned more and more stuff from 2 best friends who have been freelance developers for years. I have learned how to build full-stack mobile apps and some webdev, mainly Android and Node.js. However because I was very inexperienced and lacked discipline, all of my side projects failed horribly, and all attempts to work with my experienced friends have failed too- I feel they lost a lot of trust for me(they don't say it, but I feel it, maybe I'm wrong).

I began to realise I had to leave this job and seek a developer job in order to get better, and my wish came true 6 months ago when I finally got accepted into a startup as a fullstack webdev, for a bit lower wage but I felt it was worth it. I was overjoyed.

But now my old problems did not end, they just changed. My new job is a thousand times harder and more intensive than the old one. I feel like it sucks all the energy and motivation that was still left in me, and I have learned almost nothing in my free time, returning home exhausted. My bosses are not impressed from my work despite me being pretty junior level, and I feel like I'm in a vicious cycle that keeps me from advancing my abilities. My developer friends I mentioned earlier have jobs like I do and still manage to develop very impressive side projects and even make a nice sum of money from them, while I can't even concetrate on stupid toy projects and learning.

I don't know why It is like this. I feel pathetic and ashamed of my developer sins and lack of discipline. During that time I also gained some weight that I'm trying t lose now... I know not all of it is my fault but it makes me feel like crap.

Sorry for the long story. I just feel I need to spill it out and hope to get some advices from you guys who may or may not have similar experiences. Thanks in advance for reading this.

It's always great idea to map common keyboard shortcuts to something completely different, such as when IDEA sets the default behaviour of Ctrl+Y to "remove the line under caret". Thanks guys, I love surprises, next time try something with ctrl+c.

Note to my future self: when installing the IDEA again, remember to remap the ctrl+y..

Note to self: shared folders work both ways...

Note to self: never use gdb commands as variables in my program.

Note to self: when tracking down why your data differs from the DB...make sure the damn Workbench view is fresh. It saves a couple hours of frustration and misery.

Note to self: when you extend a functionality by rewriting a relevant part, remember to mark the old code as deprecated or delete it.

AKA "why the hell I´m not seeing anything in logs/db that reflects my changes" T_T

Got rejected for an UX designer position turns out they were realy looking for a UX tester with project leadership skills 🤗 does that even mix bro???

Note to self 🤔 never apply for jobs there in the future 🤔

Note to self: online single player games are addictive but they either never end or the ending sucks. Either way, they waste a whole lot of time and eventually I will get bored of it and realize how much time I've wasted and that there is not actual reward for "finishing" it....

Note to self for later: whenever I git push something from any side project, next time just add a TODO list so I don't loose time to remember what the fuck I was doing

Note to self: *ALWAYS* pull updates from upstream before starting to add or fix stuff in a GitHub project. Or any other collaborative project for that matter.

Now, it's time to slap myself for forgetting...

I can't integrate this damn camera (with a system) and I should get over it already, but I'm anal about having things the way I want them so I guess I'll suffer a bit longer before giving up.

Note to self: give up already and move on!

Past me is such a dick:
"Note to future self: this is a dirty hack taken straight from the ONLY StackedOverflow result. Didn't understand it then... "

Sometimes while working I find a subproblem that is isolated from the original problem domain, for example token renewal in an RTR authentication system. I take note of what I've been working on, clear my head of the broader problem write an exact specification of the subproblem. Then I code to that specification. The result is usually a self-contained open-source module which continues to improve my pace of work for years to come.

My one skill in life is wondering why my widgets aren't displaying.

note to self: Use "Get Player Controller", or all your UI will fucking break.

Note to self:
Ctrl+A followed by Ctrl+V to replace text with the clipboard contents does not work if highlighting text copies it.
I just spent 20 minutes copy-pasting stuff before realizing nothing had changed…

Note to self:
Variadic C++ templates combined with obfuscated combinations of stl containers put you on the right path to be a "compiler message decryption" archmage.
Especially when you use MSCV...

Note to self: Don't leave your ubuntu laptop sleeping on battery life.

1234F:

😭😭😭

Darn xml config file for a dll wouldn't load.

1) Searching Stackoverflow which says that only configs for exe files are loaded. Problem found and time to send bug report? Nah, better check source code first.

2) Downloading and reading the source for the dll. Nope, dll should explicitly load config file and read settings. Time to send problem report to author? Nah, better to test in greater isolation first.

3) Setting up isolated test. About to copy the LibName.dll.config.xml and WHAT? Note to self: You half witted twat, the file contents is XML, the bloody file extension isn't!

Now apply this sort of typo error to program code, and you will see why I use statically typed languages.

Note to self: debugduck.py. just a program that displays a duck while I'm programming XD

Note to self: always push the higher up managers to think about the technicalities

Doesn't want to use VCS and wants to deliver a project to client.
Note to self: Don't help friends in their misadventures