Girl : I like dangerous men.
Me : I didn't run test cases while committing my changes last night.
Girl : my hero!

Me : *wakes up from the dream*

Don't be like jimmy... test before committing! 😋

Q: "Why isn't she committing to me?"
A: "Because you are in her .gitignore list"...

Naming a variable "dogFucker" in anger and accidentally committing it.

Fucking fuck fuck fucker fucking fuck

What a dumbass guy seriously. I have this colleague in my office who refuses to create a new branch because that will "ruin the single straight line". Are you seriously fucking kidding me??? The noobest guy ever doesnt know a third git command other than pulling and committing fucking nonsense. Why use git then? Just go back to creating zip files are maintain code. Fuck that guy too who hired him and now because of this fucking asshole I am not able to carry on my work.

Such so-called "developers" should be strapped to the back of a horse and the horse made to run on a gravel road for fuck's sake.. Fuck you man 🖕

So... I just remembered a story that's perfect for devrant.

My brother got into engineering in university, and during the second semester they had their introductory class to programming. They had weekly homeworks that the lecturer would check and give grades accordingly.

The factors that could influence the grading were: execution (meaning that the code would excecute as intended), efficiency and readabilty. The weeks passed and everyone was doing well, getting fairly good grades. Everyone was happy.

Until one day a random guy we'll call bob got the worst grade possible. Bob wasn't a bad student. He had over-the-average grades in all the weekly homeworks and even impressed the professor in some. Naturally, he was baffled when he saw his grade on the google spreadsheet. He was pretty sure his code ran well. He always tested it on different machines and OSs. So, at the end of the class, he went straight to the helper of the class, in a pretty imperative manner, to demand to know how the fuck he got that grade. It's impossible he got excecution, efficiency and readabilty, wrong. All three wrong? Impossible. Even the stupidiest kid in the class had some points on readabilty.

"Oh, so you are Bob. Huh?" said the helper in a laid-back attitude. "Come with me. Prof. X is waiting for you in his office."

This got Bob even more confused. As they approached the office, the courage he had in a first moment banished and gave way for nervousness and fear.

The helper nocks the door. "Prof., Bobs here"

As soon as Bob sits in the chair in front of Prof. X's, he knew something bad was coming.
"In all these years of teaching..." said Prof. X hesitantly. "In all these years of teaching I have not come even close to see something similar to what you've done. You should be ashamed of yourself." Needless to say, Bob was panicked.

"In all these years I have not seen such blatant mockery!" added the professor. "HOW THE FUCK DID YOU EVEN DARE TO SEND A HOMEWORK WITH SUCH VARIABLE NAMING" That's when Bob realised the huge mistake he made. "NEVER IN ALL THESE YEARS I HAVE SEEN SOMEONE NAME HIS VARIABLES *opens the file on his desktop *: PENIS, SHIT, FUCKSHIT, GAYFUCKING<insert Prof. X's name>MAN, GOATSE, VAGINAVAR, CUMFUNCTION, [...]" The list of obcenities went on and on. In each word, the professor hit the table harder than the last time.

Turns out Bob felt so in comfort with the ease of the course he decided to spice things up by using "funny naming conventions" while coding, and then tidying everything up before uploading the homework. This week he forgot, and fucked it big time.

So remember folks, always check your code before committing/giving it in/production. And always adhere to naming conventions.

A couple of weeks back, I met some of the kids from my old school. They had joined together to form a small team and were designing and deploying websites for local businesses.

Turns out that they were mailing each other and using Dropbox to manage the source code. This had been going on nearly for an year.

I spent a couple of hours showing them how to use git and gitlab. Basics on committing, pushing, pulling, branching and merging.

I will never forget the look on their faces! They had seen God and its name is Git.

- you don't like math
- you don't like study
- you don't read documentation
- you throw out the manual
- you like to punch a clock
- you dislike books and reading
- you don't ever work more than 8 hours
- you can't tolerate the occasional weekend work day
- you fold under pressure
- you aren't good at crunch time
- you can't do on-call without committing seppuku
- you don't have attention to detail
- you aren't interested in technology
- you're not good at explaining things
- you can't deal with change
- you're not excited by the prospect of extreme variety
- you don't have the ability to focus
- you can't deal with ego without resorting to violence
- you can't deal with someone calling your baby ugly
- you can't discriminate between fact and opinion

And many, many more

YOU ARE A FUCKING SOFTWARE DEVELOPER WITH AT LEAST A LITTLE TRAINING FOR THE LOVE OF GOD PLEASE STOP FUCKING UP THE GIT REPOSITORY BY COMMITTING THE GODDAMN NODE_MODULES

One devs commit messages always starts with "Committing changes..."

Oh rly?!

Committing is always a hard job. Whether it's Relationship or GitHub.

Committing at 860km/h as we make our way soaring through the sky towards Berlin!

Monday morning, went to the local grocery store to get myself some croissants and 2 bottles of wine.

Cashier: "Already at it in the morning, you sure about that?"

Me: "Long story short, I've got a Wi-Fi driver from Intel to debug and rewrite, and it's a fucking piece of shit.. can't go at it without hitting or preferably exceeding the Ballmer Peak... Also I'm awake since yesterday evening already."

Why even ask? Yeah I'm a fucking alcoholic, and guess why that is.. stupid nontechnical fucks, certified enganeers like that motherfucker at Intel who wrote this pile of garbage called ipw2200, and technology that can't be arsed to work properly on its own unless I build the fucking thing myself, just to name a few reasons.

You know what, fucking piece of shit from Intel, whoever it is? How about I let you choke on my dick while fucking hanging you with a sharp metal wire that's carrying 2kVAC from a microwave transformer, just to see whether I'd nut first, or you either choke, get electrocuted, or get your fucking throat slit first. Certificates aren't an excuse for committing this fucking pile of shit and calling it a fucking product!!

Now, it's time to dive into this giant stinking fucking turd I guess.. first glass of wine to get myself prepared for the shitstorm that's a giant 20k LoC C file with barely any comments, to look what the fuck causes this fucking pile of shit to disconnect and ask for WPA credentials after a while, despite having them stored.. and not reconnect after that, because why the fuck would you?!

Let the student use their own laptops. Even buy them one instead of having computers on site that no one uses for coding but only for some multiple choice tests and to browse Facebook.

Teach them 10 finger typing. (Don't be too strict and allow for personal preferences.)

Teach them text navigation and editing shortcuts. They should be able to scroll per page, jump to the beginning or end of the line or jump word by word. (I am not talking vi bindings or emacs magic.) And no, key repeat is an antifeature.

Teach them VCS before their first group assignment. Let's be honest, VCS means git nowadays. Yet teach them git != GitHub.

Teach git through the command line. They are allowed to use a gui once they aren't afraid to resolve a merge conflict or to rebase their feature branch against master. Just committing and pushing is not enough.

Teach them test-driven development ASAP. You can even give them assignments with a codebase of failing tests and their job is to make them pass in the beginning. Later require them to write tests themselves.

Don't teach the language, teach concepts. (No, if else and for loops aren't concepts you god-damn amateur! That's just syntax!)

When teaching object oriented programming, I'd smack you if do inane examples with vehicles, cars, bikes and a Mercedes Benz. Or animal, cat and dog for that matter. (I came from a self-taught imperative background. Those examples obfuscate more than they help.) Also, inheritance is overrated in oop teachings.

Functional programming concepts should be taught earlier as its concepts of avoiding side effects and pure functions can benefit even oop code bases. (Also great way to introduce testing, as pure functions take certain inputs and produce one output.)

Focus on one language in the beginning, it need not be Java, but don't confuse students with Java, Python and Ruby in their first year. (Bonus point if the language supports both oop and functional programming.)

And for the love of gawd: let them have a strictly typed language. Why would you teach with JavaScript!?

Use industry standards. Notepad, atom and eclipse might be open source and free; yet JetBrains community editions still best them.

For grades, don't your dare demand for them to write code on paper. (Pseudocode is fine.)

Don't let your students play compiler in their heads. It's not their job to know exactly what exception will be thrown by your contrived example. That's the compilers job to complain about. Rather teach them how to find solutions to these errors.

Teach them advanced google searches.

Teach them how to write a issue for a library on GitHub and similar sites.

Teach them how to ask a good stackoverflow question :>

So I spent 4-5 weeks explaining how shit the current code base was, implemented gulp tasks to lint js, CSS etc, written shed loads of coding standards and best practices to follow. At this point everyone was onboard with the changes and thought brilliant were going to start getting some good code coming out of this team.

I go on holiday for a week, come back and fucker has ignored the documentation disabled the linters in the gulp tasks and the code is back to square one SHIT!!

Plus everyone still committing to master!!!!

Why do I bother!!

Seen another dev push changes to a production server without even committing it to git.

Sometimes I should think twice before committing (Thank god there are no contributors beside me yet)

Sometimes I have really loose the will to live and find myself face palming multiple times.

I added live chat software a web frontend for a client. Very easy job that consisted of pasting in some embed code. The actual software is very good and has native ios/andriod apps - something specifically requested.

I got a call from my client about an hour ago, saying there is a "serious issue with the live chat".

My client stated the live chat won't work when his staff go home. He asked me what my solution to this was.

Saying "wtf" many times to myself I directed him to a settings within the chat software i.e. an "away mode" where an email is sent when no chat agents are available.

This apparently wasn't good enough and said I hadn't followed his brief of "adding life chat software to the website", which I had.

After a lengthy discussion I found the root of his frustration. He'd signed a contract with a client of his own, stating there would be 24/7 support via live chat on the website.

Obviously there a huge difference between adding a chat widget to a website and committing to having it manned 24/7 :)

After a further 10 minutes of trying push the blame on myself, the client insisted of having the chat software "appear" as someone was always online, even when they are not (people need to sleep ya know!).

Bu design, the chat software requires at least one agent be logged in before the chat status changes to "online" - why wouldn't it.

After a little while I was seriously wondering why I'm involved in this conversation. I jokingly stated: "Well you could always install Andriod/iOS app on your phone, login and permanently leave it running in background. You'd get lots of notifications, but the site would say the live is always online".

The latter was something I said in jest. To my surprise the client said he'd do that on his own phone going forwards. He actually thanked me for my "resourcefulness", lol.

I'm looking at the same dashboard now and there are 407 pending chat requests - his phone must literally be blowing up notifications :)

Commit Message Part2:
6528fff Code was clean until manager requested to fuck it up
241b35f Who knows WTF?!
4381a32 Argh! About to give up :(
c3bf1a9 more debug... who overwrote!
2d68d6d Fixed a bug cause Maciej said to
b112c1a This branch is so dirty, even your mom can't clean it.
bb456d4 Shit code!
4878b46 Copy-paste to fix previous copy-paste
e2c7e87 A fix I believe, not like I tested or anything
f56109f derpherp
e4b8f4c formatted all
3691208 I'm just a grunt. Don't blame me for this awful PoS.
0888b69 just checking if git is working properly...
62741aa I'm too old for this shit!
0735196 COMMIT ALL THE FILES!
09caccf I CAN HAZ PYTHON, I CAN HAZ INDENTS
1e1cda8 giggle.
ab70bde Fixed errors
934436d Now added delete for real
5f84e30 My bad
99baff8 CHRIS, WE WENT OVER THIS. C++ IO SUCKS.
953473d final commit.
f0c3b57 Just committing so I can go home
4e5ce4e yolo push
deb4e3b I CAN HAZ PYTHON, I CAN HAZ INDENTS
710c06a Commit committed....
3c45e67 it is hump day _^_
4487788 Committing in accordance with the prophecy.
bf86e7e This solves it.
4804f68 FONDLED THE CODE
051d42e REALLY FUCKING FIXED

Years ago, I was part of a project that went completely off the rails. A little context: we were a services company and we had local offices in cities all over the country. My team provided 2nd-level support which means we often had the PMs call us from those via an annoying Nextel radio.

I won’t go through the details but suffice it to say this project envolved one such branch going rogue and committing actual fraud, with criminal proceedings and all. People were on the edge, and the relationship with that branch was increasingly hostile. There was also an internal power struggle in the company between some directors at that point. In other words, a clusterfuck I’ll always cherish, if by cherish you mean hate hate hate. Anywho…

One time, there was a national holiday on a Thursday and we were going to make it a long weekend. As customary, I communicated with all the PMs about contigency plans. This PM then told us that we could not take Friday off because the customer wanted us to fly over there. We were supposed to be at the customer’s site early Friday morning. That meant we would have to fly Thrusday afternoon. I wasn’t happy.

It immediatly felt arbitrary too. As I said, the relationship was not good and we suspected he was just trying to cost us our days off. I knew enough of the customer to be fairly sure they would not have requested us that Friday. Why did the customer want us then? There was nothing yet on production and if it was just to show progress, surely we could move it to Monday. At worst, can’t we make it over the phone? No, no, no, he said. The customer was adamant that we be there on Friday. Sucked to be us.

So we flew over Thursday afternoon and on Friday morning we headed to the customer’s offices only to find it closed. They too had made it a long weekend and wouldn’t be back until Monday.

Normally I would be furious over the waste of time but to be honest, both I and my colleague smiled at that. It confirmed that the PM just tried to screw us and the customer have never asked for us. We headed back to the local office.

Before coming in, we both bought ourselves some icecream. My friend stayed in the little garden in front and I went in. The PM immediatly saw me and demanded to know why I wasn’t at the customer yet. I didn’t answer. Instead I grabbed the Nextel radio and headed back out with the PM following. I then sat down on the grass and called my director. Smiling and staring at the PM, I told him about the office being closed. The PM’s face froze when my director asked to talk to him.

We sat outside under the sun, enjoying our icecreams while the PM got shouted at. It was the best icecream I’ve ever had.

ABC

Always Be Committing!

People committing config files with connections strings pointing to their own machines.
Oh I'll just pull the latest changes... Why is all my data suddenly different??!? Fucking Gregg just checked in a connection string with "server=GREGGSPC".

The lead dev left the company two weeks ago. His last hurrah involved committing a bunch of complicated code into our API. The code he writes is generally overly coupled but this particular code is INSANE.
It is so coupled that the tests for it almost mock the entire application end to end. I only found this heap of garbage when the deployment tests were hung after I made a simple change in a totally unrelated file. THEY DIDNT FAIL. JEST GOT INTO A STATE WHERE IT CANT CONCLUDE AND HAS NO ERROR MESSAGES. We are taking about entirely different parts of the code. As far apart in the code as it can get. It took six hours of playing Sherlock Holmes to figure out what was breaking.

He got the most junior developer to approve the garbage PR as well.

Tabs or spaces?

A script that replaces <your project's style> with <your preference> whenever you pull and does the opposite just before committing.

Spread code not war

Not cleaning before committing.
You'll probably see lots of /*unused codes*/ in my projects.

That moment when you receive an email saying

"I got an error message that's says 'All hope is lost, delete everything'. Is this normal?"

and you have to explain that was an old printf that you put there for debugging purposes and forgot to remove it before committing...

GIT LOG VERSION 101
----------------
75fed18 pay no attention to the man behind the curtain
56772ff added security.
6374fdd needs more cow bell
6b27de9 Committing fixes in the dark, seriously, who killed my power!?
bffce8a giggle.
7e93977 Refactored configuration.
e66c495 pgsql is more strict, increase the hackiness up to 11
5690dd9 Revert "just testing, remember to revert"
daa84ba Still can't get this right...
097f164 this should fix it
367f271 GIT :/
f46d735 bump to 0.0.3-dev:wq
b893721 ¯\_(ツ)_/¯
24be0d9 ...
f014a0c ALL SORTS OF THINGS
e648b80 added super-widget 2.0.
3a71628 perfect...
e2a8cb1 Fucking templates.
b08e489 pgsql is more strict, increase the hackiness up to 11

You dense motherfuxker. There is a reason why we create a separate feature branch, put our code there, check the CI and THEN merge that to master. The whole reason of merge feature to master is that the CI DOES NOT GET FUCKED UP! You never keep committing your feature changes directly to master. THAT'S HOW YOU FUCK THE CI UP.

!rant
Damn github is da shit.
I'm sure all of those people who ranted about committing their passwords and keys will be happy
PS. I don't know if this is new but I'm happy either way :D

Story of WTF happened to my job

During my employment in (name censored) was stressful, They claimed I didn't complete my task on time which they constantly remove me from git and documentation(which have to follow their style of returning data), I kept emailing, slack, WhatsApp calls them, mostly and predictably got ghosted and blocked.

So How the fuck am I supposed to push my code or code without the documentation (I can actually, prevent refactoring every time, following the documentation is the good way to go.)

On the sprint review, they will complain about me not committing and pushing the code. (I did commit locally, but can't push, they removed me from the fucking repo) and not done.

Tried reasoning, telling the obvious reasons with them, doesn't work. They come out the second reason of me "NOT COMMUNICATING". Sometimes I can get to git merge from dev to my branch and get tonnes of fucked up code. I reviewed the code, and I can't tolerate it.

Lately, I overheard them mocking and cheering me about to get fired over a zoom meeting (I was in there, they forgot to remove me). Their conversation is about me being a coloniser, a jerk, betraying Chinese ancestors for being not Chinese enough.

I was like: "Why the fuck does their conversation sound like they are tucked in the Qin dynasty?"

Frequently I got labelled as unprofessional.

How is cussing about my ancestors, personal and life a professional behaviour?

Freelance project I was working on was deployed. Without my knowledge. At 11pm. Their in-house "tech guy" thought that the preview build i gave them was good enough for deployment. Massive bug, broke their api endpoints.
Got a call at 2 in the morning,asking for a fix. I told them how it was their fault and the App they deployed had TESTING written right on the main screen.
They promised additional payment to get me to fix it asap.
Went through the commit history (thank goodness their tech guy knew git, fuck him for committing on production though) and the crash reports.
Removed three lines. All became right with the world again. 😎

One time, I was working with an org that got a new senior executive from Microsoft. He decided we needed to throw out our application's java stack and replace it with SharePoint. The code error was committing anything other than my immediate resignation.

... late night coding session ...
... me, tired as hell committing last porting of changes ...
... git refuses my attempt for commit ...
....
$ git vommit -am ........

It's time to go sleep when you vomit instead of commit.

Ok fellow ranters. I've scoured the internet for hilarious and enraging stories of programmers being asked to either work for free, or for stock options, or to hack (crack) stuff, etc.

Here's my latest one. A friend who's obsessed with crypto came up with a "great" idea which was for me (of course) to build a landing page for a fake company to trick people into submitting their crypto wallet keys and all that. What started as a joke quickly turned into my friend getting mad at me for not wanting to actually make it lol. Like seriously wtf is with people. All the reasons not to do that scheme are plainly obvious!

Next. Some person who worked for a company I consult with pulled the generic. "I have this great app idea" line & proceeded to of course ask me to "not steal it" lol. It was just an app that would list gluten free restaurants... That's hardly even an idea!!

But what's fucked up about all this is my friend from the first story is so obsessed with becoming a "crypto millionaire" he actually resents me now for not
1. being obsessed with crypto
2. not committing cybercrime on his behalf

Anybody else have enraging stories about stuff people have asked you to do?

!rant

TL;DR: "Gather all resources before working on any project and committing to the client... & over smartness can be deadly"

Couldn't stop my laughter after reading this one.

A new vacuum salesman knocked at the door….

A lady opened it. Before she could speak... The salesman rushed into the living room and emptied a bag of cow dung on the carpet.

Salesman: - Madam, if I couldn't clean this up in the next 3 mins with my new powerful vacuum cleaner, I will EAT all this!!

Lady: Do you need Chili Sauce with that?

Salesman: - Why Madam?

Lady: - Because there's no electricity in the house...!!!

😂😂😂

So today, again, I discovered the importance of unitests.
I was solving this performance issue, in which we had a few update actions for multiple entities in mongo, but it took FOREVER to complete, even when I unified it into one bulkWrite command.
Since the unified write did improve performance slightly, and we wanted to move on, we decided to let this bug go.
So there I was committing my changes when I got a rejection from the pre-commit hook since I didn't have enough unitests coverage.
Ok, let's start writing some unitests.
Some unitests also needed to test the bulk write. So there I was comparing expected with actual result, and suddenly I got a huge facepalm.
Apparently some rogue for loop iterated all entities again for each entity that needed update. So instead of getting one update per entity, I got N identical update commands per each of the N entities 🤦‍♂️
Needless to say, fixing this fixed the performance bug entirely.
Thank you unitests and pre-commit hooks!

What are your feelings on committing your .gitignore file to the repo? I argue that you SHOULD commit the .gitignore file because you are much less likely to accidentally commit things you don't want.

My team lead just told me that he doesn't want the .gitignore file in the repo because it's not part of the build.

Well there were quite some teamwork fails concerning Git and build environments. I covered a few in my previous rants.

Basically I become a tiny bit of FUCKING ANGRY when I have to work with lobotomized pricks who get a segfault at address 0x00000000 in their brain_x68.exe when it comes to handle Git in the simplest ways possible.

Horrible commit messages, unfinished/buggy stuff pushed to master, force-push with fucking 6 months old code +1 change, pushing "resolved" mergeconflicts without resolving, 1 year old issues which are not closed or marked in any commit message, copying repofiles into a backup folder and committing it, not commiting files and change it directly on the FTP...
I HAVE SEEN IT ALL.

If I was not a calm and thoughtful guy I have had exploded and quit a long time ago!
I only help them so they can improve their dev style and workflows.

Lesson I learnt the hard way today: ticket every fucking task (including admin) to:

A. Cover your arse (if the tickets are not ready because they haven't given us enough information, push back on it before committing too much effort to doing it)
B. Better deliverable (what you output will probably be better quality because you worked out the requirements upfront + you know the audience)
C. You have something to show management when they want to try and overwork you some more

Another incident which made a Security Researcher cry
[ NOTE : Check profile to read older incidents ]
-----------------------------------------------------------
So this all started when I was at my home (bunked the office that day xD) and I got a call from a..... Let's call him Fella as I always do . So here we go . And yeah , our Fella is a SysAdmin .
-----------------------------------------------------------
Fella - Hey man sup!
Me - Good going mate , bunked the office , weather's nice , gonna spend time with my girl today . So what's goinon?
Fella - Bruh my network sharing folders ain't working no more .
Me - Did you changed or modified anything?
Fella - Nope
Me - Okay , gimme your login creds lemme check .
Fella - Check your inbox *texts me the credentials*

*I logged in and what I'm seeing is that server runs on Windows2008R2 , checked the event logs , everything's fine and all of a sudden what I found is fucking embarrassing , this wise man closed SMB service*
Me - Did you closed SMB service?
Fella - Yeah
Me - You know what it does?
Fella - Yeah it's a protocol , I turned it off to protect the server from Wannacry .
Me - Fuckerrrr!!!!! Asshole dumbass you fuckin piece of Dodo's shit!! SMB is the service responsible for files and network sharing!!!
Fella - But....I just wanted protection
Me - 😭😭😭

*A long conversation continues with a lot of specially made words to decrease the rate of frustration which I used already*

Fella - Okay I'm turning it on .
Me - Go on....... Asshole
Fella - It worked! Thanks a lot bro
Me - Just leave me and my soul away from evil and hang up .

*Now the question is , who the hell gives them the post of SysAdmin? While thinking this question , I almost thought of committing suicide​ but then my girl came with coffee and my rubber duck*

Stop committing only once a day or even less frequent. And start using branches.

We should not tolerate censorship.
Beyond all the u.s. hype over elections
(and the division in the west in general), the real story is all the censorship on both sides.
Reasonable voices are quickly banned, while violent voices and loud angry people are amplified.

I broke out of the left-right illusion when
I realized what this was all about. Why
so much fighting in the street was allowed, both
justified and unjustified. Why so much hate
and division and slander, and back and forth
was allowed to be spread.

It's problem, reaction, solution.
The old order of liberal democracy, represented
in the u.s. by the facade of the GOP and DNC,
doesn't know how to handle the free *distributed*
flow of information.

That free-flow of information has caused us to
transition to a *participatory* democracy, where
*networks* are the lever of power, rather than
top down institutions.

Consequently, the power in the *new era* is
to decide, not what the *narrative* is, but
who can even *participate*, in spreading,
ideating, and sharing their opinions on that
narrative, and more broadly, who is even allowed
to participate in society itself.

The u.s. and west wants the chinese model of
control in america. you are part of a network, a
collective, through services and software, and
you can be shut off from *society* itself at
the drop of a pin.

The only way they get that is by creating a crisis,
outright fighting in the streets. Thats why
people keep being released after committing serious
fucking crimes. It's why the DOJ and FBI are
intent on letting both sides people walk.
They want them at each others literal throat,
calling for each other's blood. All so they
can step back and then step in the middle when
the chorus for change cries out loud enough.

And the answer will be

1. regulated tech

2. an end to television media as we know it

3. the ability to shut someone off from any service on a dime

4. new hatespeech laws that will bite *all* sides in the ass.

5. the ability to shape the narrative of society by simply 'pruning' networks as they see fit, limiting the reach of individuals on all sides, who are problematic to
the collective direction.

I was so caught up in the illusion of us-vs-them I didn't
see it before now. This is a monstrous power grab.

And instead of focusing on a farce of election, where the party *organizations* involved are institutional facades for industrialists, we should be focusing on the real issue:

* Failure of law to do its job online, especially failures of slander and libel laws, failures of laws against conspiracy to commit crime or assault

* New laws that offer injunctive relief against censorship, now that tech really is the commons. Because whats worse than someone online whipping up a mob on either side, is
someone who is innocent being *silenced* for disagreeing with something someone in authority said, or for questioning a politician, party, or corporation.

* Very serious felony level laws against doxxing and harassment on all sides, with retroactive application of said laws because theres a lot of people on all sides who won't be satisfied with the outcome until people who are guilty are brought to justice.

I get uneasy walking away/turning off my computer without committing my code to a server. Zero faith in local storage.

First time committing a ticket is scary… I can’t stop thinking how my colleagues and tech lead gonna look at my code and question me if I lied on my resume…

Byron (reckful) has committed suicide. He was one of the first big streamers on Twitch and a game developer.

He was suffering from depression and has been for quite some time. He always appears happy around friends. He did "joke" about committing suicide on his last stream. Watching the clip makes it obvious that there was some truth to the "joke".

Also, remember that you never know what someone online is suffering from or how that person may interpret a joke. Be careful and think about how your message is received.

Please seek help if you have suicidal thoughts or even signs of depression. It's not a sign of weakness. We all need help sometimes.

Someone just overwrote 2 weeks of work in SVN because they don't understand merging.

When they did an update before committing they ignored the conflicts and tried to build their work.

But wait it won't build if their are conflicts, I know I'll just copy this backup over the checkout and check that in instead.

It took me over an hour tho fix this fucktard's mistake and I still don't think they understand what they did wrong. Their supposed to have 40+ years of experience.

In the end it turned out they wanted to change about 10 lines. They had checked in files that they didn't even change, they were just out of date compared to trunk.

New task - add new field to a form... After few hours I'm ending up committing changes in 80 files..

*Refactoring craze*

Main language, do people have such a thing? Some quixotic shit about various languages I use:

C#: Microsoft
F#: never quite committing to 100% functional paradigms while still being one of the most enjoyable langs I use
Java: null handling via optional and maybes are ugly, but better than it was
C++: surprisingly functional in 2020
Haskell: no one else seems to ❤️ it, despite it being fucking beautiful
Kotlin: Ternary warfare, Czech sports opinions on how languages should work
Clojure: parenthetical scoping makes me far happier than it should
Typescript: makes ever more sense as it changes

Not committing changes regularly

People think I don't get angry easily at office. I just don't want to get angry, at least in real world.

My mind is constantly clouded with "throwing things away, smashing my computer to crumbs, telling people to go die, fuck off, punching faces, kicking butts, committing murders and nuking the whole world".

I honestly don't get the idea behind JavaScript frameworks. Like, if JavaScript on its own is really so bad that it's only usable for front-end devs with a framework.. why has nobody considered committing back their changes into JavaScript itself? Makes life easier for everyone.

Also, regarding the framework.. as far as I understand it's a bunch of functions that you load in, right? But do you really need all of those, to the point where the unused ones are justifiable? And wouldn't it make more sense to write them yourself as you need them? I mean that's at least the idea of functions in languages like Bash or C or whatever.

What's the point of frameworks?

I recently started working on a 3 months old project, that was outsourced to two Indians genius. One of them left just before I arrived.

I had the chance to discover those guys were not using any version control system, just exchanging a zip file. I don’t even talk about the codebase, never seen such a mess …

Even better the project managers, were not using any IT program to follow the project advancement, but just Excel!!!

After a few days I realised that the remaining dev was not committing anything, the guy was always lying, (so many people died around him + some emergencies)

So, the guy got fired, but don’t worry management found new genius to save the project 🙂

Can someone tell me if outsourcing is really working?

how to evade committing small fixes

I haven't touched a repository in a while, but my group had been committing to it for a while. I sometimes wish I could be this creative.

Thoughts prior to feedback meeting, about how it's gonna go.

---------------------------------------------------------
Scenario one:
Supervisor: The shit is this? You call this a research work? Get the fuck out of here! You're fired and even your unborn kids are banned from coming into this institute ever again!

Me: *walks out sobbing* (dunno how one can walk out of a zoom meeting, but this is imaginary so who's counting?)

Scenario two:
S: Umm, good work. I just don't think it's presentable. Maybe come back in like a few weeks when you actually polish this into a "real scientific work".

Me: *sobs after meeting. Starts preping for seppuku cuz no idea where I'm headed with this work any further*

Scenario three:
S: nah man. This is no good. Let's start from the bottom. Like, start data collection from the beginning or something.

Me: *sobs and commits seppuku on the meeting.* (I just have a pen tho. Hope it has the same effect as a sword)

---------------------------------------------------------

There are other scenarios, but they all end up in me sobbing and/or committing seppuku in/after the meeting so yeah the drama is running high right now.

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.

A colleague just committed his username and password in git. When I kindly informed him, he told me that there are a lot of things on whiteboards around the office that should not be there. Oh, if that's the case, committing your credentials to git is fine.

We all make mistakes. But your response to them is everything.

I'm a fan of Linux, and have used many distros (arch, ubuntu, debian, fedora, mint, centos, rhl) and many desktop environments (KDE, Gnome, Cinnamon, xfce, Enlightenment) before asking this question.

But every single one of these desktop environments always have felt slow to respond in some cases, where I click something and it doesn't open/close immediately, or i double click something but it fails to open or select something. basically I'm not confident my actions on the GUI will have guaranteed, quick responses within reasonable time. I've never ever had this issue with Microsoft OSes (keeping aside the many badly coded softwares which hang or crash). I'm not talking about specific softwares, this is just general usage of opening settings and using the file manager, window menus.

I'm pretty sure my hardware is not the issue. I've run everything on the same rig. And this has always kept me from fully committing myself to a Linux distro. But I can never be sure about display drivers, as they're not identical. But the issues in Linux has been noted by me for many years. So I doubt it's the drivers either.

Is there anybody who agrees with me and know why Linux is the way it is like that, or is this just me facing this annoyance?

As a Dev in college working for teams in college, I don't really have a need to use git, since most of 'self proclaimed prestigious programmer child prodigies' I work with have no idea what it is; but I use it anyways as good programming practice and ease of backups.

So I tried using a GUI client after months of the git bash, and even though I looked up a few tutorials (was embarrassed the whole fucking time). I ended up adding, committing and pushing via bash.

Can anyone explain me how is the GUI client helpful in large projects and stuff?

Colleagues of mine, even though they show signs of versioning their api by having "v1" in the URL, keep committing breaking changes to that version. 😂

An area of my company hired a new director who directed his “DevOps” team to implement a process that would prevent the CI server from running tests on a PR unless the code was reviewed first. He was worried that there would be too many tests executing with 400 developers committing code frequently.

He’s from Yahoo.

I am currently working on a project with a team of 5. I like working at night. After committing my code, I sleep at 6. My team on waking up decides to change the UI and I have to start over again. The irony is: None of them are working with me on the frontend! Feels like I am stuck on a while(true) loop.

When you sit up until 2:30am trying to fix it before committing... but just can't...

Biking out to the beach on Saturday I remembered I forgot to remove a log.warn("cuntface", values) before committing on Friday.

DFW the client decides to not renew the contract, and so their start hiring their own developers. This guy decides to fix a layout problem by putting everything in a table element, breaking a bunch of other shit he didn't test for before committing. Fucking end me now, please.

Committing README typo fixes be like...

Sooooooo…. The other day I committed a change with this message:

“Committing the ultimate sin in committing secret keys again however this repo is and will always be private and my pis will be hidden on my network so it shouuuuuuld be fine... right...”

Im new on GitHub, and google didnt give me an answer simple enough for me to understand, so here i go.

How do i commit to GitHub and keep my files up to date, but without committing my password/oauth tokens?
Does one remove the line before committing, or what are you supposed to do?

Im using IntelliJ, dark theme

I'm considering quitting a job I started a few weeks ago. I'll probably try to find other work first I suppose.

I'm UK based and this is the 6th programming/DevOps role I've had and I've never seen a team that is so utterly opposed to change. This is the largest company I've worked for in a full time capacity so someone please tell me if I'm going to see the same things at other companies of similar sizes (1000 employees). Or even tell me if I'm just being too opinionated and that I simply have different priorities than others I'm working with. The only upside so far is that at least 90% of the people I've been speaking to are very friendly and aren't outwardly toxic.

My first week, I explained during the daily stand up how I had been updating the readmes of a couple of code bases as I set them up locally, updated docker files to fix a few issues, made missing env files, and I didn't mention that I had also started a soon to be very long list of major problems in the code bases. 30 minutes later I get a call from the team lead saying he'd had complaints from another dev about the changes I'd spoke about making to their work. I was told to stash my changes for a few weeks at least and not to bother committing them.

Since then I've found out that even if I had wanted to, I wouldn't have been allowed to merge in my changes. Sprints are 2 weeks long, and are planned several sprints ahead. Trying to get any tickets planned in so far has been a brick wall, and it's clear management only cares about features.

Weirdly enough but not unsurprisingly I've heard loads of complaints about the slow turn around of the dev team to get out anything, be it bug fixes or features. It's weird because when I pointed out that there's currently no centralised logging or an error management platform like bugsnag, there was zero interest. I wrote a 4 page report on the benefits and how it would help the dev team to get away from fire fighting and these hidden issues they keep running into. But I was told that it would have to be planned for next year's work, as this year everything is already planned and there's no space in the budget for the roughly $20 a month a standard bugsnag plan would take.

The reason I even had time to write up such a report is because I get given work that takes 30 minutes and I'm seemingly expected to take several days to do it. I tried asking for more work at the start but I could tell the lead was busy and was frankly just annoyed that he was having to find me work within the narrow confines of what's planned for the sprint.

So I tried to keep busy with a load of code reviews and writing reports on road mapping out how we could improve various things. It's still not much to do though. And hey when I brought up actually implementing psr12 coding standards, there currently aren't any standards and the code bases even use a mix of spaces and tab indentation in the same file, I seemingly got a positive impression at the only senior developer meeting I've been to so far. However when I wrote up a confluence doc on setting up psr12 code sniffing in the various IDEs everyone uses, and mentioned it in a daily stand up, I once again got kickback and a talking to.

It's pretty clear that they'd like me to sit down, do my assigned work, and otherwise try to look busy. While continuing with their terrible practices.

After today I think I'll have to stop trying to do code reviews too as it's clear they don't actually want code to be reviewed. A junior dev who only started writing code last year had written probably the single worst pull request I've ever seen. However it's still a perfectly reasonable thing, they're junior and that's what code reviews are for. So I went through file by file and gently suggested a cleaner or safer way to achieve things, or in a couple of the worst cases I suggested that they bring up a refactor ticket to be made as the code base was trapping them in shocking practices. I'm talking html in strings being concatenated in a class. Database migrations that use hard coded IDs from production data. Database queries that again quote arbitrary production IDs. A mix of tabs and spaces in the same file. Indentation being way off. Etc, the list goes on.
Well of course I get massive kickback from that too, not just from the team lead who they complained to but the junior was incredibly rude and basically told me to shut up because this was how it was done in this code base. For the last 2 days it's been a bit of a back and forth of me at least trying to get the guy to fix the formatting issues, and my lead has messaged me multiple times asking if it can go through code review to QA yet. I don't know why they even bother with code reviews at this point.

Committing code with the same commit message although you refactored several times and changed the structure

A loooong time ago...

I've started my first serious job as a developer. I was young yet enthusiastic as well as a kind of a greenhorn. First time working in a business, working with a team full of experienced full-lowered ultra-seniors which were waiting to teach me the everything about software engineering.

Kind of.

Beside one senior which was the team lead as well there were two other devs. One of them was very experienced and a pretty nice guy, I could ask him anytime and he would sit down with me a give me advice. I've learned a lot of him.

Fast forward three months (yes, three months).

I was not that full kind of greenhorn anymore and people started to give me serious tasks. I had some experience in doing deployments and stuff from my other job as a sysadmin before so I was soon known as the "deployment guy", setting up deployments for our projects the right way and monitoring as well as executing them. But as it should be in every good team we had to share our knowledge so one can be on vacation or something and another colleague was able to do the task as well.

So now we come to the other teammate. The one I was not talking about till now. And that for a reason.

He was very nice too and had a couple of years as a dev on his CV, but...yeah...like...

When I switched some production systems to Linux he had to learn something about Linux. Everytime he encountered an error message he turned around and asked me how to fix it. Even. For. The. Simplest. Error. He. Could. Google. Up.

I mean okay, when one's new to a system it's not that easy, but when you have an error message which prints out THE SOLUTION FOR THE ERROR and he asks me how to fix it...excuse me?

This happened over 30 times.
A. Week.

Later on I had to introduce him to the deployment workflow for a project, so he could eventually deploy the staging environment and the production environment by hisself.

I introduced him. Not for 10 minutes. I explained him the whole workflow and the very main techniques and tools used for like two hours. Every then and when I stopped and asked him if he had any questions. He had'nt! Wonderful!

Haha. Oh no.

So he had to do his first production deployment. I sat by his side to monitor everything. He did well. One or two questions but he did well.

The same when he did his second prod deploy. Everythings fine.

And then. It. Frikkin. Begins.

I was working on the project, did some changes to the code. Okay, deploy it to dev, time for testing.

Hm.

Error checking out git. Okay, awkward. Got to investigate...

On the dev server were some files changed. Strange. The repo was all up to date. But these changes seemed newer because they were fixing at least one bug I was working on.

This doubles the strangeness.

I want over to my colleague's desk.

I asked him about any recent changes to the codebase.

"Yeah, there was a bug you were working on right? But the ticket was open like two days so I thought I'll fix it"

What the Heck dude, this bug was not critical at all and I had other tasks which were more important. Okay, but what about the changed files?

"Oh yeah, I could not remember the exact deployment steps (hint from the author: I wrote them down into our internal Wiki, he wrote them done by hisself when introducing him and after all it's two frikkin commands), so I uploaded them via FTP"

"Uhm... that's not how we do it buddy. We have to follow the procedure to avoid..."

"The boss said it was fine so I uploaded the changes directly to the production servers. It's so much easier via FTP and not this deployment crap, sorry to say that"

You. Did. What?

I could not resist and asked the boss about this. But this had not Effect at all, was the long-time best-buddy-schmuddy-friend of the boss colleague's father.

So in the end I sat there reverting, committing and deploying.

Yep

It's soooo much harder this deployment crap.

Years later, a long time after I quit the job and moved to another company, I get to know that the colleague now is responsible for technical project management.

Hm.

Project Management.

Karma's a bitch, right?

Numbers implementation in so many freaking languages!!!

Lack of naming consistency, and meaning.
And yes, setImmediate and setTimeout 0...

But the biggest feature issue is that people can code without thinking!!! There should be some hardware security to impede stupid fucks from committing code...

When your CSE partner always overrides your perfect self committing code like lastItem, rightFrontItem and just renames them all to x, n, and z. Now it looks like shit and can't understand it as easy! I guess fuck giving variables meaningful names! Lets just make chaos in a world of order.

When you're making a git tutorial and you forget to Ctrl+S before committing.....

Request for software: a program that prevents shitty coworkers from committing with the message “fix”, random letters, or other nondescript messages.

Fuck, wanted a year long streak on github but failed at 40 days.

I did code but just had no part finished so didn't commit.

I even have an alarm for committing ffs. I just snoozed it and was like I do it when I finished x. Forgot track of time like always with coding and found out four hours later.

Fuck. Back to one. I just start over, it shouldn't be that hard.

I should change my commit behavior to push if compiles instead of push after complete feature. So, I change the definition of achievement easier to achieve

Not caring about code styling and just committing because whiny people annoy me. It works; it works. I should probably abid by code styling standards and do a precommit but bite me 🖕🖕🖕

No, "committing to repository" is not the correct interpretation of "the commit messages should tell what it does, not did"

--
Always be precise, watch your wordings.

Committing typo fixes in documentation to appear as being "at work".

a telecom company whose 4g network's call drop is 65% of total calls. :) wonder what devOps is committing crime behind those chairs

Some of you know I'm an amateur programmer (ok, you all do). But recently I decided I'm gonna go for a career in it.

I thought projects to demo what I know were important, but everything I've seen so far says otherwise. Seems like the most important thing to hiring managers is knowing how to solve small, arbitrary problems. Specifics can be learned and a lot of 'requirements' are actually optional to scare off wannabes and tryhards looking for a sweet paycheck.

So I've gone back, dusted off all the areas where I'm rusty (curse you regex!), and am relearning, properly. Flash cards and all. Getting the essentials committed to memory, instead of fumbling through, and having to look at docs every five minutes to remember how to do something because I switch languages, frameworks, and tooling so often. Really committing toward one set of technologies and drilling the fundamentals.

Would you say this is the correct approach to gaining a position in 2020, for a junior dev?
I know for a long time, 'entry level' positions didn't really exist, but from what I'm hearing around the net, thats changing.

Heres what I'm learning (or relearning since I've used em only occasionally):

* Git (small personal projects, only used it a few times)
* SQL
* Backend (Flask, Django)
* Frontend (React)
* Testing with Cypress or Jest

Any of you have further recommendations?

Gulp? Grunt? Are these considered 'matter of course' (simply expected), or learn-as-you for a beginner like myself?

Is knowing the agile 'manifesto' (whatever that means) by heart really considered a big deal?

What about the basics of BDD and XP?

Is knowing how to properly write user-stories worth a damn or considered a waste of time to managers?

Am I going to be tested on obscure minutiae like little-used yarn/npm commands?

Would it be considered a bonus to have all the various HTTP codes memorized? I mean thats probably a great idea, but is that an absolute requirement for newbies, or something you learn as you practice?

During interviews, is there an emphasis on speed or correctness? I'm nitpicky, like to write cleanly commented code, and prefer to have documentation open at all times.
Am I going to, eh, 'lose points' for relying on documentation during an interview?

I'm an average programmer on my good days, and the only thing I really have going for me is a *weird* combination of ADD and autism-like focus that basically neutralize each other. The only other skill I have is talking at people's own level to gauge what they need and understand. Unfortunately, and contrary to the grifter persona I present for lulz, I hate selling, let alone grifting.
Otherwise I would have enjoyed telemarketing way more and wouldn't even be asking this question. But thankfully I escaped that hell and am now here, asking for your timeless nuggets of bitter wisdom.

What are truly *entry level* web developers *expected* to know, *right out the gate*, obviously besides the language they're using?

Also, what is the language they use to program websites? It's like java right? I need to know. I'm in an interview RIGHT now and they left me alone with a PC for 30 minutes. I've been surfing pornhub for the last 25 minutes. I figure the answer should take about 5 minutes, could you help me out and copypasta it?

Okay, okay, I'm kidding, I couldn't help myself. The rest of the questions are serious and I'd love to know what your opinions are on what is important for web developers in 2020, especially entry level developers.

Maybe im wrong but still, damn policies, at my job i need a code review and a commit review before committing code and Im ok with that but hell, I was required to run the api tests when I only modified 2 front end file, i mean seriously i need to run c# tests after modifying angular components. It just seems silly and foolish and a complete waste of time to run the tests for all the projects when i didnt even modified one.

If you work with me and know who I am then stho and accept it. :p

One of the barriers to professional software development is OCD.

Is this code right? No, fix. Wait, no, still not right.
Did I just commit this? Check again.. did jira reload properly? Wait, checking again, did I commit this? Checking. Did I commit this? Checking. Is my mind fooling me about committing this? Checking.

while(true){
goCrazy();
}

So I taught git to my colleagues. They were happy to learn new things.

I asked them to commit things that they have done with proper message in every projects from now on. I find 50-80 commits to pull in every 10mins. Ughhh. They were committing every single changes they were making. 😂😂😂

Sometimes simple things can overwhelms some people

I just started but I'm already tired.

For some years I have worked in the industry, not a lot, I know right but I really wonder how do you deal with all "not code-related" bullshit.

IT should be a dynamic field but somehow it is stuck inside the business logic which is all about the money and that does not take care of the real matter which is "code engineering".

- Most of the projects I have seen are an utter mess.
- No real structure
- Code is literally thrown somewhere to make stuff works and fix bugs
- Features which should require X amount of time are planned and shipped earlier ignoring best practices.
- The customer changes idea every week
- Nobody wants to pay for a reasonable architecture but prefer to keep financing un-maintainable projects that only God knows where they have been made (presumably in Hell)
- Juniors devs with no real senior following them committing unreasonable stuff
- Seniors devs thinking they are but they aren't.
- Company that keeps delivering projects even if they have not the required amount of people to make it in time.

Seems like nobody wants to stop and take time to think and make the right decisions. I see people running around me like crazy ants.

But, above all, what really kills me deep inside is HR. You are looking for "dynamic" "talented" "cool" devs but you are not willing to pay them enough.

Should I talk about LinkedIn?

Oh, God... Even the worsts companies sound like they are into Fortune 500. I feel so much hypocrisy here.

I have worked for big and small IT companies.
In the end, is all about "inside politics", everything which is getting financed is not because of usefulness but because of "relationship".

I started coding when I was really young.
After ten and more years, I finally take the job of my dreams but everything is shuttering under my feet.

If you have some words of wisdom, I'm here to hear you.

PS.
I'm not a native English speaker, I apologize for any mistake.

Today I was minding my own coding-committing-pushing business, when all of a sudden, a split second before typing Enter on a command, the obnoxious UPDATE JAVA popup reared it's ugly head.

Normally I just politely recommend it to fuck off and let me manage my Java versions with homebrew on my own time. But I had no time to not press Enter, and so it rapidly started downloading/installing.

Thankfully I had juuust enough time to hit the cancel button. The progress bar it was showing stopped at 81%. Didn't even have time to read what it said. Crisis averted. Them NSA fucks be like, "curses, foiled again!"

This was probably the most intense moment of the year for me. I think my lifespan grew shorter a few months.

Dreaded auto-updates are getting smarter. They nearly got me when I was in a vulnerable state of hitting Enter many times. Stay on your toes!

My manager committed an empty Jenkinsfile on his project (he loves committing empty files or docs with words "TODO" in them). I decided to add the project to Jenkins so at least he sees a red X and failed build on ever branch .... green check? An empty Jenkinsfile is a valid Jenkinsfile?! Damn it Jenkins!

i am so much dead inside that I can't even feel depression anymore, idk how to explain, its like committing a spiritual suicide

So today I was having this discussion with my colleague regarding a messed up pull request.

Me: are you done merging the remaining branches into master?
Colleague: no, I'm still merging the changes manually.
Me: but why?
Colleague: because the changes will overwrite the changes in master.
Me: but how? It will just conflict and you can keep whichever changes YOU WANT. You can even edit before committing the merge.
Colleague: I'm just redoing the changes manually anyway.
Me: -_-

Indian developers were committing hundreds of garbage pull requests to get a free Hacktoberfest t-shirt.

Meanwhile repository admins:

Just spent the last hour going through code and nHibernate relationship mappings only to realise that my repository's create method had an not exists check instead of an exists check preventing it from actually committing the data ........... i'm tired and need a holiday !

Forgetting to switch the git branch from master to back to Dev after committing. If I had a penny!

I work on a small dev team. A team member recently left. My boss is lenient about committing our repos. ex co worker didn't commit his code and instead just left his code on a zip drive. Today I had to resolve nine months of conflicts and basically throw out all the work this guy had done.

If you build a company on the blockchain you're basically committing to 100% transparency with your investors if you fail to increase the value of your token or coin your investors will be left holding the bag. 💰

God dammit, I hate my bloody coworker sometimes. He's doing a huge refactor, and committing... which is fine, but he's clearly NEVER run the fucking test suite. I didn't write that much coverage so you could commit something that breaks the build and then fuck off to lunch.

Not only has he not run the test suite, I don't think he's run his changes AT ALL. The bloody modules don't even import the way he's written it now.

Sometimes in our personal projects we write crazy commit messages. I'll post mine because its a weekend and I hope someone has a well deserved start. Feel free to post yours, regex out your username, time and hash and paste chronologically. ISSA THREAD MY DUDES AND DUDETTES
--
Initialization of NDM in Kotlin
Small changes, wiping drive
Small changes, wiping drive
Lottie, Backdrop contrast and logging in implementation
Added Lotties, added Link variable to Database Manifest
Fixed menu engine, added Smart adapter, indexing, Extra menus on home and Calendar
b4 work
Added branch and few changes
really before work
Merge remote-tracking branch 'origin/master'
really before work 4 sho
Refined Search response
Added Swipe to menus and nested tabs
Added custom tab library
tabs and shh
MORE TIME WASTED ON just 3 files
api and rx
New models new handlers, new static leaky objects xd, a few icons
minor changes
minor changesqwqaweqweweqwe
db db dbbb
Added Reading display and delete function
tryin to add web socket...fail
tryin to add web socket...success
New robust content handler, linked to a web socket. :) happy data-ring lol
A lot of changes, no time to explain
minor fixes ehehhe
Added args and content builder to content id
Converted some fragments into NDMListFragments
dsa
MAjor BiG ChANgEs added Listable interface added refresh and online cache added many stuff
MAjor mAjOr BiG ChANgEs added multiClick block added in-fragment Menu (and handling) added in-fragment list irem click handling
Unformatted some code, added midi handler, new menus, added manifest
Update and Insert (upsert) extension to Listable ArrayList
Test for hymnbook offline changing
Changed menuId from int to key string :) added refresh ...global... :(
Added Scale Gesture Listener
Changed Font and size of titlebar, text selection arg. NEW NEW Readings layout.
minor fix on duplicate readings
added isUserDatabase attribute to hymn database file added markwon to stanza views
Home changes :)
Modular hymn Editing
Home changes :) part 2
Home changes :) part 3
Unified Stanza view
Perfected stanza sharing
Added Summernote!!
minor changes
Another change but from source tree :)))
Added Span Saving
Added Working Quick Access
Added a caption system, well text captions only
Added Stanza view modes...quite stable though
From work changes
JUST a [ush
Touch horizontal needs fix
Return api heruko
Added bible index
Added new settings file
Added settings and new icons
Minor changes to settings
Restored ping
Toggles and Pickers in settings
Added Section Title
Added Publishing Access Panel
Added Some new color changes on restart. When am I going to be tired of adding files :)
Before the confession
Theme Adaptation to views
Before Realm DB
Theme Activity :)
Changes to theme Activity
Changes to theme Activity part 2 mini
Some laptop changes, so you wont know what changed :)
Images...
Rush ourd
Added palette from images
Added lastModified filter
Problem with cache response
works work
Some Improvements, changed calendar recycle view
Tonic Sol-fa Screen Added
Merge Pull
Yes colors
Before leasing out to testers
Working but unformated table
Added Seperators but we have a glithchchchc
Tonic sol-fa nice, dots left, and some extras :)))
Just a nice commit on a good friday.
Just a quickie
I dont know what im committing...

Forget about committing often and end with multitudes of changes. Which then leads to writing a generalized commit message.

Anyone else have the ritual of searching for curse words in code prior to committing & pushing your changes?

When your IDE pulls a Stannis Baratheon on your ass when committing.

When my brain was overloaded and overwhelmed during rapid-cycling bipolar disorder, my life and my thoughts were a complete mess. Somehow, when I heard or imagined plurals of certain words, like "cans" or "cups", my brain painted pictures of a cute civilization of living soda cans. They fought oppression that came from us humans, but lacked mental capacity to do so. I felt really sorry for them and wanted to help. The more ordinary the word were, the more striking effect it had on me.

The rapid-cycling fashion of bipolar disorder is often triggered by unfit prescription medicines. This kind of disorder is among the most lethal mental disorders there are, with a huge percentage of patients committing suicide.

If you can't make sense of your thoughts, if your emotional responses seem inadequate or too strong, to the point when you can collapse crying after some random thought, stop whatever you're doing and seek help. Ask friends and family to find you a psychiatrist, as by the time you need help, you may lack mental capacity or emotional resource to find a doctor by yourself. To me, even the idea of leaving my bedroom and going somewhere was painful to think about.

If your thoughts appear to be "put into your brain" against your own will, if they make no sense, don't attempt to make sense of them. They are nothing but a random noise produced by overwhelmed synapses.

I'd argue to say that committing often, even if the commits aren't always meaningful, has saved me numerous times from bad code gone awry.

I've recently learned how committing of the Save Data to file works in my project.

The file is updated w/ _each change_ made to the settings.

Worse yet - the file is updated even when _no actual change_ is made due to the setting already being at its highest / lowest value possible.
/*
e.g. 5 is maximum sound volume.
- You try increasing the sound volume.
- Setting can't get any higher, so remains unchanged.
- *Update the Save Data*.
*/

What kind of abusive masochist would do that?

// Yes... there's always blame.

Women, software engineers make good boyfriends.

Why?

We're not scared of committing. We do it everyday at work. :P

When you don't commit anything until after 48 hours of work.

I was just ready to get this feature finished so I could finally get some sleep, and in my persistence, I neglected to commit every once in awhile.

Now I've finished the feature and have all of these changes; I had to explain myself in the commit description.

When rage turns to sadness :
With great frustration wrote and debugged android code since morning , so as a reward , I thought about rebooting my laptop once the code was working and committing it later. Code ran , rebooted my laptop and went to get some coffee, only to find that bodhi crashed and wouldn't run without live usb. No commit, no backup, all went down the drain

I really hate committing comes to the got using putty.
git status
Then look at the list and see which files you modified after that adding those using
git add
This work is really time consuming and frustrating when suddenly in between the connection is lost

for the 3rd time ive tried introducing some version control on a project that really needs it because it has multiple people working on it.

And because the last time my efforts got shut down because in practice people thought it was too much of a hassle to develop locally rather than on the shared development server directly, I made a feature that would let people checkout branches on said server...

Apparently the action of; saving > committing > pushing to your feature branch > merge after aproval, is still too much for people to comprehend; "I think this is too convoluted can't we just keep pushing to the production server to check our work and then commit and push to the master branch"

So I just got pissed and said fuck it, no more git then, I'm not even going to put any effort into changing tooling here anymore, and this is a massive project where we have to manually remove code that isnt ready yet from the staging environment.

Are the people I'm working with just this stupid or am I really overengineering this solution because I think 4 people should not be working on the same file at the same time without any form of version control and just direct upload to FTP.

(and yes, I know I should leave this job already, but social anxiety of starting at a new company is a big obstacle for me)

Released the product to customers without realising someone had pre-filled a production test accounted login at the login screen. Obviously it was used for testing purposes and the dev forgot to remove it before committing.
I loled when I found out about it, and some customers started to login and made transactions.
When I checked the commit history... It was under my name :/

Really hate it when a project is switching focus every month or so. You start focusing and committing a lot of time to make things work. Taking initiative to enhance things. Then some weeks later management is switching focus and you have to port all fixes in the new code base. Then some weeks later you have to work on the things you did before but with some adjustments that result in the old code not being possible to use and you have to port fixes again. When complaining you sometimes get the question "how hard can it be, it's just some code". Some motivation is lost every time. And repeat this like a "while true" loop.

I've started to get more into the TOR idea over the last couple of weeks.

I know I'm way to "non protective" of my privacy but changing would mean I'd have to break many habits and stop using things I'm used to.

A couple years back (I guess it was in like 8th grade or so) I had a presentation in German (my first language) for an extra mark. It was about tor. In the process of researching all of it I learned quite a lot about it. All of this knowledge has stuck to me the whole time, unused.

Fast forward to today, I've finally decided to use the couple of bitcoins I have (like 15€ or so) from my home mining experiment to rent a vps for a tor relay. First, I was lucky enough to find a service provider that accepts bitcoin for a 3€. They advertised "Fair use Traffic", later found out, after committing for three months since I was like "yeah... will be fine", in the customer panel there is a graph that shows me that I have used x% of 1.5 TB... I guess the customer support will get an email from me asking what "Fair use" exactly means... But that's fine... Oh... And ipv6 wasn't a thing to be found...

To wrap it up... I've now got a 2 weeks old little tor relay <3

(I didn't wanted to put it on my main vps where I have 200mbit guaranteed at unlimited for 5€ a month since that's where I have my mail server running and a hidden service for my next cloud)

learning golang. so they have optional feature called `vendor`. so basically they reinvent the `node_modules`.

the weird thing is that it supposed to work by committing dependencies to git. but unlike node_modules, vendor directory wouldn't be massive since they come with assumption that the community wouldn't fuck up the libraries ecosystem.

huh?

Why are you so slow Kaggle...
(((preparing kernel)))
(((committing)))
I have tons of data to analyze with multiple methods...

sigh...

Coworker just showed me how he avoids merge conflicts and I'm undecided on it. We use feature-branch workflow, so if a feature takes a long time to finish, it may mean merging master multiple times. He avoids it by stashing changes instead of committing them, then when he needs to merge master into the branch it's still clean. When the feature is done and he's ready to commit, he pops the changes and git diff shows all the changes before you push and you just change what you need instead of being forced to use the horrible merge software.

There must be problems with this, right? This seems too easy for it not to be the standard.

Committing every single change to the repository without doing any tests.

I was given a project at work, and instead of committing a src directory, all of the work the person before me did was in the compiled dist directory. fml

Personal Observation
=======
Today morning I was looking through different React UI frameworks for my next hobby project. MUI React has been my favorite but I wanted something informal for this project, so I opened up all the two dozen suggested ones by Google searches.

Since reversing on committing to a UI framework, later on, is a huge headache so I was going through the component demos to shortlist a handful for final consideration, and in that, I almost skipped out all the frameworks which weren't showing a preview of their component on the documentation page itself.
========
I wonder how many frameworks are genuinely good but are passed over due to others having better and more illustrative documentation. In a market with vast abundance, one cannot rely on the sincerity of the consumer to invest time and determine the best possible product, for there are plenty of 'good enough' products that the user does not really worry about false negatives.

Committing just before leaving the office, especially on Fridays.

Committing :wq to github
#vimproblems

Sprinting all week long against time. friday afternoon, committing time. connect to Git to check latest changes. Server down.
New IT Guy pushed an update @4PM.
He's been missing for a week.

Just wanted to add my two cents about the GDPR: while i sympathize with those that need to make their company comply (it can be really tough and complicated to both convince the guys upstairs and implementing everything) i have to say that as a simple end-user it really is an amazing acheivement in transparency and honesty :D its amazing to able to see what services really collect about you, and to have a clear way to opr out of things if need be :) the document seems very well researched from what little i read, and i think the gdpr it sends a very positive message about committing to transparency and protection of users rights to othe countrirs that are very known for very lax regulation *cough* Us *cough*.

Im interested in seeing how this whole thing pans out, best of luck to everyone out there dealing with this!

COMMITTING only after complete development, testing and integration of a feature

You work in a team, for a team to move forward successfully the team should work in sync. A team always has a goal and a plan to get to it. There are times when the team needs to take a different direction therefore the set path should always be available for change because our environments dictate it.

We all have different styles of working and different opinions on how things should work. Sometimes one is wrong and the other is right, and sometimes both are wrong, or actually sometimes both are right. However, at the end of it all, the next step is a decision for the team, not an individual, and moving forward means doing it together. #KickAssTeam

The end result can not come in at the beginning but only at the end of an implementation and sometimes if you’re lucky, during implementation you can smell the shit before it hits the fan. So as humans, we will make mistakes at times by using the wrong decisions and when this happens, a strong team will pull things in the right direction quickly and together. #KickAssTeam

Having a team of different opinions does not mean not being able to work together. It actually means a strong team! #kickAssTeam However the challenging part means it can be a challenge. This calls for having processes in place that will allow the team members to be heard and for new knowledge to take lead. This space requires discipline in listening and interrogating opinions without attachment to ideas and always knowing that YOUR opinion is a suggestion, not a solution. Until it is taken on by the team. #KickAssTeam We all love our own thinking. However, learning to re-learn or change opinions when faced with new information should become as easy to take in and use.

Now, I am no expert at this however through my years of development I find this strategy to work in a team of developers. It’s a few questions you ask yourself before every commit, When faced with working in a new team and possibly as a suggestion when trying to align other team members with the team.

The point of this article, the questions to self!

Am I following the formatting standard set?

Is what I have written in line with official documentation?

Is what I am committing a technical conversion of the business requirement?

Have I duplicated functionality the framework already offers?

I have introduced a methodology, library, heavily reusable component to the system, have you had a discussion with the team before implementing?

Are your methods and functions truly responsible for 1 thing?

Will someone you will never get to talk to or your future self have documentation of your work?
Either via point number 2, domain-specific, or business requirements documentation.

Are you future thinking too much in your solution?

Will future proof have a great chance of complicating the current use case?

Remember, you can never write perfect code that cures every future problem, but what you can do perfectly is serve the current business problem you are facing and after doing that for decades, you would have had a perfect line of development success.

Goddamn I hate TFVS. I'm working on PHP application where the code is stored on TFS. So far, I've been getting by using the VSTS plug in Microsoft supplies on PHPStorm. The plugin is buggy as hell, and I'm about fucking done with it. Apparently, PHPStorm doesn't save files when your committing. Unbeknownst to me, however, the most recent attempt failed, crashing the plugin. Of course, and the commit task is still running under the hood, so none of my work has been saved

I could go programming drones to kill my own people for money, like at least then I'd have a connection to my job

also programming drones sounds kind of fun

I used to really like pvp games. I also love unconventional RTS games. who wouldn't wanna make a real-world pvp RTS game interface, or automate an army of autonomous drones that could act on their own like it's a game of screeps

literally just so fun

if I was @ostream and an accelerationist...

either case if I go work somewhere and build them something great I have weird confusing PTSD emotions about it. to be honest making war machines somehow makes me less anxious about the idea. isn't it strange. I can't figure it out

you help people but they fuck you. at least if you're fucking people you'd accept being fucked in the process so you don't end up feeling anxious? I don't know why I feel like I do

you'd expect if you help people they would help you back. then when they don't it ruins everything, it ruins your core. you also can't know if who you are committing to will help you back or not. so you can only lose. if you help you'll get fucked. so why help?

in which case just doing something you love like optimizing pwn machines is what I'm built for. is that all I got? how does that make sense? it just doesn't to me. you'd think it would be clear but something is fighting

Okay guys, after sleeping it over I decided that I didn't need to dump my entire stack of Java/mySQL and instead just slow the hell down on my development time. I'm going from Udemy to a book to help me be a better dev and this is a night and day difference as my book breaks every bit apart and explains it in a lot more depth than having a video walk me through it. What I wouldn't do without Amazon's Kindle service I tell ya...:)

The only major thing I'm changing in this project is committing to one Javascript tool, REACT, as I need a simple tool to ease myself into learning Javascript. Wish me luck. :P

Today I'm starting the project over, but this time breaking it down and going at better pace. Thanks for all the advice guys. :)

...I'm going to need a lot of Jack Daniels for this project aren't I?

Some time ago, I gave a tutorial and wrote page with some brief instructions for configuring and start using git for a team of researchers. A few day later I came back to check how they were doing and I found that following my instructions, several people were committing as:

John Doe <john.doe@example.com>

Perfect! I don't think that there is anything else I can do to help them.

mkdir ChuckTesta or MyTestProject or something similar.
I always like to use a sandbox beforehand to experiment with technologies and get familiar with them before committing to an actual project repo.

I'm never committing to finishing another PC game ever again... And sticking to arcade, short games only.

Playing Nu no Kuni 2 for the last 3 days... 25hrs and counting... Now at final boss... I think and I can't get infinite HP in Skirmish... So Keep getting entire force wiped out one hit with his laser beam which keeps getting stronger....

It's like a fly vs us. In order to win it's gotta slowly chip away at u, but he can die at an instant any time...

Oh and the 25hrs includes massive cheating and speed hacking to move faster.

A person who just starting out ask me about git.

I explain what is "init" , "remote" , "add" , "committing" everything was going well until vim happen.

I just refer him to some beginner friendly tutorial about git and give him a link to git client tool.

How do you guy learn about git? When I stop to think about it git have lot of features.

*Begins a java project in IntelliJ*
*Puts it on git without committing .idea folder*
*Suddenly finds out 26 libraries are needed so adds maven*
*Collaborators don't like maven*
*Battle on git between package names com.company.project and main.java.com.company.project*

Where even if it's now his work, he does the work. Even modifying your code in your own repository. Worse, committing it in master!

if i get a nerdy girlfriend just know i smashed the day before each day where i commit 5+ times on github