Today was hell on earth as for user support. Phone going non stop, tickets coming in faster than we were able to process.

At the end of the day I had to make a symlink for a customer which is fine. But, the day was so busy that I just couldn't focus anymore.
I've made 1K+ symlinks in my life probably but I couldn't remember if the source or destination comes first with a symlink.... The day has been hell and I just couldn't bring up a single second of focus anymore..

Fuck it, I'll do it tomorrow. I know I can do this but I don't trust myself with this right now in case of a huge webshop (swap the source/destination: webshop gone).

I think I'll thank myself for this tomorrow.

Me at work right now.

After using Linux every day for 3 years, today I learned that the first parameter to ln is relative to the second one and not to the current location.

I hate it that I'm still forced to use Ubuntu 16.04 and can't upgrade to bionic beaver.tried it on vm (for testing)loved new features and default gnome interface but even after switching to xorg most of my tool were still not running properly or crashing, most important factor is that there is still no official cuda support and installing gcc g++ 6 and symlinks are nerve racking. On top of that upgrading to 18.04 LTS on my main machine will leave me with broken packages and dependencies.

p.s. for people who are going to reply saying that these issue can be solved. Please try updating your work machine and spend hours fix these issues

Take a few seconds to reflect on the insane amount of human time and effort that goes into making development bearable or just possible on Windows.

A few examples: bash (MINGW & MSYS), make, symlinks, docker (docker-toolbox, WSL), Apache (W/X/LAMP)

The website was down.

She called me 5 or 6 times and mailed me twice that amount, asking how long it would take to get back up. Each time I answered that I did not know, that it was my job to figure out what was wrong, and that solving a problem doesn't have a fixed duration.

What I thought was that the updates on her emotional state of regret were not helping me to resolve the issue and cost me time. Why do people inflate the price of things they are going to pay for by asking for what cannot be known?

In the end it was just a shitty shared host having flipped some switches. It was their own damn fault for picking it over our recommended provider that keeps us informed about all them switches. Such as disallowing SymLinks overnight.

How to tell if someone had never developed before and never looked at Linux before: I'm not familiar with symlinks.

Goddamn, Windows' idea of symlinks is completely broken. It's like they faked it at the UI level, but if your build process wants to copy the file? Too bad, it's not real so you can't copy it.

Has anyone ever tried making symlinks on windows?

OH MY GOD. How can someone fuckup something so simple. It really pisses me off.

I mean. I am obliged to `git submodule add` because i can't `ln -s`

Boss uses symlinks for packages in go. He checked in changes for several services and then left for vacations.

Writing a library is so much nicer than writing an app. You can concentrate on the core thing you want to achieve and need to handle just a few files.

And you can still test it live even if it's a node module: just symlink it into the node_modules folder of your app.

So, I just (few hours ago)made a new variable that's either brilliant or innately flawed... not sure yet. It's an oddly unique var...

__bs__

So far I only made it in python and windows env (i script like the methodology of css).

I bet you're wondering how I've defined __bs__ and the practicality of it.
__bs__ is derived from a calculated level of bullshit that annoys me to tolerate, maintain, etc. as well as things that tend to throw nonsensical errors, py crap like changing my strings to ints at seemingly random times/events/cosmic alignments/etc or other things that have a history of pulling some bs, for known or unknown reasons.

How/why did this come about now?

Well I was updating some symlinks and scripts(ps1 and bat) cuz my hdd is so close to death I'm wondering if hdd ghosts exist as it's somehow still working (even ostream could tell it should be dead, by the sound alone).

A nonsense bug with powershell allowing itself to start/run custom ps1scripts with the originating command coming from a specific batch script, which worked fine before and nothing directly connected to it has changed.

I got annoyed so took an ironic break from it to work on python crap. Python has an innately high level of bs so i did need to add some extra calculations when defining if a py script or function is actually __bs__ or just py.

The current flavour of py bs was the datetime* module... making all of my scripts using datetime have matching import statements to avoid more bs.

I've kept a log of general bs per project/use case. It's more like a warning list... like when ive spent hours debugging something by it's traceback, meticulous... to eventually find out it had absolutely nothing to do with the exception listed. Also logged aliases i created, things that break or go boom if used in certain ways, packages that ive edited, etc.

The issue with my previous logging is that it's a log... id need to read it before doing anything, no matter how quick/simple it should be, or im bound to get annoyed with... bs.

So far i have it set to alert if __bs__ is above a certain int when i open something to edit. I can also check __bs__ fot what's causing the bs. I plan to turn it into a warning and recording system for how much bs i deal with and have historical data of personal performance vs bs tolerance. There's a few other applications i think ill want to use it for, assume it's not bs itself.

*in case you prefer sanity and haven't dealt with py and datetime enough, here's the jist:
If you were to search any major forum like StackOverflow for datetime use in py, youd find things like datetime.datetime.now() and datetime.now() both used, to get the same returned value. You'll also find tons of posts for help and trying to report 'bugs', way more than average. This is because the datetime package has a name conflict... with itself. It may have been a bug several years ago, but it beeb explicitly defined as intentional since.

@microsoft/rush is just Microsoft finding out about symlinks and heavily overusing them now.