My boss has added devRant to our company wiki :)

Its under the social tag ;)

Co-worker: "Should we keep this server up and running?"
Me: "Hmmm…"
C: "Do we have any other uses for it than the dedicated wiki?"
M: "Not really, and maybe it's time to move to the centralised platform Corporate™ introduced. Have we checked if anyone is using the server?"
C: "Good point, let me see…"
C: "… oh it's been down for last two weeks since the power outage."
M: "I think that answers the question. Let's leave it like this for a month more and if no one complains we can announce it dead"

No, I wont help you solve your stupid problem. If you are not able to read the wiki or the man pages - Arch linux is not for you.

You have only proven that you are stupid enough to listen to other people who likes to brag how good the are, but actually do not know shit.

While I'm in pause time with my colleagues and reading on wiki how, the boss comes to me and asks:
Boss: what are you reading?
Me: how to Quit Your Job Graciously 😊
Boss: 😐

The next day the boss offered me a +€0,50 p/hour.

"Arch Linux is actually not that difficult".

I ssh'ed into my home server yesterday.

I was greeted by a message from an ext3 disk about needing fsck. Fine, "I haven't been in here for a while, might as well do some maintenance". fsck /dev/sda6, let's go!

This nicely "repaired" the sshd service (i.e. cleared the sectors), I cursed at myself for pressing enter at "repair (y)" right before the connection broke.

So I connected a display and keyboard... ok so let's just pacman -Sy sshd or whatever. We can do this! Just check the wiki, shouldn't be that hard!

Wait... pacman has not run since 2010? WAIT IT'S ACTUAL UPTIME IS 9 YEARS??? I guess we know why I'm a DB admin and not devops...

Hmm all the mirrors give timeouts? Oh. The i686 processor architecture isn't even supported anymore...?

4 hours, 11 glasses of cognac, 73 Arch32 wiki/forum pages, 2 attempts at compiling glibc, and 4 kernel panics later: "I think I'll buy a new server".

😭😨😰🥴😭😭

The exact moment when I understood what programming actually was.

I was getting hard times at my 3rd college grade, trying to implement the recursive sudoku solver in python. Teacher spent a lot of time trying to explain me things like referential transparency, recursion and returning the new value instead of modifying the old one and everything related. I just couldn't get it.

I was one of the least productive students, i couldn't even understand merge sort.

I was struggling with for loops and indexes, and then suddenly something clicked in my head, like someone flipped a switch, and i understood everything i was explained, all at once. It was like enlightenment, like pure magic.

I had sudoku solver implemented by the end of the lecture. Linked list, hash map, sets, social graphs, i got all of these implemented later, it wasn't a problem anymore. I later got an A for my diploma.

Thank you @dementiy, you were the reason for my career to blast off.

Trying to learn X on wiki. Immediatelly learn that you suck at everything and need to research more about Y, Z to understand the basic meaning of X.
And that goes on recursivelly.

Literally any modern website

I read somewhere that you can go to Adolf Hitler Wikipedia page from any other wiki page within 5 clicks!

Here's what I tried.

List of Programming Languages -> Lisp -> Massachusetts Institute of Technology -> World War II -> Adolf Hitler

So yesterday a friend of mine closed a ticket which has been open for around two years: "Automatically publish job offers in our internal wiki."

This was the conversation between him and HR.
- Friend: They're all on our website. Why should they be in our wiki too?
- HR: So that our employees can see them and recruit people for us.
- Friend: How about I just put the link in our wiki?
- HR: No, no links. They should all just be in our wiki.
- Friend: *<iframe src="website"></iframe>*

Now HR and everyone else is happy.

Today I learned Slovakia is in fact a version control system, not country.

Things you find on Wikipedia these days.. 🤔

I love it

!rant

After reading the wiki page over and over, I was finally able to implement Dijkstra's algorithm 😃

The best way to waste a weekend

And you thought your markdown based Wiki was going to change the company...

Do you know what is world needs?

Good fucking tutorials for all programming languages.

Every time I want to learn a language it's a fucking mess. Tutorial here, tutorial there. Read the docs, it's fucking outdated. This person using this design, that person using that.

I am so tired of this shit.

also, for a simple example most website uses some complex architecture, something they think is the next thing.

Even searching for a simple QT singleton pattern gives me a webpage from QT Wiki which uses templates, typedefs and this shits to just show a FUCKING EXAMPLE OF THREAD SAFE SINGLETON.

I really wish there's was a greater platform for this. A platform that follows some certain standard rules for tutorials.

Official Release of Wikipedia Bot is Here

How to Use: @wiki <Query>

Runs on cron job, every minute.

If there is literally no Wikipedia page for query, still gets a relevant result.

Demo in Comments.

So what do you guys do when you're bored?
My friends : Browse Facebook, Twitter, Instagram, read some blogs maybe..

Me : Browse through the Arch Linux wiki... I mean,... you know Twitter, Reddit, the usual..

Adding big pile of 40+ megabytes pictures to git repo.

Our boss has a camera in the office to "monitor" us, the developers.
He tries to monitor our movements and record the things we say.

I'm curious, do other people do this?
I find it annoying.

Friend: " How many layers of madlad are you on?"

Me: "uhm... I made a Proot of ubuntu for a ubuntu machine once"

Friend: Watch me

[Sees him use Arch Wiki for his Debian problems]

Update on my previous kernel rant, I finally compiled it down to just 2.9GB! included all the needed modules and I am also able to boot off of it!

Great news is, that sound both on speakers and also through headphones work, bad news is, that there's some overlayed buzz/distortion, the playback is higher pitched and chrome for some reason plays videos "normally" if you set it to 0.5 speed, else the video get sped up in the "normal" speed setting, well fuck me, but atleast I am closer, also as always thanks to arch wiki, that has tons of resources.

It might be some of the quick hacks that causes this, that I used in the past to make sound work through an external usb card atleast, so might be worth it just reinstalling it all.

*gets annoyed by how vi command in Ubuntu WSL points to vim*
To be clear, that's due to update-alternatives in Ubuntu, not WSL specifically.
*le me ducking how to install vi instead, because vim in WSL has scrolling issues*

"install vi ubuntu"
> How do I install and get started with vim/vi? - Ask Ubuntu
> apt - Vim installation in Ubuntu 14.04 - Ask Ubuntu
> Ubuntu Linux: Install vim Text Editor - nixCraft

-.- I'm not looking for vim ffs, I already have that installed.

"install vi ubuntu -vim"
> Same fucking results

"!g install vi ubuntu -vim"
> Installing the VI Perl Toolkit from Source Code—Linux - VMware
> FedoraDirectoryServerClientHowto - Community Help Wiki - Ubuntu …
> Learn How To Use Linux vi Editor And Its Commands - LinOxide

Oh for fuck's sake!!!
So here's my question because apparently search engines clearly can't point me to it, and Ubuntu doesn't seem to have vi as "vi" in their repositories either. Do our Canonical overlords allow people to actually make /usr/bin/vi actually be fucking vi?

PSA.

I have established "Depressed Lonely Maggot" Club. Our symbol will be an ugly crying maggot.

You are invited :3

I don't know what non-German people do without ubuntuusers.de.
Without this wiki, I probably would know nothing about Linux today. I would have never been introduced to it as a child, would never been able to learn that much, play around with desktop Ubuntu, Raspberry Pis, administrate own servers...
So, thank you, ubuntuusers.de, for helping little Benedikt with Ubuntu in his mother tongue, and making me the Linux enthusiast I am today!

A wiki repository for all mental wellness resources around the globe.

When in internship you have to read 150000 lines of code to make changes and the code does not have any comments, no indentation, no documentation, no wiki. You'll be like fuck this shit. I'm outta here.

css quick maffs

so, you want to make a css gradient from a certain color into transparent. The logical way would be doing it like this:

linear-gradient(#112233, transparent)

however, this will cause a blurred black stripe to appear in safari. This is due to safari-specific algorithms (that also make it the quickest browser, especially on arm-powered macs).

stackoverflow and other boubas will suggest doing this:

linear-gradient(#112233, rgba(255, 255, 255, 0))

this is better, but instead of a black stripe, a half-transparent white stripe will appear.

To finally make this gradient render consistently across different browsers, do this:

linear-gradient(#112233, #11223300)

Now, you're only changing alpha. See, CSS is a declarative language, so you should be telling it EXACTLY what you want to achieve. You don't want to change one color into another (in that case, "#112233" into "transparent", yes, they are distinct colors that are totally different. CSS doesn't treat "transparent" in some special way like we do) but to only change the alpha channel of #112233.

Feel free to use rgba notation if you want to support older browsers:

linear-gradient(rgba(11, 12, 13, 1), rgba(11, 12, 13, 0))

aight bye

When I told someone to read the docco+wiki and ask me if there were problems, for them to come back every five mins to tell me "so, how does this all work?"

I wrote the wiki and it was A-Z. There's nothing I knew about the product that wasn't in the wiki.

It took me so much self-control to not bash his head into my monitor.

1) Read the wiki on git. I probably have enough shorthands and test methods that you won't need much other shit to debug issues.

2) when debugging, remember that if it is there, there's a good reason why I put it there.

3) commented-out code is probably useful for maintenance. I left it there for a good reason. 😛

4) chances are whatever I wrote, was the state of the art at the time I wrote it. There might be better ways to do it now tho.

5) I always work modular. First, understand the structure. (probably also documented on wiki) DO NOT fuck up the structure. If you change it, you document it.

6) If you feel I wrote shit, it's probably because management annoyed the living shit out of me. Pun intended.

7) Your confusion is normal. I don't do dumb shit.

I changed IP address of the domain A record to point to his new site. Told him it could take a day to propagate, but usually fine in a few hours. 2 hours later... "Microsoft is pointing to new site but Google isn't". I have to make some assumptions here, who else calls a browser by its fucking parent company, that is if he is talking about that or search engines. Anyway just sent him my favourite wiki link on how to clear browser cache and hopefully he will fuck off indefinitely.

Sometimes I get distracted because of a very technical joke that I don't get initially, but am determined to understand.

4,000 Wikipedia articles later, I understand the joke and now know the history of the pushpin (or some other off the rails object)

I want to get every contributor of arch wiki and kiss you on the cheek. EVERY SINGLE ONE.

When some random Assembly code I got off the OSDev Wiki actually booted on real hardware. This is where I'm meant to be.

Bravo Wiki, bravo

Tor
Parrot OS
The Hidden Wiki

Don't get me wrong, Dart is a darling. But also at the same time is like that one time you thought you found a good band and end up reading their wiki and one of the members turns out to be a wife beater.

Feels so good at the beginning and you feel you can do anything until you see the shortcomings and feel weird about committing time to it.

Dear IT troll: I am not some idiot user. I FUCKING WRITE SOFTWARE! I actually CREATE CAPABILITY! I don't create "content", I'm not some fucking suit that pumps out PowerPoint/Excel/Email all day long. I don't need to be handed a consumers screwdriver, hammer, and wrench set. I need to be able to set up the technological equivalent of MY OWN FUCKING FORGE AND ANVIL! Do you get it? Do you understand me? Give me administrator access and go the fuck away. While you're at it, please quarantine this pile of silicon onto a limited access network if it makes you feel better. My development system doesn't need to connect to the wealth of bullshit in your precious little dumbed down corporate Wiki-wannabe Sharepoint system. Keep my creative space away from Test and Prod networks while you're at it. Just give me the goddamed tools I need to do my work and fuck off!

Sony.

I don’t *hate* them, but I had really high hopes for Xperia smartphones back then, five years ago.

So I saved up and bought one. That’s what I got:
1. It was getting slower and slower
2. Micro usb broke just months after I got the smartphone
3. Sticky fragile screen with absolutely no oleophobic coating
4. NO UPDATES TO KITKAT AND LOLLIPOP! They just left us behind!

5. The main reason.

I catch moments with my camera. For me, camera is a vital feature, the most significant factor.

I once needed it really urgent and it just said “Camera is unavailable”. And that’s all. Camera is gone forever, broken. Factory reset haven’t fixed it.

You, alongside with Meizu, turned me away from android irreversibly and forever. When I heard about no update, I literally felt abused. Just like a girl whom random fuckboy made a proposal to, fucked and then left just months later.

With that level of customer support, basic respect to me as a user and buyer and that level of quality control, fuck you and your sloppy bricks you call smartphones. Maybe things are changing now, but I don’t care anymore and hardly ever will.

P.S. it heats up as hell, fucking pocket stove

So after my hosting my first project and announcing it on devrant, the users pointed out the many security faults and places where the code can be exploited ( thank you so much ). So I started my research on security ( im 99% self-taught ). The first thing I landed across is the code vulnerabilities which the I can fix then the vulnerabilities of the language itself and then binary code to overrun whatever the language it is. Well, the topic gets broader and broader. If I click on a link named xxx vulnerabilities oh god that is a whole new collection of hundeds of wiki like pages. I feel like I'm lost and here I need some real help

When you click on the github wiki of the API you wanted to use and it shows you the "Create the first page" banner....

Guess I'll have to find another API with proper fucking documentation.

A 'senior' dev just questioned us (by question, I mean scold) when I suggest writing some additional information regarding db patching scheme of our project on our Wiki, just thought it might be useful for other possibly new devs later.

Apparently that would be 'spoon- feeding' them and it is totally NOT GOOD.

Smh.

senior: read the fucking development setup wiki

<senior proceeds to have problems>

somebody else tells them to read the fucking wiki

oh how the turn tables

IT description of remote access tool on IT wiki page:
"Support for latest Mac and Windows release"

Also same page:
"macOS Mojave is not yet supported (...) Please do not upgraded until instructed"

No comments...

It took me like 3 hours to install stupid mariadb on my fucking arch. From the service not beeing able to start over not finding the correct base dir to permission problems in the data dir.
Well, after reading the wiki it was actually pretty easy (only minor problems) ...

Today I learned two things:
- I must be fucking dumb
- Reading the manual instead of guessing helps a lot when installing stuff on linux

Eyyyy, finished installing and it even looks like I didn't fuck anything up.
Will reboot now to see that it's actually installed and works.
Was less complicated than the wiki made it look.

month off on vacation

come back to work and try to remember shit

struggle to decipher/remember public wiki documents you wrote prior to vacation

ugh

Confluence WYSIWYG editor for tables on wiki pages. Forget about git and GitHub idiosyncrasies, "at the end of the day" project documentation in Confluence and Jira is the real challenge.

You know how a normal developer will start writing a program, and then take the big pieces and split/refactor it; move hard coded things into functions that take arguments, and cleaning up along the way?

Our manager makes a tons of empty files, and empty directories, with how he thinks he wants to build something, and checks them all in. Tons of .gitkeep files in empty directories, blank Jenkinsfile, Dockerfile that doesn't build.

When he makes wiki documentation, there are tons of subsections, all of which are links to pages with "TODO" in them.

Dear god stop it you asshat! Stop making tons of empty files and pages. Write the thing in one chunk and then split it as needed like someone who actually knows how to engineer software!

Tools are made for various audiences. Git is the de-facto standard for version management, so it can be complicated because people will still learn it (they more or less have to). Editors aren't as standard and they are to be used from the minute you start learning, so they have to at least be usable without a course or a handbook. I prefer the first type of tool because to use something really good I don't mind reading a book. Programming languages can fall in either category; Python was meant to be used by laics and is therefore very simple, sacrificing a lot for the sake of simplicity. Rust isn't meant to be used by anyone who isn't trained, and it comes with a great book that explains all the most important gotchas. Haskell doesn't have an official book AFAIK, but it has the best wiki I've ever seen in a programming language.

We've been using private GitHub repos as a distribution method for our personal npm packages at work for years.

I finally got sick of it and did the work to publish them to artifactory yesterday. Today, I worked out the remaining kinks, fixed the CI builds, and wrote a wiki page explaining the change with step by step migration instructions and sent it around to the rest of the devs. And it's working great!

I feel simultaneously like a hero for finally getting this fixed and an idiot for putting up with it for so long.

Also thankful for my devops friend who helped a bunch.

Discretion is advised

I had a bizarre nightmare where I wake up tied, my head inside the glass cube, my eyelids stitched to my eyebrows so I can’t close my eyes, and then @rutee07 pours drain cleaner into that cube, through immense pain I feel my eyes turning cloudy and skin on my face turning into soap, meanwhile drain cleaner goes down my throat

And then I woke up. This dream was the reason behind my dice game liquid PH rant I posted not much earlier.

When you refer to the Arch wiki and your files are different to what step one is, so you just wing it.

Seen some screenshots of Notion. It's like airtable meets wiki, without dealing with markup.
It's very clean, and their use of templates is very intuitive, as is creating new templates.

Their offerings, even for new users, are also very generous.

Anyone used notion and if so, what did you think of it?

You know that moment, when you look for something on wikipedia, and after few hiperlinks you are reading about influence of penguins on Mars' day length or othen nonsense?

Just happened to me like 4th time when reading Django documentation. It is so well written and easy to understand, that I just click and click and want to go deeper, and then realise I have to read what I need, because I never ever got to it in the first place.

Gotta love the people who make such docs. I never could, and prbly will.

float: center;

what wiki or frameworks are there for writing a documentation, you consider good :)

The best motivational comment

I posted a rant in which I mentioned that "few" developers who don't want other to progress and are present to show off at every platform....
Got a comment, which I want to share...
Thanks to @MrCush

Ya, most of them tend to stalk the stack overflow and Arch Linux communities. On stack overflow they tend to refresh their browser nonstop to see who their next victim is on a new question and then spend an abnormal amount of time searching the site for a similar question and then downvote you and report as a duplicate. “Umm ya, the question you linked is similar to mine. I found that one as well but unfortunately it wasn’t in the same environment with the same conditions that I raised and didn’t help me. Oh btw, he posted that back in 2002 and HEY LOOK, he got reported for a duplicate as well. Seems like you reported him as well.” 
The issues of arrogance and being unhelpful on that site are so vast that nobody else that registers can get enough points to be able to be allowed to answer someone else’s question so you never get any new blood.

Arch Linux “elites” like to answer your question with a link that you’ve already been to as they always link the same site. “Dude! There’s a wiki for a fucking reason. Did you read this page?”
Yes I did read that page and it was helpful to a degree but since I’m absolutely new to Arch, a lot of the information on the wiki is a bit too descriptive and over my head. Not to mention every paragraph links you to another wiki page which then links you to another and so on that I have no idea where I left off....
“Dude! If you don’t understand everything on the wiki then you shouldn’t be using Arch Linux man! Gtfo scrub.”
Took me a long time to get comfortable with Arch because of these assholes. You got to start somewhere and doing is the best way to learn.
Reading the wiki on how to install Arch now seems so simple to me because I know what to ignore and what is required but back when I first started it was absolutely confusing.

full form of git, from wiki xD :

Stop recommending arch
Start recommending arch wiki

These nerds spend so much stuff in their system that every weird shit and behaviour is there

You wanna know if you are a real developer?
Google "string" and see if you get as first result underwear or not.
Try "DD" and see if you get again some underwear results or a ubuntu wiki article about "the great data destroyer" ;)

Best? Clojure docs. They have disqus-like thing under every function description where anyone can submit their usage example. One example times forty submissions equals forty examples!

Also w3c specs, nuff said.

Worst? GunJS. Multiple websites that look like each other plus GitHub wiki all with the same content but idk which one should I use, also there is no complete source, you have to look up everywhere. Also NextJS, they’re too busy pitching to investors, there is no way of contacting them, you’re in your own if you choose nextjs, that’s why I banned it everywhere I have the power to ban things

Last weak I tried to use Linux Arch on my VM. The only Linux distribution I'm used to is Ubuntu and the fist time I launched Arch I completely forgot that it was " do it yourself ". And that the ISO isn't actually a fancy installer like the Ubuntu one.

So I started following a guide and found out that the arch wiki is actually the way to go.

I searched for 1 hour how to change the keyboard to swiss-french which was actually pretty simple.

After that exhausting research that made me realise how ignorant I am with UNIX universe, I finally tried to install the thing.

When I was done installing, it didn't want to boot after I restarted. I got stuck at the 'Booting...' screen. After a few tries I lost all my energy and motivation.

Tl;dr: Tried Arch Linux, realised I had no idea, gave up after a few tries

Postman App logo seems like Michael Jackson doing his famous Anti Gravity Lean

Leaving the company in 9 days (!!!)
Any suggestions for the last week?
Any ideas for a leaving session?
I updated the Wiki and documented everything.
I did the missions no one wants to do and a lot of dev tasks.
What else can I leave behind for the team?

Spends 9 months on the side developing a library for analysis of a specific programming language. No help, entirely my own work. There's various tools built upon this library. Incorporates project management, an effective build system capable of parallel and distributed builds, a packaging system...

Beta release the library. Wait four months. Ask the community for who's been using it so I can get feedback and other comments. Majority of the comments follow a specific pattern.

"You don't support X, how dare you!?"

One, this is free software, pay me if you want specific things.
Two, I'm the only developer of a project usually undertaken by a small team.
Three, yes it does you fucking invalid... Every fucking time someone claims it doesn't support some feature, it's something I've already written and validated. I swear to fucking God users can't find something themselves and instead of checking the Wiki or asking for help, they blindly assume they can't make mistakes and it must be my defect.

Writing documentation is one of those tasks that most developers don't like doing. Especially when it comes to writing in say a Word/PDF file, an online wiki, or Confluence. It's time consuming and a pain in the ass.

But even if you don't like it, at least write comments in your source code! I hate having to keep writing "Write the PHPDocs for this class/function" in every pull request that I review. It's wasting my time writing such comments when it's such a basic thing to do when writing source code.

So last night I ran out of space on my root partition, apparently 30GB isn't enough for `/` besides `/home` and `/data` because both `/var` and `/usr` used around 14GB each so I decided to create partitions for them, had 500GB unallocated disk space on my SSD for if I wanted to install windows on my machine besides Arch Linux.

I edited the fstab file and sure enough, the partitions were mounted on boot, everything went fine. Then U realised the data wasn't actually removed from the first partition so I decided to mount the drive again and remove the files, the system still worked fine.

Untill I rebooted. Apparently the bit scripts require files in the`/usr` folder which wasn't mounted at boot, but right after. F*ck, system won't boot and now I'm in a recovery shell in busybox. After googling and reading the arch wiki I noticed a small message saying what you should do if you want to have `/usr` on another partition. I didn't do any of that.

After a couple of hours and a lot of reboots and chroots from a live USB to the broken installation it was fixed without losing any data! I did learn to read the manual or wiki to see any specifics when using more partitions. 😂

So I just spent all morning struggling setting up a project and getting it to run. My colleague sent me a screenshot of the documentation wiki, but didn't give the link.

*4 hours later looks at email for the Nth time*

Wait he did... that's not a wiki, that's Readme.md... this is in the repo link right above it!

I didn't need to checkout the repo so didn't open it...

Got my first job after graduation for my Java skills. I was told to learn Hybris from its wiki. I gave it my best and worked very hard.

Two months later, manager tells me to forget about Hybris and puts me in a team with two idiots in a new . Net project.

Worked non stop and and single-handedly brought the new project to completion with . Net, bootstrap, jQuery etc.

Again the manager tells me that they need people in integration team and i have to learn Apigee and Informatica.

The thing i regret most is leaving my beautiful code in the hands of those two idiots that will definitely shit all over it.

In case you're wondering, I don't work for a start up, my company is worth US$ 99.64 billion.

Whenever I hear "this <person> is going to work on <project>" I edit my "bus factor of 1" wiki page.

Teams work on projects. People work on teams.

It was the worst local Hackathon. It's not even a Hackathon either, where the whole event spanned over 2 months.

It was a group entry with me and 4 teammates. Each of them did contribute:

Guy A: criticizes what is built and designed
Guy B: offered financial tips on how to make this thing feasible
Guy C: did UI but in graphics. No CSS file, just bits of graphical elements.
Guy D: family commitments

And then there's me, writing documentation, built the entire project, wiki, drove the project, prepared the presentation slides, tests the framework, unit tests, stuck with stupid problems like SSL, localhost, Google Maps Key and the likes.

And we didn't even win, let alone launch this thing, whatever it is, to anywhere. Never doing group projects again.

I'm flying solo for now

So we're using Jira Wiki for all the documentation related work. It's hell rich with features as they describe. But for me easiest way is to write doc on markdown and then copy paste on Wiki. Highlights code, format tables and aligns paras perfectly.

I've spent months with like 200ms+ ping and I just read the Arch wiki for my network card for the first time. Turns out its a common issue that is fixed with one dam kernel parameter. Now my ping is <30ms. Linux just be like that ig.

$this->newTab->devRant->postRant();

When you use CMD+Space on your Mac to open an application, and it looks it up on Wikipedia instead.

Literally just did this. I went to open Synergy(While typing a different post on dev rant) and instead it opened the wiki link for "Synergy"

ok I give up trying to make a screensaver for Linux

I don't even have anything to rant about

just everything I tried didn't work and nothing makes sense

I'm gonna find somewhere to bury my woes

this is so stupid, too. because I can just query the system if it's idle, run my app, and then ask my app to exit if there's any user input. but instead I'm trying to integrate it with the existing screensaver software. which evidently never runs my application for God knows what reason. and I'm tired of reading 100 pages hunting for the answer. where's my arch wiki page for how to make a screensaver =[

//long rant ahead!

I need to plan a Wiki with SharePoint for not connected Sites.
Im now in dispute with my CoWorker since 3 Months, this is how the conversation goes. My two bosses are involved in this and also unhappy about SharePoint.

[C refers to CoWorker, M for me]
C: Hey, we finished SharePoint with Selfservice Storage Rooms. They even have a Wiki.

M: Okay cool, will check it out

C: Well we need to also plan the Wiki inside, I already asked our Department Head and he agreed, that you will be the one.

M: Okkkkaaayy, normaly it's your job to do such things, but welp, I will look into it, if we can work with it.

(2 Weeks pass)
M: I checked SharePoint out and tested everything. The Wiki is a Nogo, we need a other solution or programm for ourself a Wiki Integration/Engine. Did you maybe check out Confluence? It has also a SharePoint integration plugin.

C: We wont do Confluence, too expensive (already overspent the budget for SharePoint in six digits 🤬). Also we wont add to SharePoint Custom Code, it needs to stay standard.

M: Thats impossible, SharePoint Wiki is shit and also handels sites just like documents, no brain behind! Also you overspent the Budget and now it's my Problem?!

C: You need to do the best out of it.

(3 weeks passes and we get a meeting with the department heads)

M: Alright I made a UseCase and documented where the essential flaws are in SharePoint Wiki and why we cant use it.

Boss: Ok if it's impossible to use, then we will stay on our Fileserver for Documents and wont use SharePoint.

M: Thats not my Point, my statement is, as status today, SharePoint Wiki is not the right solution, code or buy software to it.

Boss: We will do a Prove of Concept, if it doesnt work then we will aboard it.

M: Well it is only some missing essentials, like hierarchy and Groups for the Pages, Example Confluence has this. If we could built in this features in SharePoint, everything would work out.

C: (angry) I told you that we wont use Confluence!

M: (calm) I said we need Features, not Confluence. Please mind the consent.

(3 weeks passes, and one more meating with bosses)

M: alright here again is a analyses, why already in Theory the current SharePoint Wiki wont work. It's already flawed in the core.

Boss: Yea SharePoint is crap, I checked out confluence and thats a real Wiki.

C: Well I dont know anything about Confluence and never looked at it. But if SharePoint is a fail we need the Proof of Concept.

M: Why do we need to do a Proof of Concept, when it already doesnt work in Theory! Thats nonsence and unlogical.

Next meeting will be in 4 weeks and I will give him the FUCKING PROOF OF CONCEPT. I will be a Bastard and build behind CoWorkers back a Confluence Wiki to show the Departmentheads how to built it right.

I hate CoWorker now, he makes a part of my loved Job a hell, I will goddamn cuk Coworker to space, that fucking Cukatron of lazyness and shit 🤬. I provide the Solutions and you just say no, how dafuq will the project advance, if you always say NO! Are you so unflexible and fixed on your Castle of Ignorancy!

I once worked on a project with 3 specification documents; a word document with numbered points describing every feature inadequately, a UI specification with mocked up screenshots in a badly-versioned wiki, and a user manual which had already been produced by an overzealous marketing department.

Of course they all contradicted each other :D

So my team started creating an in-house wiki for all information about our products, methods, scrum, documentation etc. From the beginning we had settled on doing everything in English instead of native language just in case we get a foreign student intern or simply a foreign employee... And now it looks to me that nobody but my team leader and I care about it: half of the documents are either fully native (especially from other part of the team who work on a different project, they have probably never gotten the memo of language choice to start with) or the documents are in some weird-ass combination of English-native which is even worse imo.
I really don't understand why my own team doesn't adhere to the decision though: we're all at least reasonably educated and our country focuses heavily on using English as second language so that should be no big barrier. And why would you want inconsistent documents/code?!
And this is not the first time people don't stick to what is decided for things like formats and language... Getting a bit tired of it tbh...

Imagine you decide to spend a few hours to contribute to an open-source project wiki/documentation that hasn't been updated in years, to actually make it useful for new users, and then the maintainers start expecting further modification and corrections from you before pulling the PR, like you work for them, instead of just fucking pulling it in and then editing what they want themselves. It's just another example of how stupid and nonsense the open-source community can be.

Am I the only one that keeps mistyping & mispronouncing Magneto when I mean Magento?

Can't count how many times I've scratched my head because I got search results pointing at Sabayon Linux's wiki when enquiring about it...

Was wondering what kind of workflow you use.
My team is currently a big unorganized chaos...
Our manager wants us to take the form of:
Feature idea -> Design -> Build -> Test -> Train (explain to users how to use it) -> Deploy

The `Train` step is something rather odd to me, as that would mean teaching every single employee how to use the product we're making.

Wouldn't it just be better to skip the `train` section (and maybe use some kind of wiki?) and try to make everything as clearly labeled and obvious as possible?

- Reading random Wikipedia pages (mostly history)
- Speedcubing

I look at the "Discover Repositories" sidebar every time I log into github. I've found some really cool stuff that way.

But I'm really confused as to why I keep getting typescript-related repositories there.

I've never created a ts repository
I've never made a pull request that had ts in it.
I've never created an issue in any ts repositories.
I've never even written a single line of ts.
The only reason I can think of is that I was browsing the official typescript language wiki for a few minutes...
A COUPLE WEEKS AGO
Yet sometimes, all 3 repos in the side bar have typescript in the title.

TL;DR: github, please stop pushing typescript on me.

Is there any alternatives to Atlassian's Confluence and Jira?

We used to use GitHub projects and wiki, but "the business" wanted a more formalised process and access controls on kanban boards and backlogs.

We started using Jira and Confluence last month, but Jira have been incredibly slow with a horrible interface also Everytime I create a new issue it feels like I'm wasting a lot of time compared to the time needed to setup an issue on GH and add it to a project board, plus the entire team is used to using markdown which doesn't work great on Jira.

I've looked for some alternative but I wonder what you are using out there!

One year ago I made a resolution to do one of two things: get serious about learning neural networks, or finish one of the side projects (markdown based wiki with some nifty features). Didn't do the first one, and got the second one to about 50%.

Not really happy as I did not complete any goal. Still some decent work was done and built an open source parser. So, I guess I am 50% happy.

What were your achievements this year? Did you achieve 100%?

When an internal wiki document you wrote for your personal reference not intended to be used as a guide, gets used as a guide.

Like I intentionally didn't write it well , with no details or explanations, it's what just happened to work for me, on my environment.

Who knows when and if this'll come back to bite us. Hopefully I don't get blamed.