wk87 is a dangerous topic for me, i've been through a lot. I apologise for what I am about to inflict on this network over the coming week.

Most incompetent co-worker, candidate 1, "T".

T was an embedded C developer who talked openly about how he's been writing code since he was 14, knew all the C system libraries and functions like the back of his hand. For the most part, he did ... but not how to actually use them, as (based on his shocking ... well everything) he was inflicted by some sort of brain disorder not yet fully understood by medical science. Some highlights:

- Myself and the CTO spent 4 days teaching him what a circle buffer was and how to build one.
- His final circle buffer implementation had about 3 times as much code as he actually needed.
- When the code was running too slowly on the device, we didn't try find any performance improvements, or debug anything to see if there was anything taking too long. No not with T, T immediately blamed TCP for being inefficient.
- After he left we found a file called "TCP-Light" in his projects folder.
- He accused the CTO of having "violent tendencies" because he was playing with a marker tossing it up in the air and catching it.
- He once managed to leave his bank statements, jumper and TROUSERS in the bathroom and didn't realise until a building wide email went out.
- He once .... no hang on, seriously his fucking trousers, how?
- He accused us all of being fascists because we gave out to him for not driving with his glasses, despite the fact his license says he needs to (blind as a bat).

... why were his trousers off in the first place? and how do you forget ... or miss the pile of clothes and letters in a small bathroom.

Moving on, eventually he was fired, but the most depressing thing of all about T, is that he might not even be top of my list.

Tune in later for more practiceSafeHex's most incompetent co-worker!!!

Boss: I saw your last commit, great work!
Dev: But... You told me to delete all the features I added...
Boss: Yes, fantastic improvements!

Huge code improvements

So i've been a dev manager for a little while now. Thought i'd take some time to disambiguate some job titles to let everyone know what they might be in for when joining / moving around a big org.

Title: Senior Software Engineer

Background:
- Technical
- Clever
- Typically has years experience building what management are trying to build

Responsibilities:
- Building new features
- Writing code
- Code review
- Offering advice to product manag......OH NO YOU DON'T CODE MONKEY, BACK TO WORK!

Title: Dev Manager

Background:
- Technical
- Former/current programmer
- knows his/her way around a codebase.

Responsibilities:
- Recruiting / interviewing new staff
- Keeping the team focused and delivering tasks
- Architecture decisions
- Lying about complexity of architecture decisions to ensure team gets the actual time they need
- Lying about feature estimations to ensure team gets to work on critical technical improvements that were cancelled / de-prioritised
- Explaining to hire-ups why we can't "Just do it quicker"
- Explaining to senior engineers why the product manager declined their meeting request

Title: Product / Product Manager

Background:
- Nothing relevant to the industry or product line what so ever
- Found the correct building on the day of the interview
- Has once opened an Excel spreadsheet and successfully saved it to a desktop

Responsibilities:
- Making every key decision about every feature available in the app
- Learning to ignore that inner voice we like to call "Common sense"
- Making sure to not accidentally take some advice from technical staff
- Raising the blood pressure of everyone below them / working with them

Title: Program Lead / Product Owner

Background:
- Capable of speech
- Aware of what a computer is (optional)

Responsibilities:
- Sitting down
- Talking
- Clicking random buttons on Jira
- Making bullet point lists

Title: Director of Software Engineering

Background:
- Allegedly attended college/university to study computer science
- Similar to a technical product manager (technical optional)

Responsibilities:
- Reports directly to VP
- Fixes problems by creating a different problem somewhere else as a distraction
- Claiming to understand and green light technical decisions, while having already agreed with product that it will never happen

Hey everyone,

During some backend improvements to the devRant infrastructure, some of our async queue processors (SQS) stopped working which caused many notifs to not go out/stop working. Unfortunately our alerting didn’t pick up on this since there were still queues being processed (just not specific ones) and some aspects of notifs working. Big apologies for this issue!

It is now resolved, and while very delayed, no notifications were lost and all were processed after the queue processors started up again. Sorry for the bulk notifs, but we wanted to make sure all that were supposed to go out went out.

Additional alerting will be put in place to prevent this from happening again.

Thanks for your patience!

Among the many improvements introduced by Windows 10, the one I enjoy the most is the freshly redesigned, user-friendly BSOD.

"Can you work on this ticket? It's kind of urgent."

-- "OK"

"And could you please not refactor? Just get this done."

-- "Why? What's the issue?"

"The logic is complex. We should not break it."

-- "Erm, that's what the tests are for. So yes, if the need arises, I'll refactor. The tests are my guidelines if the logic breaks or not."

There's a reason we create tests. So let's not hinder code base improvements by some random fear that stuff might break.

If breaks due to refactoring, we'll fix it by adding a valid test case during and then fixing the bug.

If my refactoring does not break the tests, I'll assume the code base is stable.

If your code is untested, then we have a complete different problem.

---- Startup RantLife ----

A senior developer joined the team, let's name him Bob, and this guy is really good no doubts about that.
He made suggestions, some improvements, but Bob is always waving his hands and says out loud that some part of the code base is really really bad.
I kept quiet until one day I had to pair with Bob to check a feature. Guess what happened, as usual, Bob clenched his fist and start pointing that this code is super ugly.
So let's check the history of changes and boom, Bob was the main writer.
That moment, I was completely silent, trying not to smile as Bob came up with an excuse, he never admits that he is wrong, now he needs a scapegoat and he starts blaming the process, the planning...
I believe that being humble and saying sorry is a quality that it requires time to develop.
So don't be like Bob, please :)

While working on some improvements to camera system I accidentally made pretty cool transition to the rooms.

I need more dev friends... currently drinking a beer alone. Not that I am alone but I am unable to engage in normal conversation at the moment. Just finished a 7 hour coding binge where I developed a solution which I am very proud of and which results in weeks of development time saved for the company which results in more time for proper refactorimg and Magic tournaments. I just want to sit down with a friend, show my code, ask for improvements and reason the chosen solution. And drink beer.

So i've been put in charge of bringing the devs together to form a small dev team, instead of having 3 separate devs (including me) sitting apart on separate projects. The idea was to have us talk more, work together more, learn more about the other projects, reuse more code etc.

(I've been arguing to let us do this for a while)

So I asked my manager could we move to the 4 desks in the corner, so we can have our own space, talk without having to book a meeting room each time etc. Its also a bit quieter over there and we all really need that in our noisy office.

Manager sent me an IM today while I was working from home to tell me we can have the desks. Was super happy, messaged the devs to tell them they can start moving.

Just got a message from one of them to say our manager has started moving his stuff over too. Seems he agreed with me that it is quieter over there and he doesn't like the noise either ... so he's joining us.

A huge part of the move was us wanting to work on side projects to automate and speed up various things in the team, that he has been against. We know we can make huge improvements but he doesn't see it. He's only interested in Word, Excel and Powerpoint.

So now we have our space, and anytime we try to work on something we are actually interested in, we'll have a little voice in the corner to pop up and point out what other things he deems more important and tell us to stop wasting our time.

Pretty fucking annoyed to be so happy and then get shot down like that. Happy weekend everyone!!

Bittersweet moment today, the interns last day was today, the improvements they made over the last 4 months, putting up with my “Gordon Ramsey” style attitude... definitely goes down in the books as one of best groups of freshman interns. They all truly thanked me for what they learned I sat them down and did a code review with them... but fooled them and showed them code they wrote 4 months ago.. they totally forgot about.. and couldn’t believe it was their own code.. that’s the level professionalism and improvement they made writing embedded software in 4 months.. they can’t wait to for next summer, neither can I.
Even had some of the electrical interns asking our department manager if they could switch to more software focused during their next rotation. Just so they can be under me.
I may be hard and a dick at time... but they learn! And it says a lot when you have college students impacted enough and see other students benefit so much that the “outsiders” wanna switch majors or focuses.!

KISS.
Keep it simple, stupid.

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

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

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

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

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

Started working on a pihole alternative a while ago.

I like pihole a lot but one of the features I am missing is to be able to define a list of mass surveillance related domains (Snowden leaks; PRISM program and such) and show statistics based on dns queries containing blacklisted domains, prases/words and surveillance-related domains/words (google/facebook/microsoft/apple etc).

Started working on one based on an existing (php based) dns server which is open source and slowly but surely developed something which worked.
Then, I found out that the php resolving function (dns resolving) uses the system default, which can, of course, be google's dns as well. Changing this would be ideal but while the documentation suggested that it could be done some way, it didn't work for me so I chose a library which can do it with specific dns servers (to use as external dns servers).
This library used a different way of showing the retrieved dns query results and really wasn't in for converting everything by hand so i kinda quit the project a while ago.

A few days ago I thought fuck it and started again.
Now have a working version based on the new dns resolving library and made some other good improvements.

For those who are wondering why I chose PHP for this: why the fuck not?

Happy happy happy.

I've been fairly lucky with my bosses of late since I've progressed in my programming career. But my absolute worst boss was when I first started working in an office environment doing data entry. My boss at the time was terrible, and she was always against innovation or process improvement. She also always tried to make herself look good and taking credit for the accomplishments of others. If she screwed up it was your fault, and she was "always buried in email" so she could never respond to you for pto requests, or escalation of issues between departments. My whole family pretty much worked in various roles in the department and she fired my brother after my mother left the company for no reason, saying he was "sleeping", but I worked right next to him and he's tall and had to slouch just to comfortable see his computer screen since the same manager refused to approve work station improvements for him.

Our workflow was to receive daily spreadsheets of health care claims that we had to manually process and enter into the system. So being the lazy innovator that I am, and trying to find ways I can efficiently work, I delved into studying visual basic and programmed a few functions and tools in excel to analyze, highlight, and process some of the data since the claims on the spreadsheets always had a specific pattern. This was all before I had any formal education in computer science so the program was very basic and clunky but it tripled my efficiency. When I brought it up to my boss to spread it among the rest of our team so they could use it after a short 20 minute training, she struck it down saying any training or use of it would be a waste of resources since it was too technical and complex to be used and if I were to keep improving it or use it I would be fired. It was literally copy and paste from one spreadsheet to the other en masse and clicking a button to sort and fill in the blanks. Eventually I showed it to the director of the department when working on a large data entry project with her, and I was later offered a job as a technical analyst where I was responsible for the codebase that generated the reports for the department and specifically all the reports my old boss used where I would occasionally mess with her to get back at all the crap she gave me and my brother. Since all the reports were blind carbon copied to everyone, I would send out her reports on a delay while everyone else got them on time. It eventually got her in so much crap she had to step down as a manager. She still works in the same company that I started working at again earlier this year, and like the many careers she's ruined she eventually ruined her own within the company 😂

I once reviewed a Pull Request made by a fairly junior developer. They had joined recently, and this was one of the first times they had to touch a bigger part of the code.

Due to a mix of inexperience, new (to them) coding standards and lack of git knowledge, they ended up with a mess of a PR, with a few thousand lines changed, and no way to split it off.
I ended up spending the best part of a day reviewing the whole thing and requesting changes.

Even with the long list of improvements, however, I wasn't sure they would get the magnitude of their fuckup.
So I decided to use a real-world, palpable way to show them what they had done: I went and printed the github diff for that PR. It rendered the glorious amount of 73 pages.

I'll never forget their face, and those of their teammates, when I barged into the room with a thick wad of paper and deposited them on their desk.

At least it worked. I never saw another big, ill-thought pull request from them again.

Today I visited a partnered company, best summarized as "our people are the best at what they do, although we haven't figured out what it is that we do".

It was fucking awful.

Halfway a presentation about "capitalization on the internet of things" which featured nothing about hardware or protocols at all, a guy stood up and started talking about improvements on ecdsa and schnorr encryption or something... for no apparent reason. Then followed a bunch of pretty slides about the sharing economy... after which the CEO concluded with some vague speech about decentralized management of assets in a globalist world or whatever...

It was like a bunch of pretty smart people all had been locked up in some kind of closet with mirrors on the inside for six months, discussed their best ideas with their own reflections, then immediately grouped up and convinced an investor to fund their startup.

Ugh, I have to wash my ears and eyes with bleach. My brain is flooded with pretentious bullshit buzz and over the top startup decadence.

Actually, I think this sums it up best: There was a framed oil painting of the CEO with his dogs in the conference room, and the bathroom had a large marble Charizard statue watching me pee.

Feeling like I've gone back in time about 15 years!

Just told my CTO about various improvements we could make to the development process. Things like git, continuous delivery, agile project management apps such as Jira, task management such as Gulp, etc.

His response - "never heard of them. I bet they'll pass in a few months. Just another round of fads".

Exactly 10 years ago, my first job interview for a position as java developer:
Tech guy, asking me lot of deep questions about last java improvements, upgrades of newest web frameworks etc.
I answer very well.
He seems satisfied. He is about to leave, and just on the door, he turns and he asks this "just-one-more-question" in Lieutenant Columbo style:
"ehy do you know something about COBOL"?
Me: "well, ....yeees" (thinking: it's a programming language, only thing I know, plus I want the job)
He: "...and would you mind...." (some vague gestures)
Me: "...hmm...not at all..."

I got the job. All the project was about a huge legacy COBOL program. Almost no java.

I soon discovered that nobody inside the company wanted actually to deal with that project either....

Sometimes during interview you try to sell yourself, but it's actually the other way around, they are trying to sell something to you...

Solid improvements.

When you don't have new feature to add to the app but need to keep updates.

"General bug fixes and performance improvements."

When your team has no time to address technical debt/infrastructure improvements but we need to make that square checkbox round immediately.

So… I released v2.0.0 of devRant UWP a few weeks ago.
Then I got a lot of reports of problems on Windows 10 Mobile and older (than 1809) versions of Windows 10 on Desktop.
I decided to resubmit v2.0.0-beta16 to the store, and try to find the issue in the update… I didn't find it.
The code seems the same as the working version (at least the part I try to test is 100% equal).

So it seems I fucked up the vs project.

This means that to find the issue I can spend weeks to search it over and over inside the latest project (using shitty emulators of older Windows 10 builds to debug it), or I could just restore it to the old v2.0.0-beta16 (released in august) and implement again every single new feature and fix (something like 5 new features, dozens of improvements, changes and bug fixes).

In any case, this will require a lot of time (which I don't have at this moment).
I'm really sorry for this inconvenience, I know some of you use my client daily (~3.000 users I guess), I'm really glad someone likes it, and thanks a lot for the awesome reviews and feedback, but stable v2 (v2.1.0 at this point) will be available not earlier than in February.

Probably some of you have already download v2.0.0 while it was available in the store, and maybe it works on your device (please let me know in the comments below if you did, how is it going, and also if you like the new features and improvements).

After this epic fail, and more than 1 year (way too much) of v2 public beta, I want to throw the current project in the trash, and start it from scratch.
Which means I will start to work on v3 as soon as you will see v2.1.0 in the store, making it faster, lighter and with better support for the latest Windows 10 (Fluent Design and not) features, dropping the support for the very old UWP API.

Thanks for your attention.

Have a good day (or night)!

Facebook devs be like,
Today I'm gonna change a variable name and release a new app version.

Discord: Restart app for improvements
Improvements: Captcha added

The senior developer who's never had a smartphone in his life gave me a lecture on why my UI improvements to the mobile application were terrible and to revert them. He didn't want to hear squat from me, and was literally saying "You're not gonna win this" while I was trying to argue why these features were necessary.

1 month later, we get a Interaction Design expert to review the app. His recommendations were hardly surprising.

Except, now I have a tighter deadline and will work this weekend. Sigh.

Completed Angular 2 course on codeschool, really liked improvements and simplicity of Angular over Angularjs. Decided to do quick start guide in official website. Oh my f**king god... I need to setup webpack, typescript linter, typings, polyfills etc angular2-cli is no better, crawling with errors... why... why can't one just start a project and work instead spending loads of timing configuring all of that... AND WHY WE CANT HAVE PROPER SUPPORT FOR LATEST FEATURES...

I don't even know what I am ranting about... I just wish to spend more time creating things than configuring for ages development environment.

Worst CMS: Joomla.
Worst IDE: Eclipse.
Worst language: Python 2. (Python 3 brought many improvements to many annoyances there)

I fucking hate when I update my apps and they don't describe what they changed. Like the latest spotify update description:

We’re always making changes and improvements to Spotify. To make sure you don’t miss a thing, just keep your Updates turned on.

A) Create something that works, is fast, minimum bugs, have edge cases covered, nice testes, clean code. Cool, you did your job. END.

B) Create something shitty with bugs, performance issues, non or poor test coverage, mess code, etc. Cool, you did you job. But...

Next week you reduced bugs by 50%. Wow, you're rockstar.

Another week you improved performance by 15%. Again, you're the hero.

2 weeks later, you reached 85% test coverage. Management is so happy that almost got orgasm.

"A" took 3 months, "B" took 3 months plus few months of fixes. The only time where B was winning was first 4 weeks, where A was carefully building it's architecture and quality.

Yet B is seemed more successful.

This industry is F****d Up beyond my understanding.

Okay, windows, it's cool that you're getting a dark themed explorer and overall UWP-Fluent Design improvements but...

What's up with this context menu, which has a button saying "close [context] menu"?

(this is made up of screenshots, not a recording - the actual animation is much smoother)

Watch out for these fucking bug bounty idiots.

Some time back I got an email from one shortly after making a website live. Didn't find anything major and just ran a simple tool that can suggest security improvements simply loading the landing page for the site.

Might be useful for some people but not so much for me.

It's the same kind of security tool you can search for, run it and it mostly just checks things like HTTP headers. A harmless surface test. Was nice, polite and didn't demand anything but linked to their profile where you can give them some rep on a system that gamifies security bug hunting.

It's rendering services without being asked like when someone washes your windscreen while stopped at traffic but no demands and no real harm done. Spammed.

I had another one recently though that was a total disgrace.

"I'm a web security Analyst. My Job is to do penetration testing in websites to make them secure."
"While testing your site I found some critical vulnerabilities (bugs) in your site which need to be mitigated."
"If you have a bug bounty program, kindly let me know where I should report those issues."
"Waiting for response."

It immediately stands out that this person is asking for pay before disclosing vulnerabilities but this ends up being stupid on so many other levels.

The second thing that stands out is that he says he's doing a penetration test. This is illegal in most major countries. Even attempting to penetrate a system without consent is illegal.

In many cases if it's trivial or safe no harm no foul but in this case I take a look at what he's sending and he's really trying to hack the site. Sending all kinds of junk data and sending things to try to inject that if they did get through could cause damage or provide sensitive data such as trying SQL injects to get user data.

It doesn't matter the intent it's breaking criminal law and when there's the potential for damages that's serious.

It cannot be understated how unprofessional this is. Irrespective of intent, being a self proclaimed "whitehat" or "ethical hacker" if they test this on a site and some of the commands they sent my way had worked then that would have been a data breach.

These weren't commands to see if something was possible, they were commands to extract data. If some random person from Pakistan extracts sensitive data then that's a breach that has to be reported and disclosed to users with the potential for fines and other consequences.

The sad thing is looking at the logs he's doing it all manually. Copying and pasting extremely specific snippets into all the input boxes of hacked with nothing to do with the stack in use. He can't get that many hits that way.

I've always liked the idea of a virus that attacks other viruses. An antivirus virus, if you will. It would infect a computer and clean out all the malware and perform a bunch of random system improvements, then delete itself without a trace. To the end user, one day their computer would suddenly start running a little better for no apparent reason.

When I wasn’t the lead yet there are so many things I want to do and improve. I have asked and judged my lead’s choices a thousand times for choosing the easy and fast way instead of the right way.

Now that he left and his role was given to me, I can now sense the same judgements from my members to the decisions I make (or not make).
I now understand. We don’t always have the luxury of time. If I say yes to improving everything at once then our app will never be done. (That our bosses will blame me for)

I'm soooo glad that the Google Drive team isn't one of those that always puts "But fixes and performance improvements." 😒

Oh, this PHP thing is becoming big, we must use this; *makes ASP*

Oh, oh, this Java thing is really popular, and we're not the big bois now! *releases C#*

Waaait, functional is cool now? Damnit. Dude, grab this~~~ *F#*

Uhh. So people actually like JavaScript now? A wild *~~TypeScript~~* has appeared

Why does Microsoft have a history of following trends, and releasing poor clones with no substantial improvements??

My little drawing tablet is finally here! 😁

I have started drawing, but the improvements to my skills are gonna take a loooooooooong time.

Plus, I have a slow and old lappy available now... which freezes in the middle of drawing but oh well! Better than nothing! 🙂 Little improvements matter.

Today was a short exhausting relatively happy day. 🙃

Being a lead developer, I don't know if I am on the side of developers or managers.
In a product roadmap meet today, one of the developers explained the update of last week. He talked for at least 15 mins.
After that the sales lead looked at me, expecting me to explain (or basically dumb it down for her)
Me: Oh, he meant "UI improvements"
She: Oh, why didn't he say so?

I don't know who was the reason for the FacePalm 😐

I had the most depressing realization last night after I spent a good chunk of the day answering questions on Stack Overflow.

I can usually understand their code, I often understand their questions, and I know how to help and when to recommend that they completely change direction. I'm effectively trying to mentor total strangers using a few code samples and paragraphs. I'm happy to do that, and I'm good at it.

Then I realized - these people all have programming challenges of their own to solve. I work for a so-called "consulting" agency where I sit around for weeks because they have nowhere to put me. When they do find me a client it's some company that has no idea how to develop software and no interest in how I can help. They just want to add another developer into the giant mess they've created to keep doing what they're already doing. I'm still using any of the skills I put to work all day long helping people on Stack Overflow.

In other words, the people who need my help figuring out how to write code actually have the jobs writing code, and I don't. Clearly I'm doing something wrong.

Ironically, when I go to one of these companies with a lead developer who doesn't know how to write a unit test or put together three lines of coherent code, that person tells me to just follow what everyone else is doing without making any improvements. Then he goes on Stack Overflow to figure out how to do his job, and chances are I'm the one answering his questions.

As my wife always reminds me, I work in air conditioning so I shouldn't complain. It's a stable company with nice people and it pays the bills. But I sure would like to develop some software in my software development job instead of treating it like a personal hobby.

Just joined this Linux Development Team Xenta OS, it originated in my country, Im asking for a favor to check it out and seeing what needs improvements...

If you are curious and want to help out , check it out in 'xentaos.org'

Hello Google, I know you're watching.
There's still room for improvements in your search algorithm.
Sincerely, you know who I am.

My company has two offices in separate cities but they treat each the devs of each location very very differently.

In one office the devs get full power to experiment with whatever tech they want, they just stomp their feet and management gives em whatever they ask for, freedom of choice regarding anything they are working on, to be allowed to do greenfield work or experimental stuff

But in my office we are forced to do ONLY. Bug fixing and refactoring shitty code from over a decade a go, our tech is ancient and we are not allowed to to
Shit , anything we ask for is denied
And improvements to our process is shut down with the reasoning that whatever we got works so why meddle ??

For us , management is solely focussed on making sure we respond to support calls , deployments , configurations and little bug fixing. Basically they only care that we manage to finish for out next delivery.
No new work whatsoever!
If there is any hint of something new to to
Implemented the golden boys from the other office just stopm their feet tillmthey get it or just go off and start working on it then seek permission afterwards, with their much larger team they obviously get further than we do by the time management hears about it so they end up taking over the work since they already have more done already

My manager decided to push us to attend a company devCon to share ideas with our devs from our other location. This rapidly turned into a sour experience

Basically we do all shitty boring work which puts money on the table which goes straight to those idiots to play with...

They have the guts to laugh when we mentioned that we never get anything interesting to work on

Never seen so many of our devs looking up job sites on the bus back...
This is gonna blow up in management's face...

In an application that everyone in production floor used... I made some "improvements"... Next I know I get tons of tickets because is really slow... Like 20 minutes waiting and it doesn't load... I try with my user in their computers and it loads instantly... Puzzled... After trying in many computers my user loads instantly... Oops... I left a if(user = "me") skip all active directory checks 🙄... Made all production floor lose about 3 hours 😆 because I didn't believe 😛

During my first year of working, I was offered to work part-time at another company. I actually took it to my supervisor and asked for his advice.

He began with a sigh, he knows that I like programming so much and wants the job because I wanna do more programmings. He gathered his thoughts and said calmly, "Look, I cannot stop you if you want to, but think about this, you already are doing programming for five days a week here. Take those extra times you have to develop other parts of yourself. Go learn public speaking or something" or something along that line.

I gave it a deep thought, took the advice, and rejected the offer. I eventually went on to commit myself on volunteering for the next two and a half years, and secured a promotion about a year from that conversation because my supervisor sees improvements in my communications with others and my soft skills in general (unlike programming, you can't volunteer in an organisation without speaking to people).

Sometimes we programmers only wanna code that we forget that what we're building are for humans and involves other humans. You wanna be the best at work? Try to grow on your horizontal axis, too.

Taking care of your skin once a week, won't give you better skin.

Just like eating a healthy meal once a week, won't make you skinny.

Changes and improvements take time, effort, but most of all consistency.

Worst thing you've seen another dev do? Here is another.

Early into our eCommerce venture, we experienced the normal growing pains.

Part of the learning process was realizing in web development, you should only access data resources on an as-needed basis.

One business object on it's creation would populate db lookups, initialize business rule engines (calling the db), etc.

Initially, this design was fine, no one noticed anything until business started to grow and started to cause problems in other systems (classic scaling problems)

VP wanted a review of the code and recommendations before throwing hardware at the problem (which they already started to do).

Over a month, I started making some aggressive changes by streamlining SQL, moving initialization, and refactoring like a mad man.

Over all page loads were not really affected, but the back-end resources were almost back to pre-eCommerce levels.

The main web developer at the time was not amused and fought my changes as much as she could.

Couple months later the CEO was speaking to everyone about his experience at a trade show when another CEO was complementing him on the changes to our web site.
The site was must faster, pages loaded without any glitches, checkout actually worked the first time, etc.
CEO wanted to thank everyone involved etc..and so on.

About a week later the VP handed out 'Thank You' certificates for the entire web team (only 4 at the time, I was on another team). I was noticeably excluded (not that I cared about a stupid piece of paper, but they also got a pizza lunch...I was much more pissed about that). My boss went to find out what was going on.

MyBoss: "Well, turned out 'Sally' did make all the web site performance improvements."
Me: "Where have you been the past 3 months? 'Sally' is the one who fought all my improvements. All my improvements are still in the production code."
MyBoss: "I'm just the messenger. What would you like me to do? I can buy you a pizza if you want. The team already reviewed the code and they are the ones who gave her the credit."
Me: "That's crap. My comments are all over that code base. I put my initials, date, what I did, why, and what was improved. I put the actual performance improvement numbers in the code!"
MyBoss: "Yea? Weird. That is what 'Tom' said why 'Sally' was put in for a promotion. For her due diligence for documenting the improvements."
Me:"What!? No. Look...lets look at the code"

Open up the file...there it was...*her* initials...the date, what changed, performance improvement numbers, etc.

WTF!

I opened version control and saw that she made one change, the day *after* the CEO thanked everyone and replaced my initials with hers.

She knew the other devs would only look at the current code to see who made the improvements (not bother to look at the code-differences)

MyBoss: "Wow...that's dirty. Best to move on and forget about it. Let them have their little party. Let us grown ups keeping doing the important things."

Why are people complaining about debugging?
Oooh it’s so hard.
It’s so boring.
Can someone do this for me?

I honestly enjoy debugging and you should too..
if it’s not your code, you’ll get to understand the code better than the actual author. You’ll notice design improvements and that some of the code is not even needed. YOU LEARN!

If it’s your own code (I especially enjoy debugging my own code): it forces you to look at the problem from a different perspective. It makes you aware of potential other bugs your current solution might cause. Again, it makes you aware of flaws in the design. YOU LEARN!

And in either case, if it’s a tricky case, you’ll most likely stop debugging at some point, refactor the shit out of some 50-100 line methods and modulize it because the original code was undebuggable (<- made up a new word there) and continue debugging after that.

So many things I know, I know only because I spend days, sometimes even weeks debugging a piece code to find the fucking problem.

My main language is java and i wouldn’t have believed anyone who told me there’s a memory leak in my code. I mean, it’s java, right? We refactored the code and everything worked fine again. But I debugged the old version anyway and found bugs in Java (java 6.xx I believe?) which made me aware of the fact that languages have flaws as well.. GC has its flaws as well. So does docker and any other software..

Stop complaining, get on your ass and debug the shit out of your bugs instead of just writing it in a different way and being glad that it fixed the issue..

My opinion.

The Subtle Art of Not Giving a Fuck: A Counterintuitive Approach to Living a Good Life

I am not into motivation books but I was intrigued by a title.

Nice fucking book.
Found some improvements I can make in my life.

Author literally wrote he don’t give a fuck if you’re reading it or not.

older clients are returning with my old projects and asking for improvements, I did buy a few very shitty scripts from the internet/ and used one of my friends custom php cms for the other client because I REALLY needed money and they needed the projects yesterday.

Now I'm looking at the code and can't start working because of how messy it all is, I want to remake it all with a good framework and system, but it would take too much time (and they want it fast) and they wouldn't want to pay for the improvements because what they have now works..

I guess the shit you throw out when you're younger does come flying back like a boomerang..

In other news, I have been forbidden by my boss to implement any security or performance improvements into the company infrastructure as this holds no business value. Furthermore, passwords are not to be a random alphanumeric+special-chars string but something legible.

Fuck you google android IME team and fuck their open source policy..

So recently i had a chance to work with AOSP LatinIME code, basically our Android keyboard was forked from very old code base of LatinIME and my job was to change its base version to latest Version available on AOSP repository. Downloaded latest Android 8 codebase. Did 2 weeks of deep investigation of what improvements we will get from upgraded code base.

And I came to know that those Google fucking cunt sucking dick heads deprecated that project and broke the whole thing to a pice of shit. Half of the code is broken with fucked up todo stuff and motherfucking missing method implementation with not implemented warnings. What those motherfucker did is that they abandoned the open-source project after they released Google GBoard, and fucked the stable code by adding quard gram support and dictionary download with multi account features which was never completed by those motherfuckers..

Those misguiding donkey shit fuckers kept a depreciated project in AOSP build tree which has not received a single fucking commit from shitty ass Google IME team, is said to be reference model of Android IME implementation..

What kind of fucking shit is going with open-source code in name of making competition high with thirt party Android keyboard developers ..

Fucking shit fucking ime team .. fuck you .. wasted my fucking time reading your shitty code base .. Fucking shit

Can we please stop using continuous delivery on mobile. I don't want to update your app every other week just because you decided to change a comment.
Also Bugfixes and improvements doesn't say anything as a changelog!

People are so obsessed with apis nowadays that I was thinking about writing a rest api to get the amount of fucks that i want to give to the client whenever they ask for some change requests or improvements..

Soo, my manager asked me to create tool for CSI. Sort of ticketing tool for service improvements.

So I spent a few months working on it including design, websocket based real time statistics, exports to their belowed excel, easy to use, fast and so on.
I've presented it to mgmt, told them that deployment was easy and just need a simple linux virtual and all is automated.

They told me that they don't have a server. Company where main business is cloud services. Didn't pay me a penny for my effort even though worked on that mostly in my free time.
I didn't even want anything for the tool, just for my time.

Then a month later they've introduced similar thing based on Sharepoint with 1/10th of fuctionality, slow as hell, buggy, unintuitive.

And guess what, I can't open source my tool because it is a company property.

So, fuck it, never gonna do anything again without proper contract, even if for the same department.

I've already left that hell hole, but thought I would share my story.

Markdown's backticks on devRant ... ```holly ~~shit~~ crap``` that would be so ```cool```

Project in college, many moons ago.

Team is building a robot for a project. Nothing too crazy, it does some simple tasks like walk along a path and shit.

3 weeks for the project. 3 team members.

The largest graded part of the project is the ability to follow a path based on vision.

The 3rd member INSISTS on doing that part, he says “I want to prove to the professor that I am the smartest in the class so he helps me get a work term.”

Of course, my other partner and I see this as the complete selfishness of a child who will never be employed anywhere worth talking about anyways. He is a big asshole about it and we end up giving in.

## Week 1

We get our parts done (working together the way a team would) without his help.

He struggles, hits walls, complains. You know, dumbass grown child stuff...

## Week 2

We offer to help since we are done. He refuses. The teacher sees all of this and doesn’t like it at all.

After class the 2 of us go to the teacher and let him in on the details. The guy insisted, he is struggling and will not take help etc.

Teacher goes and talks to him and tells him it is a team project for a reason and that we should be helping. He says yes.

Then he misses the rest of the classes that week and send an email saying...

“Since everyone decided to keep interrupting me and breaking my train of thought, I could not get anything done in class. Therefore I will be staying home to finish the project from there.”

And to top it off, he didn’t even take home the robot’s connectors he needed to do the damn thing. Haha.

## Week 3

We know he wasn’t going to get it done, so we approached the teacher. We make it clear that we have done all we can and that we are not ok with losing marks because of this.

Since we are both good students that he likes, he decides to give us an option.

You can take a 50% on his part even if he doesn’t get it done (for trying to help) or we can do it ourselves and he won’t get the marks if he doesn’t finish.

## Night before

We say fuck it and do the thing.

In fact, since we were learning Java at the time we decided to do it in Java. Our other prof sees us playing with robots and gets excited, he stays with us and suggest improvements.

In the end we rewrite all 3 robot functionalities in Java and hand in the project the next day.

## The day of

Partner 3 comes into class and says this...

“That walking path part is impossible, I didn’t get it done, but I bet nobody else did either. So at least we will get a 60% on the other 2 parts!” (With a big shit eating grin)

Prof calls our group up. We walk up and the prof looks at the 3rd guy and says.

“Since you have decided to do your part alone, we will have you present your part alone at the end of the groups”

He tries to say something but the prof cuts him off and tells him to sit down.

We show all of our code and the robot does everything perfectly.

Groups go by, now it’s that guys turn.

He says that the walking part was impossible but seems to realize right away that he just saw EVERY other group get it working.

The teacher ask him to stay after class.

## Result

We got a 98 (prof said he was hoping we would have done in VB like asked but he liked the result a lot).

Other guy gets a 5% for his non-working spaghetti code on 0s on the other 2 sections. He blames us, of course.

Bonus Content:

That same asshat above once said this to me...

“I don’t indent my code so that if I work for a company and no one else can understand the code then I am unfireable!”

Yes, he wrote all code like this...

const Example = () => {
Stuff
More stuff
For() {
Stuff
If() {
Stuff
}
}
}

Fuck that guy🖕🏽

Noticed a new version of our primary customer management application was deployed to my machine. Its been a while since I've seen it, so I decide to see all the 'improvements' over the 'old' one (~18 year old app written in Delphi).

Wow, it's slow, several seconds to open. Tried to open my account..really, really slow.

Notice a lonely edit box with no label, and button right next to it with no caption, so I click it and get the attached error.

Tried to place an order, I must have done something 'out of sequence' because I clicked another button and the whole app crashed.

In less than 5 minutes I found a dozen or so UX failures. I suck pretty bad at UI, but good lord...what the frack happened to basic usability.

I was just writing a long rant about how my rant style changed, and how I could fix anything that annoys me in a heartbeat by just putting my mind to implementing a change. Then YouTube once again paused the synth mix that was playing on my laptop in the background, with that stupid "Video paused. Continue watching?" pop-up. I even installed an add-on for it in Firefox to make it automatically click that away. I guess that YouTube did yet another bullshit update to break that, for "totally legitimate user interface improvements" or whatever. Youtube-dl faces similar challenges all the time, and it's definitely not alone in that either. I also had issues with that on Facebook when I wanted to develop on top of that, where the UI changes every other day and the API even changes every other week. And as far as backwards compatibility goes, our way or the highway!

So I did the whole "replace and move on" type of thing. I use youtube-dl often now to get my content off YouTube into a media player that doesn't fuck me over for stupid reasons like "ad fraud" (I use an ad blocker you twats, what ads am I gonna fraud against), or "battery savings" (the damn laptop is plugged in and fully topped up for fucks sake, and you do this crap even on desktop computers). Gee I wonder why creators are moving on to Floatplane and Nebula nowadays, and why people like yours truly use "highly illegal" youtube-dl. Oh and thank you for putting me in Saudi Arabia again. Pinnacle of data mining, machine learning and other such wank could not do GeoIP. for a server that used to be in a datacenter in Italy for years, and recently has been moved to another hosting provider in Germany. It's about as unchanging and static, and as easy to geolocate as you can possibly get. But hey, kill off another Google+ when?

Like seriously, yes I'm taking your Foobar challenges and you may very well be the company I end up working for. But if anything it feels like there's a shitton of stuff to fix. And the challenges themselves still using Python 2.7 honestly feels like the seldom seen tip of the iceberg.

If you dish out the same shit you inherited from your senior colleagues onto your juniors, you have just successfully become the part of an ongoing shit show.

Be kind and supportive. Earn their trust, be approachable. Listen to them and help them learn to solve problems. Give constructive feedbacks, not harsh criticisms. Point out room for improvements, not belittle someone. Be that mentor/teacher you wish you had.

Learn. Build. Teach. Grow

Today, Linux kernel 5.8 was released, here is how it runs on my new laptop.

- Realtek shit ethernet still doesn't work (no, I didn't return it, because I would have to buy at least 2 times as expensive docking station instead and it is just not worth it), but considering Realtek, it is probably not a Linux kernel issue
- Battery life while watching videos was improved pretty significantly from 6.5 hours to about 7.3 hours (1080p HEVC)
- All temperature sensors are now working correctly
- Fan is a little more silent overall, probably because of some power draw improvements
- Subjectively, the system is a little bit more responsive overall

Still on the primenumbers bender.
Had this idea that if there were subtle correlations between a sufficiently large set of identities and the digits of a prime number, the best way to find it would be to automate the search.

And thats just what I did.

I started with trace matrices.
I actually didn't expect much of it. I was hoping I'd at least get lucky with a few chance coincidences.

My first tests failed miserably. Eight percent here, 10% there. "I might as well just pick a number out of a hat!" I thought.

I scaled it way back and asked if it was possible to predict *just* the first digit of either of the prime factors.

That also failed. Prediction rates were low still. Like 0.08-0.15.

So I automated *that*.

After a couple days of on-and-off again semi-automated searching I stumbled on it.

[1144, 827, 326, 1184, -1, -1, -1, -1]

That little sequence is a series of identities representing different values derived from a randomly generated product.

Each slots into a trace matrice. The results of which predict the first digit of one of our factors, with a 83.2% accuracy even after 10k runs, and rising higher with the number of trials.

It's not much, but I was kind of proud of it.

I'm pushing for finding 90%+ now.

Some improvements include using a different sort of operation to generate results. Or logging all results and finding the digit within each result thats *most* likely to predict our targets, across all results. (right now I just take the digit in the ones column, which works but is an arbitrary decision on my part).

Theres also the fact that it's trivial to correctly guess the digit 25% of the time, simply by guessing 1, 3, 7, or 9, because all primes, except for 2, end in one of these four.

I have also yet to find a trace with a specific bias for predicting either the smaller of two unique factors *or* the larger. But I haven't really looked for one either.

I still need to write a generate that takes specific traces, and lets me mutate some of the values, to push them towards certain 'fitness' levels.
This would be useful not just for very high predictions, but to find traces with very *low* predictions.

Why? Because it would actually allow for the *elimination* of possible digits, much like sudoku, from a given place value in a predicted factor.

I don't know if any of this will even end up working past the first digit. But splitting the odds, between the two unique factors of a prime product, and getting 40+% chance of guessing correctly, isn't too bad I think for a total amateur.

Far cry from a couple years ago claiming I broke prime factorization. People still haven't forgiven me for that, lol.

What do y’all think about the new Raspberry pi with that 4GB of RAM. Other good improvements too, but that’s what I’m most excited about

*The week after php7 has been released*
Customer: we could replace php5 with php7 to increase performance of the entire application!
Me: of course, let's do this 1 day before going live, I'm sure you'll see great improvements -_-

I hate touching my keyboard when I eat... I usually put some video to watch and start eating. But every single time it goes like this:

Me: "Finally finish that piece of code, time to cook some food!"

*After cooking and back in front of my screen ready to enjoy the next episode of my favorite show*

Brain: "Wtf are you doing! You have better things to do than watching this garbage! Like implementing all 101 improvements you thought about while cooking!"

My coworker is a grade A super badass.
He work as a consultant and is only on site 2 days a week. He wasnt here on tuesday but got in today, first thing he did was starting to complain about some improvements we made during the week. Next he decided to remove and destroy parts of our software and check in his "improvements". Then without telling anyone about his changes he went home after lunch.

What a legend.

When you just fix some bugs and add little improvements, but you want to announce it with style

Is anyone else get irritated while upgrading apps and seeing changelogs as:
1. minor improvements
2. performance boost
3. information not provided by the dev
4. repeating changelogs from the past few updates.

just tell me what minor improvement u fixed?
where performance is boost?
how can I trust if tomorrow you decide to add some malicious code.

I don't know but it really irritates me. Sometimes I don't even upgrade the app until they have something in the changelog.

Maybe because I am getting old now.

The new devRant vote info is great! Improvements like this is one reason we all love devRant! Thanks devRant team for implementing this.

Everyone in the gaming internet talking about how Microsoft's Activision Blizzard purchase will usher in a new age of improvements have never had to use teams.

A big, fat FUCK YOU to everyone who pushes out app-updates with generic "Improvements for speed and reliability" changelogs. I hope you and all your descendants, relatives, friends and pets get huge, hairy, painful warts between your buttcheeks that grow larger every day and return after every attempt to have them removed. Fuck you, and fuck your bullshit updates.

And if there are any devs on devRant guilty of this behaviour, fuck you too. I hope your sexual organs rot and fall off, and that you lose all your upvotes.

My latest attempt to improve myself as a dev has been learning front end technologies, or as I prefer to call it, throwing heaps of shit at a wall and seeing what sticks and calling it modern design. Fuckers.

Otherwise I usually try to implement small manageable side projects to learn new tools enough to know what they are good for so if I ever do need them I know what to choose.

me to dba: do you have any recommendations of sql or query improvements? dba: no, just let us know once you're done.

after sending them explain plans, new queries and asking for reviews with no response from them, i applied the changes in dev.

after applying changes.

dba: you should involve us in any development. we need to collaborate.

me: please check your emails over the past 3 weeks.

wtactualfuck.

Video game graphics have peaked. It absolutely has. It's gotten to a stage where 500% extra effort would result in 5% improvement which is not worth it imo.

We have games that were released in 2010's which still hold up to today's standards.

If every game company could fucking stop with the graphics improvements and actually work on building bangers to play and have fun with, that'd be great.

I have such little patience for the whole fucking “let’s just do it later” mentality anymore. Especially when it takes like 30 minutes or less to fix. Then a month goes by and everyone suffers from it not being fixed. Like I understand why they do so and why it’s important to just do the task. I understand there’s often no time to make huge improvements, but if you have time and you see a small thing that can be fixed, make improvements you silly little bump-on-a-log. Like have a little empathy for your comrades goddamnit.

devRant app should be Open Source for us to help in the development

I think A LOT of us would try to bring ideas and improvements to the app and service overall :)

Upgraded from a gen 6 motherboard and cpu to a gen 11. And the difference is asounding.

My old setup did everything I needed it to pretty well. Hell it got me through college as well as multiple part time and full time jobs. As well as the system that I learned about 80% of what I know specifically for my career

But alas the old cpu's age started showing and I'd consistently throttle multiple threads when compiling or even just using 7z on large folders. Hell deleting anything above a couple hundred mb would pause for a few seconds

The new cpu is immensely faster on such tasks (probably cause of the extra 2 cores and cpu improvements since gen 6)

I haven't been this excited since I got my first SSD a few years ago and saw the immense boot time improvements. Maybe soon I'll get an nvme drive and really be zooming with this setup 🤣🤣🤣

So I was assigned to improve an existing internal CMS application where they wanted the ability to add extra form applications and restricting them based on people from different departments. As well as include some other improvements like speed as they mentioned that it was slow in some instances.

What I found was the original developer decided to not use any kind of framework and decided to be creative by creating his own MVC framework. With about 300 users in this system and utilising no caching of queries, views, not even using PHP OpCache, even quite a few security holes, I was damn surprised at how this thing was running. I asked the original developer why he didn't use an open source framework and he said that he thought that he'd create something and be the next Facebook.

It was a mammoth task to "improve" this system but the main thing was that I took custody of this project and that I prevented him from trying to make a bigger mess of things for this project.

TL;DR: I hate how management doesn't listen to devs (even Dev managers).

We need to sort out our release process where I'm at. It takes a Dev about 2 solid days to complete and it's hideously involved and ripe for human error. They're completely out of action until it's done and it happens once a week!

It's stopping us releasing business critical bug fixes and features that need to go out. Instead the work just sits in develop for days doing fuck all.
Can't be agile if it takes so long to deliver value 🙃

Plus makes any fuck ups by our department look worse as it takes an age until it's fixed which reduces their collective trust in us and our opinions.
Making any improvements we want to make harder todo as they're harder to convince 🙃

Has anyone had any success getting automated releases?
How did you convince management to prioritise it?

I need to convince someone who has some influence in my company and ask how they got that influence

Holy shit, my first freelance project will be field-tested for the first time tomorrow!

After a few more rounds of fixing bugs, some serious improvements, and some new features additions, I can actually say that I'm proud of the code I've written! It's not perfect, but I definitely like the way it works - AND IT ACTUALLY WORKS!

Knock on wood, hopefully it won't shit the bed tomorrow.

As a developer I have a problem I have to get over and it's called: negative spiral thinking. It's the biggest impediment to progress (that and bureaucracy).

You sit there facing a problem, you keep focusing on the problem, but the problem spouts other problems and then you care too much about those other problems and you start fussing around, negative thoughts start to spout everywhere and you end up continuously losing your focus.

Blah.

I am in a situation where I am tired to give suggestions or implement any improvements to the company's app. I am in a situation where I will just do as told, nothing more, nothing less.

Regardless of how many suggestions or improvements I had made, the boss is constantly sceptically asking for "BLACK AND WHITE " proof. Sometimes, something does not require proof but cause and effect. As the application constantly prompts a DataType issue, which is a common bug in this app! I declare datatype the issue went away.

I wonder how this application can go further when they declare every variable as `var`, not using `const` for constant value, and redundant methods everywhere, most methods are not specific (in dart when you do not specify the method, the method become `dynamic`), a long list of nested if-else for something can be easily solved with switch case, etc.

So, today, right now, I will revert every improvement, and keep the original structure. If anything goes wrong, I know why it happens (deep down I will say "I told you so"). I am here to work for food, not to reinvent the wheel.

I'm so exhausted to the point where I will just go along and tell my co-worker "as you wish"

No more me suggesting.
No more me giving ideas.
No more me pointing the mistakes .

I will let them find out themselves is much better than I say it, just to prevent getting unnecessary hatred from them.

The best punishment to give somebody is to never mention their mistake let their ego do the job of consuming them into ignorance and asleep, and never wake them up. Let them commit the same mistakes repetitively until them realised there's no way to revert.

So, i helped solving 168 bugs for this website. Ofcourse, doubting every step since i'm still new here. Yesterday there was a meeting with the directors. Appearently they where happy a graded the site with a 8.5.
I finished my education with a 6. Not taking credit for any of the above...

Don't forget to give the developers the opportunity to innovate. Nobody wants to sit and type out the same structures day after day. That's not why we got into this job. We like solving problems. In my current team we set aside some time every sprint to spend on individual innovation. Super useful as it gives us the chance to break out from the standard chugging of the backlog and spend some time trying to solve some of the trickier problems and bringing improvements back to the product that we discovered by messing around with stuff. If you are reading this and you are in charge of a development team, try this out for a sprint or 2.

so, me and my best friend started playing pen and paper and after a wile we decided to create our own system. After a year of improving and testing we thaugth about a new java side project and more improvements for our system. time goes by and now we have three java apps for our own pen and paper and a lot of reusabilly code.

Playing and planing a new session of p&p is now so comfortable and fast 🤗

!rant

I had a talk with my manager about my future role in the company. I had talked with him before about my interest to dive deeper in the technical side - rather than the business side, for which we have a higher dev demand.

The outcome is that I will work more closely with the senior devs on technical improvements and also tech strategy (e.g. implementation of code reviews). I will also advise the upcoming manager of the development team (who is coming from a PM position) on technical decisions. Lastly the roadmap for the company is to work more with cloud technology (azure), which is also going to be in my new duties.

I'm looking forward to these new challenges where I can improve myself on the technical side (yay!) rather than on the business side (which bored me).

Publishing stuff and receiving feedback and improvement ideas is sush a great feeling. A guy opend an issue today asking for a feature to be implemented and he was very polite. Thanking me for my work.

This is way better than money. Money can't buy that feeling. People like this guy is the reason open source stuff lives.

In This Rant: A mildly satisfying piece of mind story.

Using code to prove yourself right is a hell of a drug.

A few weeks ago I whipped up a tiny program that downloads configs from hardware we manage. Since the vendor's API documentation is hidden behind a pay wall, my method of extraction is different. It results in bigger files, but testing showed it to still be valid.

Enter today. Interns at work downloaded a config to load onto a spare machine and it won't work.

"TheCapeGreek, your configs don't work"

I was confused since I tested the files when I built it and it worked. I am also currently fleshing out that download utility's features so the fear that I've been wasting the past 2 weeks on improvements is looming.

Last 15 minutes of the day and nothing else to do so I figured I might as well whip up a string comparer. The smaller file's content is scattered in the big file so a direct diff won't work.

Code it all, quick hardcoded proof of concept code, bit it got the job done. I was right, my bigger file is still correct!

Turns out the issue was with the machine they were configuring. They found this out before I finished my test code, so I'm off the hook already, but it was good to have piece of mind haha!

Firefox is getting better and better!
The improvements that came with 57 and Quantum were awesome! And now with 58 there are mayor performance improvements like Off-Main-Thread Painting and a new Javascript caching.
There are even some nice new features like the screenshot tool (in 58 available for the private mode, too!) that are really exciting.
I am looking forward that Firefox could maybe become again what it was back then! It's so cool!

Devrant should have a feature to unsubscribe notifications on a rant + notifications should say from which rant it came from. These would be much appreciated improvements.

As expected, I take a single day of PTO and I get a whole bunch of emails about stakeholders needing help and requests for website improvements. I have 14 days of PTO that I have to use in the next two months, so stakeholders gonna get a rude surprise when they see my out of office response almost every other day.

As a student, I live in a house with friends and the actual didn't have a table in my room.
So after one month waiting for a answer of the owner I decided to buy one in second hand. All I can say is that I love it.
Any suggestions to some improvements?

PS: external drive is only temporary

I'm just attending an online conference of a big, global company. They are redesigning their internal websites and going through all the improvements. Just then a question pops up in chat:

"Will we be able to insert moving gif files into the new sites?"

Sheeeeeesh, 1990 feelings...

I just finished reading the last chapter of the DevOps Handbook, its an eye opener, but not an easy read. And still recommended.

I've been reading this book for the past year and a half, little by little. It was hard since I started understanding why my work was so frustrating (I'm in System-Cloud-Ops position). The book made sense, while the work did not, it got harder since the book provides solutions, but whenever I dicussed any solutions with management they dismissed everything.
I started to initiate improvements by myself:
Prioritizing tasks I thought were more important to improve the way of work - do now and ask questions later... I got yelled at, I got my managers angry, but afterwards more often then not they admitted I was right.
To make it possible I worked overtime and on weekends, trying to prove a better way is possible, by implementing a long term solutions to solve problems instead of workarounds, automating a lot of stuff, creating labs, preparing presentations and documentation.
Time and time again I tried to pitch more ideas related to DevOps but the managers didn't care...
I know now my burnout started 8 months ago slowly, my hairline started receding, I started clenching my teeth (the doctor said stress was the cause) which was very fainful.
I continued to work but I noticed I was also more cynical, frustrated, and tired.

In the process I neglected myself.
So finally after 2 years and a half I quit my job, to focus on myself, at least for a little while.
I hope in my next job will be better.

It's over.

I've been working on you for months, and thinking about you for near a year.
I built you with a shitty language first and some crappy ideas. I obviously got bad results, but I didn't lose courage and I continued you.
Got near the obsession to improve you. Every time. Switched to a fast but hard language. Got into my first low-level fuss. All for you.

Now I reached the end with no more improvements and tweaks I could imagine, I can tell that:

I had a lot of expectations from you.

But turns out you were nothing more than a nasty brain fart pretending to be a good idea.

The core of the concept was rotten. Blinded by my lust for success (perhaps cupidity ?) I didn't see you just couldn't work.
I'm utterly disgusted, of course. Who wouldn't, after working so hard on something that looks right but is completely useless ?

But even though this was all in vain, you taught me some great lessons down the road.
Efficiency matters over facility.
Get sure you're using the right tools, and stay open for changes of such.

But some others were harsher, though just as important.
There's times you just have to admit defeat.
Putting a lot of efforts into something doesn't always bring a reward.
If after a long time you can't get the thing right, then stop. Your time is precious. Don't waste your time or time will waste you (Thanks Muse, I love this sentence).

And the most important: next time I got some "grand" idea that is not about improving some random software, I'll bang my head to my desk enough times to forget about it.

So now the time has come.

Goodbye, project "hpym". You put me in grief, but I know I matured a lot in my concepts of development because of you.
Now take place into the project graveyard among the other clunky half-assed shit I got rid off.

I was away from devRant for more than six months. It is good to be back. How I missed this!

Just spent hour browsing through the rants. So refreshing. Also so many improvements and new features to devRant, developers are busy.

Fucking SalesForce.. Nothing worse than spending hours figuring out what precisely you need only to find yourself on a "success" labeled rant platform where a customer rep acknowledges the problem and promises improvements....... 4 years ago

I’m studying at uni remotely at the moment. I’m taking a software engineering class. I love developing software so I was super excited about this course. First assignment is to make a tic tac toe game in python. I finish the assignment super fast within the first hour of our first class.

We end up spending the rest of the fucking semester on this fucking program. No improvements, nothing. Literally just staring at this less than 200 line command line tic tac toe game talking about the same fucking shit every class.

Our fucking final is a presentation about this fucking program. The entire class is going to present the same command line python tic tac toe game

People told me that in the past, this class would find a local client and fulfill a request (making a website, etc)

However, now there’s a new prof teaching this course.

Best way I can describe it, 3 hours of this fucking prof screen sharing a google doc and droning on for 3 hours

I wish I could get the 20+ hours of my life back that this course has taken from me

¡rant|rant

Nice to do some refactoring of the whole data access layer of our core logistics software, let me tell an story.

The project is around 80k lines of code, with a lot of integrations with an ERP system and an sql database.

The ERP system is old, shitty api for it also, only static methods through an wrapper to an c++ library

imagine an order table.

To access an order, you would first need to open the database by calling Api.Open(...file paths) (yes, it's an fucking flat file type database)

Now the database is open, now you would open the orders table with method Api.Table(int tableId) and in return you would get an integer value, the pointer.

Now for the actual order. first you need to search for it by setting the search parameter to the column ID of the order number while checking all calls for some BS error code

Api.SetInt(int pointer, int column, int query Value)
Then call the find method.

Api.Find(int pointer)

Then to top this shitcake of an api of: if it doesn't find your shit it will use the "close enough" method of search.

And now to read a singe string 😑

First you will look in the outdated and incorrect documentation given to you from the devil himself and look for the column ID to find the length of the column.

Then you create a string variable with ALL FUCKING SPACES.

Now you call the Api.GetStr(int pointer, int column, ref string emptyString, int length)

Now you have passed your poor string to the api's demon orgy by reference.

Then some more BS error code checking.

Now you have read an string value 😀

Now keep in mind to repeat these steps for all 300+ columns in the order table.

News from the creators: SQL server? yes, sql is good so everything will be better?

Now imagine the poor developers that got tasked to convert this shitcake to use a MS SQL server, that they did.

Now I can honestly say that I found the best SQL server benchmark tool. This sucker creams out just above ~105K sql statements per second on peak and ~15K per second for 1.5 second to read an order. 1.5 second to read less than 4 fucking kilobytes!

Right at that moment I released that our software would grind to an fucking halt before even thinking about starting it. And that me & myself and I would be tasked to fix it.

4 months later and two weeks until functional beta, here I am. We created our own api with the SQL server 😀

And the outcome of all this...

Fixes bugs older than a year, Forces rewriting part of code base. Forces removal of dirty fixes. allows proper unit and integration testing and even database testing with snapshot feature.

The whole ERP system could be replaced with ~10 lines of code (provided same relational structure) on the application while adding it to our own API library.

Best part is probably the performance improvements 😀. Up to 4500 times faster and 60 times less memory usage also with only managed memory.

Our new project is a responsive mobile-first web system coded with HTML, CSS, jQuery and AJAX that connects to MySQL, but the main tasks runs trough a huge application written in Visual FoxPro, per client request...the web version could manage the whole business but no, it has to be Fox.
Oh, and it's the version 6, not even using the latest version 9 with all it's "improvements". What are we, back to the past milleniun?

!rant
Improvements for devRant

Add markdown support.
Change ++ -- button's color. (they look like they are disabled)

More probably coming soon

@dfox @trogus

Swear work is where you I go to fix other peoples poor design decisions and clean up the bullshit that comes out of said decisions.

CANT!
BE!
FUCKED!

How you have so many years experience and still design in way that ensures that maintenance /improvements/touching in the future is a huuugggeee clusterfuck.

Hey, I got an idea, lets make this whole data warehouse without a single index or primary key cos you know, that's the Kimball Method.

Hey fellas,

So, our company is taking up some consulting projects to survive this pandemic since our main business is a little down. I've been assigned to a RN project and the client company has 2 other devs. Those devs are so incompetent that they don't even know the basics of JS and RN. They don't even understand how to split code into components and make it resusable. Okay, fine they must be new devs. I get it but can't you even fucking follow the instructions and guidelines that I'm giving you!! The code is very bad with a lot of pitfalls. In the first 2 weeks I reviewed all the code they were writing and gave comments for improvements. They didn't even care to do that! Now I've given up!

Every single day looking at the codebase makes me sick and not want to touch anything. I've practically started hating the project. How do I deal with this situation? Now, we are reaching the deadline and they're piling up the work on me. Any suggestions on how to handle this?

Thanks!

P.S: This is my first actual rant!

Why is there always one asshole!

New job just a month in, had a meeting where we could bring up improvements and put them on cards.

I brought up the idea of using slack so we could collaborate better or maybe a collab space. We all have our own offices or share with high walls.

The guy running the meeting has the same title as me said we never had that before, are you unhappy with yiur onboarding?

Slack or a messaging app is industry standard for even none tech companies. I was polite and said it was just a suggestion and it might make it easier to get help for the new people if there is a group chat.

Also brought up using a formatting standard so code reviews are spent commenting on spacing. I said we could you prettier to implement that and just pick a standard.

He said that was an issue because people were not paying attention before they pushed the code.

I am sorry I am new so I am rewriting and rewriting code all the time. I was to format on save and not spend time fucking formatting!

I could use a package before since it I formatted it would look like a bunch of fucking changes in git.

Why make things harder? Part of the meeting was how to get code done and PR’ed faster so it gets to the testers. Autoformatting shit would help.

Don't you just love it, when Windows lovers community just throws user's concerns and issues right back into their faces? "it works for me!" they say.

On the other hand, Linux sucks. (because it still got a lot of room for improvements!)

Seriously, we need better OSs.

You had two additional weeks to improve your project.

You could research different marketing strategies to increase revenue. You could add some new features to attract more users and ensure your existing users are satisfied. Finally, you could optimize performance to make your UI quicker.

But you’ve chosen to write some unit tests. Now that two weeks are gone, you got no new features, no performance improvements and no new marketing strategies while your competitors got them all.

Tests caught obvious bugs that can even be caught by static typing, but you by definition couldn’t write tests that’ll catch unpredictable bugs, so they are still present.

After six months you realize you have to rewrite a major part of your project because your project (surprise-surprise) has to chase market needs to stay relevant. Your tests are thrown into trash along with your old code.

“Having trouble with code quality? Write a lot of tests. And I mean a *lot*. Test every file in isolation. Mock as many imports as possible.

When you're done, your code will still be bad, but now your tests will make sure it's impossible to improve anything in any meaningful way.”

When I first started reading about Angular 4 I must admit I was a bit excited. It seemed like it fit the company enterprise requirements. The improvements it offered on paper looked quite good for our use case. HOWEVER... After writing Angular 4 for two weeks I'm seriously doubting I made the right decision. Testing is a dependency hell and there are two ways to build and structure your application. The webpack way and the SystemJS way. The grunt way and the angular-cli way. For fuck sake Google. And the documentation is somewhat half supporting one thing, half supporting another. So when you're using angular-cli with webpack, you're pretty much screwed when we're talking about documentation. It has now taken me almost 50 hours to write a pretty basic Angular app, made it compliant with our staging environment and writing a Makefile for it, since I haven't been able to find any same way to provide custom arguments when building it with the angular-cli --aot option. So fuck you Google. Luckily I've found a way to modularize it so much that I'll be able to reuse the core in the future. So I guess I got that thing going for me, which is nice... -.-' *sigh*

We use at our company one of the largest Python ORM and dont code ourselfs on it, event tough I can code. Its some special contract which our General Manager made, before we as Devs where in the Project and everything is provided from the external Company as Service. The Servers are in our own Datacenter, but we dont have access.

We have our Consultants (Project Manager) as payd hires and they got their own Devs.

Im in lead of Code Reviews and Interfaces. Also Im in the "Run" Team, which observes, debuggs and keeps the System alive as 3rd-Level (Application Managers).

What Im trying to achieve is going away from legacy .csv/sftp connections to RestAPI and on large Datasets GraphQL. Before I was on the Project, they build really crappy Interfaces.

Before I joined the Project in my Company, I was a Dev for a couple of Finance Applications and Webservices, where I also did coding on Business critical Applications with high demand Scaling.

So forth, I was moved by my Boss over to the Project because it wasn't doing so well and they needed our own Devs on it.

Alot of Issues/Mistakes I identified in the Software:
- Lots of Code Bugs
- Missing Process Logic
- No Lifecycle
- Very fast growing Database
- A lot of Bad Practices

Since my switch I fixed alot of bugs, was the man of the hour for fixing major Incidents and so on so forth. A lot of improvements have been made. Also the Team Spirit of 15+ People inside the Project became better, because they could consult me for solutions/problems.

But damn I hate our Consultants. We pay them and I need to sketch the concepts, they are to dumb for it. They dont understand Rest or APIs in general, I need to teach them alot about Best Practices and how to Code an API. Then they question everything and bring out a crooked flawed prototype back to me.

WE F* PAY THEM FOR BULLCRAP! THEY DONT EVEN WRITE DOCUMENTATION, THEY ARE SO LAZY!

I even had a Meeting with the main Consultant about Performance Problems and how we should approach it from a technical side and Process side. The Software is Core Business relevant and its running over 3 Years. He just argumented around the Problem and didnt provide solutions.

I confronted our General Manager a couple of times with this, but since 3 Years its going on and on.

Im happy with my Team and Boss, they have my back and I love my Job, but dealing with these Nutjobs of Consultants is draining my nerves/energy.

Im really am at my wits end how to deal with this anymore? Been pulling trough since 1 year. I wanna stay at my company because everything else besides the Nutjob Consultants is great.

I told my Boss about it a couple of times and she agrees with me, but the General Manager doesnt let go of these Consultants.

Even when they fuck up hard and crash production, they fucking Bill us... It's their fault :(

Fine! If I’m not allowed to make improvements to the site, I’ll blatantly write you shitty code and continue to fuck you over for the future. I tried to help but you guys are fucked.

Asciidoc! I finally got around to play around with it and it is just so awesome! Best tool for documentation hands down! So many improvements over Markdown:

- importing real code snippets based on tags with syntax highlighting and annotations (which can be also auto numbered with "<.>" instead of "<1>"!)
- Admotions! Love them!
- automatic TOC! Finally!!
- joining a child item to a parent item in a list with "+" in a new line (this one took me a while to understand, but no more offset items in lists! Love it!)
- making tables and loading data from an actual CSV-file! The future is now!!
- embedding images with a fixed size

Just a few things from the top of my head. I don't know why I put up with vanilla Markdown all these years...

Last but not least, a big THANK YOU to everyone who recommended Asciidoc! I accidentally stumbled across multiple mentions of Asciidoc a few months ago. Sorry, but you know who you are! Much love to you and your loved ones! You changed my life for the better. Thank you!

Manager brings up an idea, asks how long it would take to build out. I tell him a couple hours. I can be nice sometimes when the workload is light.

Build it out, make some improvements at home, create a dashboard so he can make small configuration changes.

We never use it.

So I've been writing code for 2 months to implement the GAN for a research paper that I'm writing, and I'm slowly becoming paranoid.

IN THEORY my idea should work. BUT WHAT IF there's some bug in my code that's preventing it from actually doing so. I'm tired of having to wait for days to see some minuscule training improvements...

I swear to god, I'll blame it on the documentation. >D

We have trello all set up and have been using it for ages. Stop sending me Google slide presentations for bug reports or ui improvements.

What are some of your Linux desktop preferences and workflow improvements?

I use Mutate for app launching, DDG searches, and a dozen or so scripts I wrote myself.

I like different URLs to open in specific browsers, so I wrote a script called xhttp that determines which browser to open with URL regexes, and used freedesktop to register it as a browser, and set it as my default.

Anything fun you've done?

At the job interview to my current position I was asked the classic ”where do you see yourself in X years” question. I replied something along the lines of that I see myself staying if I feel good where I am and long as I have the opportunities for professional growth.

Now with recent developments it’s looking like those opportunities will be bygone pretty soon. I work on a massive legacy codebase, where with the scarcity of current dev resources and the apparent difficulties of procuring additional personnel to the dev dept, it does look like we’ll be limited to maintenance and simple small scale improvements with no room for meaningful projects. Theoretically I could ask to be moved to another product, but realistically that would both be a dick move well as unlikely to happen, as other projects are fully staffed (and made with technologies there’s easier to find personnel to).

As a consequence of this perceived imminent halt in opportunities for self-development at work, I’ve been starting to look for greener pastures. There are some intriguing ones out there. But then I come here, read some rants and comments, and it always becomes abundantly clear I’m good where I’m at right now. So what of it, if my position won’t enable growth out of the box for a while? I can always develop my skills and knowledge on my free time, and besides, the stagnation won’t last forever... right?

"The Phoenix project" alternative ending:

Bill Palmer manages to avert disaster with heroic efforts, working 18 hours per day for weeks.
His wife files for divorce. He starts to sleep at office, next to the servers room.
At the last moment a huge hacker attack almost destroys everything, but he finally manages to announce that Phoenix is ready on time, security auditing passed and any kind of great improvements.

Steve, the CEO, calls him and says: "are you crazy? we put you on an impossible project with short notice to make you fail! All our investors have been secretly short selling our stocks, so now they are waiting a big failure to cash in. We also paid korean hackers to bring you on your knees. But you are really stubborn! "

All Phoenix Project is rolled back, huge shit happens, stocks fall, investors ripe great benefits. All IT is outsourced to an external company (owned by members of the board)

Bill is fired. His reputation tainted by the failure, he can't find job anymore. his technical skills and knowledge are out of date.
As he didn't have time to take care of divorce he has lost also all his personal wealth.

He writes a book about his experience, well, actually a rant, but the company sues him forcing him to pay more money.

In the final scene, police arrests him, drunk while trying to burn a server farm with matches.

No I don't want your updates every single day, Windows 10. Maybe I don't want to be so edgy with your updates. May be I like it XP style when updates didn't used to bug me with every single boot up and power down. It has become even worse. Who thought defering updates to the next boot up was a good option? It fucking interferes with the flow of work. They were like -
"You know what, let's update till 35% and then fucking update the remaining 65% at next boot"
"But users will be frustated"
"We'll show the update screen with clean font and a nice background. It will calm them down"
"Okay, so let users choose when to download the updates"
"That's not a fucking option, mate"
And if you are going to force updates down our throats please fucking mention what is being changed as a short description instead of showing a 'KBxxxxxxx' update number! If not that, at least hyperlink the thing to your update docs page! OR Mention a version buff if not it! I HATE seeing 'Update for Windows 10 Version xxxx for x64-based Systems' EVERY. SINGLE. TIME I see an update ready to be downloaded.
And no I don't play Candy Crush, or other games that are pre-installed as soon as I re-install fresh Windows or go on Xbox App. I hate to do this ritual of turning off auto download from Windows Store every time. So please don't pre-configure anything for me. Keep it fucking raw. That's why Linux distros win.
I'm just saying, Service Packs were a great thing with a need of little improvements. You guys ruined the whole experience, Microsoft.

Nightmare morning. Woke up for the fact that my app in app store is crashing on opening. Yesterday submitted improvements to the app (react-native).

Tested locally on simulator and also on real machine by react-natives --variant Release. Worked ok. But now when I build it with xcode and sent it to app store, it's no longer working at all =/.

Im losing users by every minute. Was able to immediately make a hotfix, but apple has not taken any hurry in reviewing it. Also it's not possible to revert previous version in app store, I just have to submit a new version that will be reviewed. I even called them and they promised to hurry but nothing's happened and it's been like 4-5 hours already.

I got so bad luck because usually in review they test the app, but now they didn't, and this time it didn't work at all. And I thought that testing it by react-natives --variant release mode would be enough, but apparently theres something different when you build and archive it with xcode. I feel my app is doomed now, many of the users might abandon it completely =/.

If I learned something it is that always try to test the last modified version of the app. Even if the modification seems small. Don't trust react-natives --variant release for testing an ios app.

Ever suggest improvements and get shot down at every turn? I was discussing automating our release process today and suggesting that instead of having to do everything manually and babysit the build, we should let Jenkins deal with releasing and the attitude was that we shouldn't even try because we'd spend more time maintaining the automation and wouldn't gain anything. Obviously I disagree, but it seems like I'm always coming up against shit like this.

Our requirements gathering is another point of contention; I think we could be way better at it if we invested more time talking to customers before a project starts but the attitude is to get straight into development and deal with that later.

I don't know why I even bother sometimes...

So working for a company and the dev team I’m apart of works on a legacy rails app. Technical debt is high, no automated tests, no proper routing and also running unsupported versions of the language.

I joined seven months ago and got the current team doing automated testing so that’s a plus, they bought this app four years ago and there’s been no language updates, testing, cleanup, security updates, nothing, just adding to bad code.

Now we’re looking to actually upgrade language versions, the language and the framework now this will cause a lot of stuff to break naturally due to how outdated it is.

So I started putting proper routes into place how things should of been when things were being built as we have some spare time I decided to go out of my way to clear up some of the technical debt to get ahead of the curb. Re-done an entire section of the app, massive speed improvements, better views, controller, model, comment clean up and everything exactly how it should be.

I push the PR,
*other dev* - “why are we doing all of these other changes”
*me* - “well to implement routes properly, we have to use the new routes I just did some extra cleanup along the way”
*today, me* - “can you lend me a hand with one of the routes the ID isn’t getting passed”
*today, other dev* - “this wouldn’t of happened if you didn’t redo all these files, let’s just scrap the changes”
…

Sooo, I’ve spend three weeks improving one section in the app, because I’m having issues with one route according to this dev I should scrap it? Wait come again, am I the only one in this team who cares about making this app better all round?

Frustrating…

"reach out"

"touch base"

"ping an email over"

Just a couple of examples of terms people like recruiters love using that make you cringe so hard you want to throw yourself under the next bus. Very similar to clients who say:

"can we make it pop"

"I showed it to my graphic designer friend and they said it needs more fonts"

"I've made some improvements in Word for you"

The new devRant upgrade is great! So cool that everyone can easily get to podcasts from the menu. Comments interface nice improvements. devRant rules!

!rant
When applying for a new job, how do you tell the difference between somewhere that is really old fashioned but wants someone come in and make improvements to processes and coding standards... And somewhere that pretends to want those things, but actually has no intention of letting anyone make those changes?

Coding distraction
To be honest - task distraction

1. Starting a task, you need to do
2. finding old code you want to refactor
2. Doing some improvements
3.Fixing the bugs created by prev actions
....
Task not finished
But that's kind of fun. Livin' on the edge

Office improvements by developers

Where and How do you make developer friends.

My coworkers are smart and decent developers but they learned on the job for the job.

But they're not interested in discussing improvements to legacy projects that barely still work until they break and we need to rush to recreate them 'better'.
or sit on a call on the weekend working on spontaneous personal projects that usually die cause another idea came along.

Sometimes I really just want someone I can hop on a discord call with so they can criticize my projects and brainstorm ideas and improvements with me

Why is every one of these marked critical!? Every month or two they have an update that is critical and they are usually just security improvements. Is their security really that bad to always mark as a 'critical' update.

I have made a lot of small changes in my app like minor bug fixes, Animation, optimizations, better database management, new options, overall interface improvements, ... to give the application a better overall appearance. Then I decide to show it to my Client.

"From what I can tell, you haven't done much since last time"

Lua users, have you used moonscript?

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

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

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

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

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

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

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

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

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

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

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

someShit: =>

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

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

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

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

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

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

good commit message:
"make improvements to the user interface."
bad commit message:
"made improvements to the user interface"
no, you didn't. it's not deployed yet. your merely SUGGESTING improvements at this point. that's like walking into an interview telling the secretary you already got the job. flushing before you wipe. eating the pizza when it's still frozen. you are way too assumptive about this commit you've just made actually making it to production.
unless you are already on production? well, in that case, your commit message was incorrect. let me amend it for you:
"HOT FIX ALL TEH BUGS!!!11111!!11"

Finally convinced the senior engineer I'm working with to let me use Angular CLI for our front end because of all the added things we get compared to what he had originally setup for our Angular project (plus it's a phenomenal tool). I was slowly adding in things to make the app better (more like a PWA), but what pushed him over the edge was the platform-webworker package letting us off load some heavy tasks into a web worker. I'm excited for the improvements coming!

Definition: Minecraft Mods
QOL improvements that introduce a grind to reduce the grind of something else.

Don't trust that update with change log -
"Bug fixes and performance improvements".

I maintain two websites for my employer. The head of my department and my manager decided it’s best for me to focus my time on website A and website B should be replatformed to an out of the box solution. For website B, we’d work with our IT team to find something suitable.

I did some research and came up with a list of possible solutions. IT looked into solutions that would work with the org’s best practices for tech. A few sales pitches and demos were arranged with the top choices.

Stakeholder for website B is really digging in her heels. SH keeps badgering our Product Manager and IT about why can’t we just build in-house. The out of box solutions don’t do everything she wants.

PM tells SH that no solution will be perfect. PM also reminds SH that comparable institutions just use Google sheets/forms and do everything by hand. So choose an out of the box platform or use Google forms.

Plus, the list of improvements the SH wanted for website B would take at least a year if I did them on my own and there’s no budget to out source the labor. That’s not counting bring the code up to best practices or improving database efficiency.

I’m glad I don’t have to work with Stakeholder anymore. SH and her department were just a pain. They want a lot of custom tech solutions but they freak out at the smallest talk about tech issues.

Tips on getting promoted on work:

1. Collect a list of all improvements and achievements that u did during your time in that workplace

2. Compare your output with your colleagues output, check their MR's, their complexity and compare with yours.

3. Talk with your manager about a raise. Tell him about your achievements, like maybe you are working on a wider scope than others. Maybe you are mentoring junior devs. Or maybe you deal with a bigger workload than others but still deliver on time. Maybe your communication is good or maybe you document stuff very well and in that way you make your team more efficient and increase team output. Whatever. Pitch and sell yourself. Also provide some personal reasons why you need a raise, like maybe u have kids or maybe your rent doubled. Inflation and so on. Selling point is that u are a human not a greedy bastard.

At the end of that talk the manager most likely will say that he needs to speak higher ups, he needs to gather feedback from your colleagues and so on. Give him a week or two if possible, no more.

He will probably get back to you with an offer. If there is none start applying, get an offer and put in your notice. In my case I waited 3 months for my raise to go through. I put in my notice, had a stressed call from manager, showed him my offer and my raise was arranged the next day.

Why do people keep inventing new object serialisations when there is already JSON and XML? Why do people think that a custom format and parser would be better than an industry standard and a parser that has years of development improvements? :-S

How would you teach / punish these people?