As a Dev,
I hate writing Docs.

As a Dev,
I hate it when there's no Docs.

Vicious Cycle.

The project where I realized I wanted to go from chemist to pro dev.

I built a flow-chemistry spectrometer with monitoring backend in Haskell.

Spectroscopy is where you add a reagent to a glass tube, it changes color, and by measuring the exact color it tells you how much of something (for example, a toxin) is present in the sample.

I had to do that a lot on factory samples, writing down measurements using pen & paper.

I'm lazy so I decided to do the logical thing: Automate it. I bought a second hand spectrometer, stripped the casing, did a shitload of glassblowing and hooked up tubes to the production pipelines, so I could get samples, mixing them in the correct ratio with reagents in continuous flows using valves.

I ended up using 2 home-crafted arduino-like boards (etching PCBs is fun!).

One to calibrate the mixture against known samples and control solenoid valves to continuously cycle through various reagents and deionized flushing water, the other to record the measurements and send them to a server running a Haskell/Yesod API.

The server collected the information into InfluxDB (A time series database), displaying all data on a graphite dashboard.

Eventually I wrote Haskell plugins for most of the chemistry processes, from pH & temperature measurements to polymer property and pigment tests (they made a lot of printer ink).

Then I was fired because they didn't need chemists anymore, and the code "could be maintained by the intern" (poor guy)...

But I did find out that I loved functional programming, chemistry automation projects, and crafting my own electronics during that time.

I'm too tired after programming, I need to relax.
...
I'm too bored, need to program.

Today I realized that I hit a total burnout. Last 3 years were extremely stressful for me (4 jobs in 3 different countries, exhausting and toxic relationship, bad habits). Last 7 months are the worst. I became lonely isolated and miserable. I learned to rely purely on stress, determination and validation to get through my days. Was supressing my emotions for a long time just to focus on making the money. Its time to break the cycle.

Im done with this. Next week Im quitting my fulltime job. Saved enough money for starting capital of my own dev services company. Built three projects that generate stable income to cover my living costs. Now finally I can take a long break to recover from this burnout and to heal myself. That poor persons mentality that I had from my poor family has been shattered. I achieved what I wanted in terms of having the money and gathered enough experience necessary to survive anywhere.

I managed to get through all this shit on my own with barely any support. People around me were draining me more than actually helping me. But I managed to do it and now its time to focus on myself, to heal and restore love for living. Im safe now.

The real software development life cycle.

Dear Indian Companies,

Why do you hire for a role and then say: "We dont have that role but then we want you to grow up to be a Generalist"!

6 years as a build, release and SCM guy at Moto and Nokia back then, I shifted to this big Indian IT corp coz Nokia was shutting down...

A week into my orientation (which is a crazy weirdness inducing ritual in and of itself), the new manager I'm supposed to be working with comes up and says- "Here's the code repo, there are 2 open jQuery issues, fix them!"

I'm not really sure what to say at this point because jQuery is nice and all but thats not who I am.. I'm the infra / DevOps guy. And this is circa 2012 when DevOps as a term was just hotting up...

Tell me to setup a multi-stage pipeline and automated test cycles, I'll do it drunk, but oh no! bug fixing on a jQuery script? Noooo!!!!! I just dont have the chops for it.

So long story short, I get reported to HR for insubordination - Yeah, Go Figure!

Cue: HR meeting
HR: You wont work?
Me: I cant work on jQuery. I am a sysadmin / devops guy... Give me a project that involves those skills and I'll work.
HR: But we hired you to work on jQuery.
Me: But you did not mention jQuery / UI / UX in the job description - Pulls up email and shows JD for interview which says Symbian, Build, Release, Configuration Management but NOT jQuery.
HR: ....
Me: :-/
HR: But we want you to be a generalist.
Me: #wtf
HR: We want an engineer to be able to do anything he is tasked with!
Me: Can I know my last working date here?

And thats how my career at a glorious IT corporation just went poof!

When I think back on it, I feel good that I chose to do what I wanted to get better at and what I loved working on...

And this is the problem with IT companies in our country - They play with people's aspirations and passions... To the point that all thats left of a software engineer is the looking forward to pay day so he can start the damn cycle all over again.

I remember reading shampoo directions as a kid and it feeling wrong to exit the cycle.

1. wet hair
2. apply shampoo
3. lather
4. repeat

I didn't choose development life, it chose me

Project Status Life Cycle... Lol :)

So still you say that a tree cannot have a cycle?

Want insights into a developer's sleep cycle? Check their commit history.

Personal project coding cycle:

- Because to many libs, too many ways, to many choices

Rant && story time

When I was in first grade of high school (age of 15) we had a class of informatics. Nothing unusuall, you say, but this teacher was ummm ... Let's just say special. Most of his classes looked like this:

TEACHER: Ok, class, today we are going to learn/work with <insert a name of a software here>. # And then he sat behind his desk, falling silent for the rest of the lesson. We had to look up the software ourselves, and learn to use it. Or not.

Next lesson, he just said:

TEACHER: Continue your work from the last time.

And on the third lesson of each cycle, there was grading in place. He walked through the class and if he saw you working with the software, you got a 5 (that is A for our western friends), but if you were doing something completely different, you got a 1 (that is F). That just ment that you had to open the program and wave the mouse around while he was looking at your screen, and you got a guaranteed 5.

And then the cycle repeated.

However, this is not the story about the teacher in general, it's a story about one specific event involving him.

Around the beginning of the year (calendar one, not school one; that is middle of the school year) a programming competition took place.

The first stage (school competition), was easy; I got 45 points out of 50 (I was second-best on the whole school, of all years (students from 15 to 20 years of age).

A few weeks later, second stage (national competition) took place. However, when I got to the registration dosk, things got weird.

I patiently waited in line, but when I got to the front, the assistant asked me for year and school.

ME: I come from SCHOOL_NAME and go to first year.
ASSISTANT1: All students who go to SCHOOL_NAME need to go to that separate line.

It seemed strange, but I walked over anyhow. Maybe there was enough students from our school so that new line opened for us.

ME: I go to first year. # I assumed I don't have to tell the name as the line was only for our school.
ASSISTANT2: Ok, but you need to go to that row. *points to the row wherexI just came from* # WTF is going on now?
ME: Ummm, I just came from there, and they told me to come here.
ASSISTANH2: Oh, you go to SCHOOL_NAME?
ME: Yeah
ASSISTANT2: Ok then. What is your name? # Thank Knuth, one mistery less
ME: My name is SELF.NAME
After a short search through the envelopes:
ASSISTANT2: Here you go # Both the fact that my name was completely misspeled and the procedure it took us to finally get to the correct envelope are a story for a different time.

Skip forward some 10 minutes, to the lecture hall where they just told us all the instructions and started to divide us into classrooms

ASSISTANT3:
for CLASSROOM, STUDENT_LIST in STUDENT_DIVISION:
for STUDENT in STUDENT_LIST:
STUDENT.invite(CLASSROOM)

At the end, only a few people, including me, remained.

ASSISTANT3: Is there anyone not from SCHOOL_NAME? # Umm, yeah, WTF is going on now?
Noone replied.
ASSISTANT3: OK, you all, come with me now, we will find you a classroom.

From there on, competition went fine, I came in second, got a new phone as a prize, no complaints.

However, later on, I realized what was the reason for all that weird behaviour.

Signup date for the second part was on LAST_SIGNUP_DATE, which was at least two weeks before the competition, and signups had to be done untill 1600 that day.

Our teacher signed us up at 2200. ON THE FUCKING DAY BEFORE THE COMPETITION. OF COURSE THEY HAD NOTHING PLANNED FOR US, NO ENVELOPES, NO COMPUTERS, NOTHING, IF WE WERE SIGNED UP LESS THAN FUCKING 12 HOURS BEFORE THE COMPETITION INSTEAD OF 2 WEEKS EARLIER. THE ONLY REASON WE GOT TO COMPETE WAS BECAUSE SOME PEOPLE DIDN'T SHOW UP AND WE USED THE PC'S MENT FOR THEM. IF EVERYONE SHOWED UP WE FUCKING COULDN'T COMPETE.

And from that moment on, I always signed myself up for all of the competitions; better safe than sorry.

Developers coding cycle:

Start of Project - "Right, I am going to make this code clean and structured."

Deadline looming - "F**k it, just throw the code in there and get it finished".

The cycle of programming

Long ago, like 5 years, I made an app for my EX GF in symbion to track her periods. Application predict the next date when your period will come based on her cycle.

How ever after 2 month of usage she told me that application was flashing that she is pregnant. She scared shit out of herself and made me sacred a hell as well.

Later i find out that the variable i used to store number of days between last period and current date was not capable of storing value more than 40, i don't know how, and triggers negative value to be shown.

Early days of my programming, Shit happens.

Overheard a phone call between the Senior Network Engineer and a contracted Printer-company at 9am this morning. Photocopier was giving a 'functional error' message on-screen and not printing;

N.E:
I logged this call last
Thursday afternoon. Thats 1.5 days of the photocopier not working on our busiest site! Where's the engineer??
.... yes, that's the error message.
Yes, i can log into it, you should have the IP address from the call.
Yes, it's obviously pinging too.
Yes.... we've power-cycled the printer multiple times...
yes, tried that too...
yes, I've unplugged the network cable as well... left it for 15 minutes.
... sorry. What?
What did you say?
Are you f***ing kidding me?
Would you also like me to rub the side of the f***ing machine, and say a prayer while I'm at it??
*takes a deep breath*
Fine, I'll do that but when it doesn't work, i want someone out on the site before lunchtime today!
*slams phone down angrily*

N.E to me as he stomps out of the office;
He wants me to get the user to unplug the network cable and do a power cycle. How the f**k is that going to help? Idiots! Don't know why we have a contract with them, i could do a better job!!!

*comes back into office 5 minutes later*

Me: did it fix it?
NE: yeah. Damn.
*leaves room again to make apologetic phonecall*

Software engineering and developers and life cycle of Project 🤣🤣🤣😂😂

>be me
>Get hit by a wave of depression
>Question the reason for your existence
>Open laptop start coding as a distraction
>Discover/invent/learn something new
Hey that's nice!!! (wait for the next wave of depression)

How to never finish a project:

*Le me staring at my own code after a few weeks*
"Bleh! Icould do better. Lets change it all before things get worse."

And the cycle continues...

Just joined a skype meeting:

Me (software engineer): Am I audible?
Product Manager: Am I audible to you?
Business Development Manager: Hey guys, Am I audible?

After 30 minutes:
Me: Hey guys, Am I audible?
Product Manager: Am I audible to you?
Business Development Manager: Am I audible, guys?

TFW your client's git policies are so draconian that the dev teams use "develop" as trunk, and completely ignore the release process.

I wrote up 50 pages of git standards, documentation and procedure for a client. Bad indian director 9000 decides the admin (also Indian) who specializes in Clearcase and has no git or development experience is more qualified to decide and let's him set the policy.

FF to today:

- documentation, mostly contradictory, is copy pasted from the atlassian wiki
- source tree is the standard
- no force pushing of any branches, including work branches
- no ff-merge
- no rebasing allowed
- no ssh, because he couldn't figure it out...errr it's "insecure"
- all repos have random abbreviated names that are unintelligible
- gitflow, but with pull requests and no trust
- only project managers can delete a branch
- long lived feature branches
- only projects managers can conduct code reviews
- hotfixes must be based off develop
- hotfixes must go in the normal release cycle
- releases involve creating a ticket to have an admin create a release branch from your branch, creating a second ticket to stage the PR, a third ticket to review the PR (because only admins can approve release PRs), and a fourth ticket to merge it in
- rollbacks require director signoff
- at the end of each project the repo must be handed to the admin on a burned CD for "archiving"

And so no one actually uses the official release process, and just does releases out of dev. If you're wondering if IBM sucks, the answer is more than you can possibly imagine.

5 hours on the call. No end in sight. Nothing in logs, errors, or captures. Want to cry.

The intern has directly editted the CSS file then push to the repo.
The senior optimized the old codebase and compiled the SCSS with gulp leading to the CSS file rebuild.

The vicious cycle continued until code review which was like 2 weeks later.

This is how I work and my headphones are beats

The vicious cycle

PS:
Potential cycle fix:
if(user.stopsAskingQuestions())
{
//free user
break;
}

I love Linux, but its community can be so full of incompetent assholes..

Just now I asked in Freenode ##linux how to get the process ID of my current running process in bash. I got my answer - it's a shell built-in called "$$".

Then people start to nitpick some more - why do you need it? How is that different from an exit? - to which my response was.. well I know the whole idea behind exit codes, and I'd use it whenever possible, in all defined behavior that allows my program to terminate itself whenever it can. This pidfile however would be used to exit itself and provide diagnostic information whenever the program enters undefined behavior - a segfault in C language. Scenarios in which I don't have full control over the script's behavior anymore, such as the system entering an unworkable state where the system stalled, still got some binaries in RAM but the rootfs got unwritable, such as now - very helpfully, thanks HP! - when my laptop likely overheated and shat itself. I issued sudo reboot into it, but even that wouldn't issue properly anymore due to the /sbin/poweroff binary becoming inaccessible too. I had to issue a hard power cycle.. one of the few times in which I'm thankful to HP for actually causing shit like this, lol.

Point is, that undefined behavior is what I'm trying to mitigate against. I certainly can't let any files other than diagnostics remain in nonvolatile storage like that, especially when their state should be predictable in order to ensure good operation (like files expressing whether the script is already running or not, i.e. lock files).

Back to that IRC chat. Aside from the answer, I got ridicule from people who probably don't even know how to properly compile a kernel. Ubuntu users, overconfident scum. Sometimes I feel like I should ask questions in channels like #archlinux only, where such incompetency is ridiculed on its own.

Fibonacci for developers.

One Developer writes bad code and leaves. Company hires two more to fix the code and cycle continues. Now you know why software developers are in demand.

After returning back from the company we were purchasing a new phone system (hardware+software, $100K+, kind of a big deal)
VP: “I need the new phone system software integration for our CRM by next week. I need to demo the system for the other VPs”
Me: “No problem. Were you able to get their API like I asked?”
VP: “Salesman didn’t know for sure what that was, but he said all the developer software documentation is on their site.”
Me: “Did he give you a URL? Their main site is all marketing mumbo-jumbo. I assume there is another one specific for developers.”
VP: “Yea, he might have said something, but I don’t understand why you need it. The salesman said the integration would be seamless. He showed me several demos.”
Me: “No, I mean I need to know, is the API a full client install? a simple dll? is this going to be a web service integration? How will I know what to program against?”
VP: “I think I heard him say something about COM? Does that sound like an API?”
Me: “It’s a start. Did he provide you anything, a disk, a flash drive, anything with the software?”
VP: “No, only thing he told me was our CRM integration would be seamless and our development team would have no problems.”
Me: “OK..OK…I get it…he’s a salesman. Is there an 1-800 number I can call? A technical support email address? Anyone technical I can reach out to?”
VP: “Probably, but I don’t understand what the problem is. I need the CRM integrated by next week. I gave the other VPs a promise we would get it done. I do not break promises.”
Me: “Wait…when are we installing the new system?”
VP: “Well, the purchase order will be cut at the end of the month’s billing cycle, the company has about a two month turnaround time to deliver and install the hardware, so maybe 3 months from now? Are you going to be able to have the integration ready for next week?”
Me: “If we won’t see any of the hardware for 3 months, what exactly am I integrating with?”
VP: “That API you wanted or whatever it is. COM…yea, it’s COM. I was told the integration would be seamless and our developers would have no problem. I don’t understand why you can’t simply write the code to make it work. Getting the hardware installed is going to be the hardest part.”
Me: “OK, so I have no documentation, we have no hardware, no software, and no idea what this ‘seamless integration’ means. I’m afraid there isn’t anything I can do right now. ”
VP: “Fine!...I’ll just have to tell the other VPs you were not able to execute the seamless integration with the CRM.”
Which he did. When the hardware+software was finally installed, they hired consultants (because I “failed”). I think the bill was in the $50K range to perform the ‘integration’ which consisted of Excel spreadsheets (no kidding). When approached with the primary CRM integration, the team needed our API documentation, a year’s development time and $300K. I was pissed off enough, and I had the API documentation, I was able to get the basic CRM integration within 3 days. When an agent receives a call, I look up the # in our database, auto-fill the form with the customer info, etc. Easy stuff when you have the documentation.
The basics worked and the VP was congratulated by ‘saving’ the company $300K. May or may not have been bonuses involved, rumors still out on that one, but I didn't see em'. Later my manager told me the VP was really ticked that I performed the integration ‘behind his back’, but because it was a success, he couldn’t fire me.

Real life cycle of programmers...

Beware, this is gonna be a long one.

Today, in university, our professor wanted us to do an algorithm where a number was given in input, and we had to see if that number was, as she put it, "triangular".
For example:
3 is triangular because it's 1+2.
6 is triangular because it's 1+2+3.
10 is triangular because it's 1+2+3+4.
And so on.

While she was explaining this, I was programming it on my phone (because I didn't bring a PC there).
In about 10 minutes I completed it.

This student who was beside me, which I didn't know until today (I'm still in my first year here), saw me programming it, and when I finished it, he looked at it and said: "It takes too much time, like this."
So he spent another like 5-10 minutes """fixing""" it, and then showed it to me: "Here, now it's better."
Do you want to know what he did?
The only thing he did was putting a for cycle instead of my while cycle.
And he didn't even do it properly!
He put an else statement inside the brackets of an if, and some variables weren't correct.
You call that making a program more efficient? Deficient is more like it.

Also, like 5-10 minutes after I did it on my phone, on my own, I looked at the prof's desk: a guy (who apparently is "the best") wrote his algorithm on the blackboard, and the whole fucking class applauded.

Later, I saw on our Whatsapp group that someone sent a photo of him writing on the blackboard, with the caption "The student surpasses the teacher." Others agreed.
I replied with: "For the record, I did this algorithm in 10 minutes."
An asshole replied: "You'll never be superior to the master"

Fuck off. -.-"
...I'll show them.

Every year, my company organizes an internal seminar week for its engineers and developers. I helped plan it this year and, since I also ran a few sessions, was absolutely exhausted by the end of the week.

On Friday of that conference week (after I'd spent four hours in our engineering building), I come back to my desk to discover that a coworker managed to, single handedly, get our boss to agree to shortening our release cycle to one that, without dramatic infrastructure changes, would require about 8x the developer overhead than today's. ...The test cycle I am supposed to pick up in a month.

When asked about it, he said he was so full of energy, why wait for automaton? What better way to inspire us to improve than to switch right now? The worst that can happen is just a few bugs.

I love my job, but I can't stand this guy. 😒

First year at uni, during c++ basis.
The professor has just finished explaining the while cycle.
Professor: We want the code to print all numbers from 0 to 40 using a counter. How would you do?

Classmate puts up his hand: we do 40 if statements and when we reach the 40th one we stop.

Professor: *face palm*

Project life cycle for developers

The DE life cycle of every Linux hobbyist:

1. Let's work with Unity.... it's so blah
2. Let's check out XFCE.... it does its job, but it needs more zing
3. Let's check out KDE...aah, my poor battery.
4. Let's check out LXDE.... Can you be any more boring?
5. Let's check out Pantheon.... This is perfect, but I'm tired of using a tweak tool to even enable minimize and maximize
6. Let's go to Gnome 3...Ah never mind
7. Let's go to Cinnamon... Blurgh, It reminds me of Windows
8. Let's go to MATE....Hmm, Mutiny layout?!! It reminds me of Unity. Wonder if Unity 8 has made any progress!
9. Go back to Step 1.

In india

Teachers teach students to code, without any field experience

These students learns things tht they dont need in their life and becomes teachers

The cycle continues...

From my genius analysis, we can see that these students need not go to a company to work like a horse,

Why are we in a company working like a horse?

➡️You Are Not A Software Developer⬅️

When I became a developer, I thought that my job is to write software. When my customer had a problem, I was ready to write software that solves that problem. I was taught to write software.

But what customers need is not software. They need a solution to their problem. Your job is to find the most cost-effective solution, what software often is not.

According to the universal law of software development, more code leads to more bugs:

e = mc²

Or

errors = (more code)²

The number of bugs grows with the amount of code. You have to prioritize, reproduce and fix bugs.

The more code you write, the more your team and the team after it has to maintain. Even if you split the system into micro services, the complexity remains.

Writing well-tested, clean code takes a lot of time. When you’re writing code, other important work is idle. The work that prevents your company from becoming rich.

A for-profit company wants to make money and reduce expenses. Then the company hires you to solve problems that prevent it from becoming rich. Confused by your job title, you take their money and turn it into expensive software.

But business has nothing to do about software. Even software business is not about software. Business is about making money.

Your job is to understand how the company is making money, help make more money and reduce expenses. Once you know that, you will become the most valuable asset in the company.

Stop viewing yourself as a software developer. You are a money maker.

Think about how to save and make money for your customers.

Find the most annoying problem and fix it:

▶️Is adding a new feature too costly? Solve the problem manually.
▶️Is testing slow? Become a tester.
▶️Is hiring not going well? Speak at a meetup and advertise your company.
▶️Is your team not productive enough? Bring them coffee.

Your job title doesn’t matter. Ego doesn’t matter either.

Titles and roles are distracting us from what matters to our customers – money.💸

You are a money maker. Thinking as a money maker can help choose the next skill for development. For example:

Serverless: pay only for resources you consume, spend less time on capacity planning = 💰

Machine Learning: get rid of manual decision-making = 💰

TDD: shorter feedback cycle, fewer bugs = 💰

Soft Skills: inspire teammates, so they are more productive and happy = 💰

If you don’t know what to learn next — answer a simple question:

What skills can help my company make more money and reduce expenses?

Very unlikely it’s another web framework written in JavaScript.

Article by Eduards Sizovs
Sizovs.net

Craziest bug, not so much in the sense of what it was (although it was itself wacky too), but in what I went through to fix it.

The year was 1986. I was finishing up coding on a C64 demo that I had promised would be out on a specific weekend. I had invented a new demo effect for it, which was pretty much the thing we all tried to do back then because it would guarantee a modicum of "fame", and we were all hyper-ego driven back then :) So, I knew I wanted to have it perfect when people saw it, to maximize impressiveness!

The problem was that I had this ONE little pixel in the corner of the screen that would cycle through colors as the effect proceeded. A pixel totally apart from the effect itself. A pixel that should have been totally inactive the entire time as part of a black background.

A pixel that REALLY pissed me off because it ruined the utter perfection otherwise on display, and I just couldn't have that!

Now, back then, all demos were coded in straight Assembly. If you've ever done anything of even mild complexity in Assembly, then you know how much of a PITA it can be to find bugs sometimes.

This one was no exception.

This happened on a Friday, and like I said, I promised it for the weekend. Thus began my 53 hours of hell, which to this day is still the single longest stretch of time straight that I've stayed awake.

Yes, I spent literally over 2+ days, sitting in front of my computer, really only ever taking bio breaks and getting snacks (pretty sure I didn't even shower)... all to get one damn pixel to obey me. I would conquer that f'ing pixel even if it killed me in the process!

And, eventually, I did fix it. The problem?

An 'i' instead of an 'l'. I shit you not!

After all these years I really don't remember the details, except for the big one that sticks in my mind, that I had an 'i' character in some line of code where an 'l' should have been. I just kept missing it, over and over and over again. I mean, I kinda understand after many hours, your brain turns to mush. and you make more mistakes, so I get missing it after a while... but missing it early on when I was still fresh just blows my mind.

As I recall, I finally uploaded the demo to the distro sight at around 11:30pm, so at least I made my deadline before practically dropping dead in bed (and then having to get up for school the next morning- D'oh!). And it WAS a pretty impressive demo... though I never did get the fame I expected from it (most likely because it didn't get distributed far and wide enough).

And that's the story of what I'd say was my craziest bug ever, the one that probably came closest to killing me :)

Past few weeks, I have started to work late night and sleep whole day. I go to office at around 7pm and returns back next day 8-9am. I found it super productive.
But, my manager wasn't happy about it and now, she shifted daily scrum at 1 PM and emailed me to make sure I attend it daily.
Now, I have to fix my sleeping cycle... Nights are so great to work. Silent and nobody around.
Now, from tomorrow, I got a new challenge everyday to make it to scrum daily.

software life cycle...

Programs are like humans. First you need to do baby steps and make it work like you want it, and teach it how to work. Then after the release the youth brings a lot of bugs and swearing. Finally it's grown up and can handle itself. Then it gets old and no one are so attracted to it anymore. It rests in peace on a old storage drive, and gets replaced by a new generation. 👶🏼👦🏽👨🏽👴🏽

I wake up, take a look at the clock: 5:21.
The alarm is at 5:40.
Thanks fucking sleep cycle for waking me up to wake up the alarm clock... FUCK!!!

Let me share a piece of advice to entry level devs that are getting ready for job interviews that I wish someone gave to me when I was first looking for work straight out of school. Do not focus making yourself look good to this company by trying to make your resume flashy or trying to oversell yourself. Although its important to present yourself sure, but it should not be the foundation for you to base your interview goals around. Rather focus on the company itself. Find out whether the company itself uses modern technology,practices and upholds to project management and the software development cycle, find out how they work,communicate and develop as a team. Simply put focus on whether they are worth working for instead of looking like your worth being hired. Can they collaborate,communicate and solve problems efficiently. Otherwise you may end up getting hired and hating your job. Just a thought and some advice on my own experiences. Hope it helps someone.

Data Engineering cycle of hell:

1) Receive an "beyond urgent" request for a "quick and easy" "one time only" data need.

2) Do it fast using spaghetti code and manual platforms and methods.

3) Go do something else for a time period, until receiving the same request again accompanied by some excuse about "why we need it again just this once"

4) Repeat step 3 until this "only once" process is required to prevent the sun from collapsing into a black hole

5) Repeat steps 1 to 4 until it is impossible to maintain the clusterfuck of hundreds of "quick and simple" processes

6) Require time for refactoring just as a formality, managers will NEVER try to be more efficient if it means that they cannot respond to the latest request (it is called "Panic-Driven Development" or "Crappy Diem" principle)

7) GTFO and let the company collapse onto the next Data Engineering Atlas who happens to wander under the clusterfuck. May his pain end quickly.

You know that the mobile ecosystem is completely fucked when you have to open up your device just to do a hard power cycle.. and what for? What's the fucking difference between a connector inside of the device, and one that's outside the device? A couple of cubic millimeters? If it's even that much?

Another project with legacy code got just dusted off at work. Shits fucked beyond recognition! We got:
- Rando variable names that mean nothing
- Timers running with a cycle time of 2.5ms if you start them with the multiplier 1.
- An Interrupt routine thats 300 lines long.
- Another interrupt thats starting an ADC conversion and waiting for it to complete before returning.
- For loops that start with one and subtract one from the iterator in the loop
- Every value that would normally be expressed as a regular number is written down in Hex. Eg: if(val==0x05)
- State machine built without writing down which state is which. Its just a number. (In hex obviously!)
- All running on a Microcontroller you cant debug on.
- Using a compiler no one has ever heard of before.
- Weird ass Port manipulations
- 15 different .hex and .elf files with no clue whats in them.
- No version control
- We tried explaining the code to a monkey and it hanged itself.

Call me a spoiled Linux kid but FUCK WINDOWS UPDATE!!
It's not even the shitty deployment cycle that they have for their updates, the real cancer is the fucking update app.
First off, if you fucking piece of shit already have the audacity to load gigabytes of updates over my 0.8mbit/s connection in the background, without my goddamn consent, at least let me PAUSE the fucking download!!! I don't see why the fuck you have to block my connection, and therefore me, from the most basic things like visiting a fucking website for more than a FUCKING HOUR to load useless updates, YOU PIECE OF BLOODSTAINED SHIT, I GOT SHIT TO DO.
And it doesn't stop there, noooo: then you even have the bloody fucking nerve to FORCE ME TO INSTANTLY RESTART AND SIT THROUGH YOUR FUCKING 40 MINUTE UPDATE PROCESS WHILE IM TRYING TO WORK.. WITHOUT THE ABILIT TO DELAY THE UPDATE!!! What the fuuuck?!

It is seldom that I am this 👌 close to just dd'ing /dev/null to my windows partition. Fuck you!!

In the before time (late 90s) I worked for a company that worked for a company that worked for a company that provided software engineering services for NRC regulatory compliance. Fallout radius simulation, security access and checks, operational reporting, that sort of thing. Given that, I spent a lot of time around/at/in nuclear reactors.

One day, we're working on this system that uses RFID (before it was cool) and various physical sensors to do a few things, one of which is to determine if people exist at the intersection of hazardous particles, gasses, etc.

This also happens to be a system which, at that moment, is reporting hazardous conditions and people at the top of the outer containment shell. We know this is probably a red herring or faulty sensor because no one is present in the system vs the access logs and cameras, but we have to check anyways. A few building engineers climb the ladders up there and find that nothing is really visibly wrong and we have an all clear. They did not however know how to check the sensor.

Enter me, the only person from our firm on site that day. So in the next few minutes I am also in a monkey suit (bc protocol), climbing a 150 foot ladder that leads to another 150 foot ladder, all 110lbs of me + a 30lb diag "laptop" slung over my shoulder by a strap. At the top, I walk about a quarter of the way out, open the casing on the sensor module and find that someone had hooked up the line feed, but not the activity connection wire so it was sending a false signal. I open the diag laptop, plug it into the unit, write a simple firmware extension to intermediate the condition, flash, reload. I verify the error has cleared and an appropriate message was sent to the diagnostic system over the radio, run through an error test cycle, radio again, close it up. Once I returned to the ground, sweating my ass off, I also send a not at all passive aggressive email letting the boss know that the next shift will need to push the update to the other 600 air-gapped, unidirectional sensors around the facility.

!rant

I've been doing wrong these last year, so I decided to step up my game, implementing on my work cycle:

+ Testing
+ CI

It feels fucking great. If you're not doing it, it's time.

My development process seems to go:

1. Write code
2. Believe that said code is amazing
3. Write more code
4. Revisit earlier code and start to doubt it's amazing-ness
5. Get frustrated that it could be done better
6. Redo 1 and repeat cycle

Seems a massive waste of time but I tend to like taking a different approach as soon as I find I'm getting stuck with the previous one.

I then get encouraged to take the quick/easy approach which seems like a backwards step and not worthwhile because I know it won't be as fast/efficient.

devRant is awesome, but Disney also manages to light-up my day.
This is how Wall-E became a beloved member of our team, and helped me put a smile on my face throughout a very frustrating project.

It all started in a company, not so far far away from here, where management decided to open up development to a wider audience in the organization. Instead of continuing the good-old ping-pong between Business and IT...

'not meeting my expectations' - 'not stated in project requirements'
'stuff's not working - 'business is constantly misusing'
'why are they so difficult' - 'why don't they know what they really want'
'Ping, pong, plok... (business loses point) ping, pong'

... the company aimed to increase collaboration between the 2 worlds, and make development more agile.

The close collaboration on development projects is a journey of falling and getting back up again. Which can be energy draining, but to be honest there is also a lot of positive exposure to our team now.
The relevant part for this story is that de incentive of business teams throughout these projects was mainly to deliver 'something' that 'worked'. Where our team was also very keen on delivering functionality that is stable, scalable, properly documented etc. etc.
We managed to get the fundamentals in place, but because the whole idea was to be more agile or less strict throughout the process, we could not safeguard all best-practices were adhered to during each phase of a project. The ratio Business/IT was simply out of balance to control everything, and the whole idea was to go for a shorter development lifecycle.
One thing for sure, we went a lot faster from design through development to deployment, high-fives followed and everybody was happy (for some time).
Well almost everybody, because we knew our responsibility would not end after the collection of credits at deployment, but that an ongoing cycle of maintenance would follow. As expected, after the celebrations also complaints, new requirements and support requests on bug fixes were incoming.
Not too enthusiastic about constantly patching these projects, I proposed to halt new development and to initiate a proper cleaning of all these projects. With the image in mind of a small enthusiastic fellow, dedicated to clean a garbage-strewn wasteland for humanity, I deemed "Wall-E" a very suited project name. With Wall-E on board, focus for the next period was on completely restructuring these projects to make sure all could be properly maintained for the future.
I knew I was in for some support, so I fetched some cool wall papers to kick-start each day with a fresh set of Wall-E's on my monitors. Subsequently I created a Project Wall-E status report, included Wall-E in team-meetings and before I knew it Wall-E was the most frequently mentioned member of the team. I could not stop to chuckle when mails started to fly on whether "Wall-E completed project A" or if we could discuss "Wall-E's status next report-out". I am really happy we put in the effort with the whole team to properly deploy all functionality. Not only the project became a success, also the idea of associating frustrating activities with a beloved digital buddy landed well in our company. A colleagues already kickstarted 'project Doraemon', which is triggering a lot of fun content. Hope it may give you some inspiration, or at least motivate you to watch Wall-E!

PS: I have been enjoying the posts, valuable learnings and fun experiences for some time now. Decided to also share a bit from my side, here goes my first rant!

How I met python
[long read but worth]

There's nothing wrong with falling in love with a programming language for her looks. I mean, let's face it - Python does have a rockin' body of modules, and a damn good set of utilities and interpreters on various platforms. Her whitespace-sensitive syntax is easy on the eyes, and it's a beautiful sight to wake up to in the morning after a long night of debugging. The way she sways those releases on a consistent cycle - she knows how to treat you right, you know?

But let's face it - a lot of other languages see the attention she's getting, and they get jealous. Really jealous. They try and make her feel bad by pointing out the GIL, and they try and convince her that she's not "good enough" for parallel programming or enterprise-level applications. They say that her lack of static typing gives her programmers headaches, and that as an interpreted language, she's not fast enough for performance-critical applications.

She hears what those other, older languages like Java and C++ say, and she thinks she's not stable or mature enough. She hears what those shallow, beauty-obsessed languages like Ruby say, and she thinks she's not pretty enough. But she's trying really hard, you know? She hits the gym every day, trying to come up with new and better ways of JIT'ing and optimizing. She's experimenting with new platforms and compilation techniques all the time. She wants you to love her more, because she cares.

But then you hear about how bad she feels, and how hard she's trying, and you just look into her eyes, sighing. You take Python out for a walk - holding her hand - and tell her that she's the most beautiful language in the world, but that's not the only reason you love her.

You tell her she was raised right - Guido gave her core functionality and a deep philosophy she's never forgotten. You tell her you appreciate her consistent releases and her detailed and descriptive documentation. You tell her that she has a great set of friends who are supportive and understanding - friends like Google, Quora, and Facebook. And finally, with tears in your eyes, you tell her that with her broad community support, ease of development, and well-supported frameworks, you know she's a language you want to be with for a long, long time.

After saying all this, you look around and notice that the two of you are alone. Letting go of Python's hand, you start to get down on one knee. Her eyes get wide as you try and say the words - but she just puts her finger on your lips and whispers, "Yes".

The moon is bright. You know things are going to be okay now.

First rant!

The first time I got in touch with programming was when I was about 14 years old. I started a private server for a game called Maplestory (yeah you know it, I know you do) and had one of the most popular servers.
Topping all the rankings of best servers, getting lots and lots of traffic...
Anyway, I started modding the game and implement new features and quests. Right until my father saw our bandwidth. Because the server was running on my computer in my own bedroom 24/7 and blowing nice hot air in my room.
Our bandwidth limit was reached in just a couple days in to the next billing cycle and had to shut everything down from that point. And this happened a few times.
I was devastated shutting it down but learned so much from it. And it introduced me to programming.

Up till now, I'm almost graduating in computer science, already have 2 companies that are willing to hire me, and probably even going to work with my dad on a huge app soon

Story time

I really love helping and teaching others about code. Recently I had a friend that wanted to get into web development. Being me, I told him that i would teach him all he wants but that he needs to do some research first to show me that he feels comfortable with as a minimum requirement. I told him to research the minimum technologies required to build a web page and to tell me about the request response cycle and stuff like that. When he came back I was expecting small explanations such as "html stands for bla bla and is used for bla bla".No. this dude comes back all proud to tell me about flipping Laravel. I sit there quietly listening to him go on about the "Laravel programming language". He likes anime, I like kendo (and have trained in it) so while he is talking I slowly move us into the part of my office where I keep my boken (wodden sword). As soon as he sees me sitting down with the sword he asks what am i doing with it.
"Well, remember when in some anime that you like you see teachers beating their studets over stupid shit?"
"What?"
..."WHAT DOES HTTP STANDS FOR?"
"The...the err the web language that.. er"
BOINK
"what is javascript?"
"Like the updates thing?"
HARDER BOINK

:) guarantee he wont forget what http is after that and what js and Laravel are from now on :) needless to say he will continue learning with much more care.

Coding dojo for real mofockas, ya dig?

Well, I was Always into Computers and Games and stuff and at some point, I started wondering: "why does Computer Go brrr when I Hit this Button?".

It was WinAPI C++ and I was amazed by the tons of work the programmers must have put into all this.

13 year old me was Like: "I can make a Game, cant be too hard."

It was hard.
Turns out I grabbed a Unity Version and tried Things, followed a tutorial and Made a funny jet Fighter Game (which I sadly lost).

Then an article got me into checking out Linux based systems and pentesting.
*Promptly Burns persistent Kali Live to USB Stick"
"Wow zhis koohl".
Had Lots of fun with Metasploit.

Years pass and I wrap my head around Javascript, Node, HTML and CSS, I tried making a Website, worked Out to some extent.

More years pass, we annoy our teacher so long until he opens up an arduino course at school.
He does.

We built weather stations with an ESP32 and C++ via Arduino Software, literally build 3 quadrocopter drones with remote Control and RGB lighting.
Then, Cherry on the top of everything, we win the drone flying Contest everyone gets some nice stuff.

A couple weeks later my class teacher requests me and two of my friends to come along on one of their annual teacher meetings where there are a bunch of teachers from other schools and where they discuss new technology and stuff.

We are allowed to present 3D printing, some of our past programming and some of the tech we've built.

Teachers were amazed, I had huge amounts of fun answering their questions and explaining stuff to them.

Finally done with Realschulabschluss (Middle-grade-graduation) and High school Starts.
It's great, we finally have actual CS lessons, we lesen Java now.
It's fuckton of fun and I ace all of it.
Probably the best grades I ever had in any class.

Then, in my free time, I started writing some simple programs, firstvI extended our crappy Greenfoot Marsrover Project and gave it procedural Landscape Generation (sort of), added a Power system, reactors, Iron and uranium or, refineries, all kinds of cool stuff.

After teaching myself more Java, I start making some actual projects such as "Ranchu's bag of useful and not so useful stuff", namely my OnyxLib library on my GitHub.

More time passes, more Projects are finished, I get addicted to coding, literally.
My days were literally Eat, Code, sleep, repeat.

After breaking that unhealthy cycle I fixed it with Long Breaks and Others activities in between.

In conclusion I Always wanted to know what goes on beneath the beautiful front end of the computer, found out, and it was the most amazing thing ever.
I always had constant fun while coding (except for when you don't have fun) and really enjoyed it at most times.
I Just really love it.

About a year back now I noticed that I was really quite good at what I was doing and I wanted to continue learning and using my programming.
That's when I knew that shit was made for me.

...fuck that's a long read.

Best: I pushed myself to learn better about the field I am in and want to pursue. Also accomplished a few achievements because of my extra efforts.

Worst: It ruined my sleep cycle.

But it's all paying off.

feel super motivated to work on important project

Cant produce any actual work when sitting in front of it.

When not in front of it, badly want to go back to project to work on it.

Repeat cycle

Web3 truly is a fucked up space. All of the fuckertry happening over here is out of control. Literally a dystopian shithole of scams frauds crimes theft and ponzi schemes.... As much as i try to defend web3 since im a web3 dev it's getting real fuckin hard. The more i work in this space the more i understand economics and how all of this shitshow flows.

Without diving into details, I'll tell you right now from a very deep economic perspective: i realized that all of these cryptos are just.. shams, quasi buzz words to keep the "investors" giving them money. Essentially like wolf of wallstreet scams mixed with bernard madoff multi billion dollar ponzi schemes. The "investors" earn a lot of money.... But on paper! As unrealized gains. And by the time they are able to withdraw their money, that money becomes worthless because of insufficient liquidity in the pool that has been drained from top to bottom of the pyramid. So the only person truly getting filty rich is the one on top of this pyramid - the founders!

After the FTX disaster that happened 2 days ago the prices of ALL coins dropped drastically and it isnt stopping. So much for your glorified "decentralization" 😹😹😹😹😹

How can something be decentralized if its enough for 1 influential man to tweet some shit and the company/token price value drops or increases within minutes? In this case the whole of crypto got sliced by 1 influential man... Again. It's only a matter of time until someone else goes bankrupt and cycle repeats... Again.

interview today

me: and can you tell me a little bit more about your development process? e.g. an example dev cycle from reqs to testing and review...?

senior dev interviewing me:
*gives frustrated/annoyed "why tf are you asking these?" look*
So, uh, we don't really use testing for these projects cuz it would make it harder to refactor later.
(and responded nothing else on the topic)

I left shortly after that.

Ever since i was a little boy, i was fascinated by the stars in the sky and what made them shine. I used to wonder how our universe came in to being. What made it what it is today. What will happen to it long after we re gone. Will it die? Will it live forever? How big is it? Why is it big if it s big and why is it small if it s small. "God did it" was never a satisfying answer for me. God does not play dice as Albert Einstein said. So many questions went through my 10 12 year old mind. Until someone recommended to me the book, "A brief history of time". The book answered a lot of my questions and gave birth to more. Computer science is like my crush. I love it as a friend. But Astrophysics, its the true love of my life. It not only quenches my thirst, but it satisfies my curiosity, while making me more curious. Its an endless cycle. It teaches us that we came from the stars, we go back in the dirt, and only to be returned to the stars again.
Stephen Hawking, his work, his books, taught me so much. Inspired me. Made me more curious. And today the world has truly lost, one of its greatest people.
You will be missed Sir Hawking. RIP.

The inevitable cycle of a developer.

I have discovered a fresh hell

Some guy I’ve never met or heard of in the office lobbed a comment at one of my *approved and merged* pull requests. He doesn’t say anything specific, only that my REST urls are not in line with naming convention. That’s all he says, and I’ve already walked the URL consumers through the code and given them the URLS.

I’m really annoyed that this guy won’t just say what he has in mind, but fine whatever this is a professional environment and developers are not known for being a diplomatic people. Let it go and get your work done!

I do some googling and find an obvious change that needs to happen- I implement it, open a new pull request and inform my URL consumers of the change.

This rando still isn’t satisfied and still won’t say what needs to change. I am on round 3 of this wonderful cycle and this guy is acting all fuckin HAUGHTY about it. “Here is a list of conventions I found googling, you should read them even if it takes 4 hours because it will benefit your career”

Sure dog you’re probably right on that one but we are in a professional environment and at this point you are holding up production so you can wave your dick around! Just SAY WHAT YOU MEAN SO WE CAN MAKE THE CHANGES AND GET OUR WORK DONE

Excerpts from "Bastard devops from hell" checklist:

- Insistently pronounce git with a soft "G" and refuse to understand people not using that pronunciation, the same goes for jithub, jitlab, jit lfs, jitkraken etc.

- Reject all pull requests not in haiku format, suggest the author needs to be more culturally open minded when offending.

- increment version numbers ONLY based on percentage code changed: Less than 1% patch increment, less than 5% minor increment, more than that major version increment.

- Cycle ALL access keys, personal tokens, connection strings etc. every month "for security reasons"

- invent and only allow usage of your own CI/CD language, for maximum reuse of course. Resist any changes to it after first draft release

I've been asked to work a Sunday next weekend; and like an idiot I agreed. Wasting a beautiful summer day inside designing software for a company to push more fast food product and contribution to obesity and diabetes in the world.

This is my life, and I hate it here. I hate this industry. In my 15 years, I once took off for 11 months and lived out of two bags through Asia and Europe. I spent 5 months with just a car driving across America. It's fun, but non-sustainable and I had to find a job afterwards both times.

I need a way out of this cycle. I need to contact professors and get letters of recommendation and get into a PhD program (I have a masters already), but finding the time after exhausting days at work is .. well .. exhausting.

The most I can do after work is go hang out with friends or do something, but if I come straight home, I just fall asleep. I'm tired all the time.

Life cycle of a Software engineer;P

When an application is nearly complete and suddenly there is a recommendation thrown from management to change a technical specifications . Which will change the whole cycle effort meaningless. How does that feel?! Getting it now.

Programmer’s life cycle:
- Nothing can stop me today
- A bug huh? let's squash
- I can’t fix this
- Confidence crisis
- Questions career
- Questions life
- Oh it was a typo
- Nothing can stop me today

Trying to install macOS High Sierra. However the installation file seems to be corrupt. And it keeps rebooting halfway through the install cycle never allowing me to intervene and reset and revert to my previous iOS. Thanks Apple FML

Started off a developer 6 months back. I seem to have lost control of my life. I wake up at 8, be at work at 9am, get back home by 7 or 8pm, dinner, learn, work on my platform, sleep at 12am or 1am and the cycle continues.

I have no time for taking care of myself, no working out, no grooming, no family time, no time with friends, nothing naada! It scares me that I don't have that balance.

I always feel like I'm not good enough and I'm curious by nature, because of these, I sit my ass down and work / learn like crazy because I want to be good but I fear for my health, I'm 22, so I can live for now like this but this lifestyle will ruin my future, I've started getting back problems and shit, that was the wake up call!

How do you guys do it? work - life balance? I believe this information is vital for everyone starting out as a developer.

Life cycle...

Life cycle of code

1- See what sound code I have written! It's beautiful.

2 - Hey we missed something last time, just add this bit of tweak.

3 - We need to add some flags for some exception cases

4 - Hey there is a new requirement. Just add some more paths and more flags

5 - More flags!

6 - This shit runs now more on flags than on the design!

7 - Flagception!

Yesterday I had a good idea for a project I'm working on, so I decided to stay awake all the night drinking RedBull in order to implement it.

Eventually I went to bed. I dreamed I was on an island with some friends and a volcano erupted. We escaped from the lava boarding on a big boat, then a tsunami wave reached the boat. Boat didn’t sink, however electric power went down. When the electric power returned, on the boat screens appeared the following text: "Please, restart MySQL". However, under it there was the PostgreSQL elephant logo. I was someway more worried about that rather than the tsunami. After that, a hurricane was coming too. We were saved by people coming with a spaceship, however they appeared to be drunk. I woke up thinking «WTF!».

This morning my husband told me our 4 cats made fuss all the night.

Coming up on a year as a junior dev, nobody told me about the vicious cycle of the more I learn the more I want to keep learning. I would rather code than do lots of stuff I used to love doing. And the lack of sleep, oh the lack of sleep. Best career ever!

- be any programmer hired to a job
- do some cool thing that helps the business
- gets labeled as a smart programmer and a helpful team member
- get questions and cries of help from everyone at the office
- get burnt out and refuse to help some people
- get labeled as lazy, bad at my job, and having a bad attitude
- gets shadow fired
- cycle repeats

It’s time to burn down the houses of every rich person - and I hope we actually fully commit this time :)

This is a short tale that can be summed up as "oh fuck meee".

After finishing an API the night before I settled in for a day of bug fixes and tidy ups. Until slack went off.

The front end dev was getting an error, a code breaking error. After doing the standard process of request checking i went okay must be me. I find the script that is has the error and the line that it is failing at.

Que 2 hours of the full cycle of anger, sadness, pleading, and finally acepting that it had finally happened I had gone insane. The code was to documentation best practise correct and it still had the same error.

I the cheaked the DB on a whim and I found that my code was not wrong and it was doing exactly what I wanted the data however had a single record that was old and the schema had change juuussstt enoigh to break everything at that record. One 3 secound deletion later code ran perfectly.

Quick rant!!

Deadline in 2 days, working with a team.

Me: yo ! , How's the xyz feature? Is it working now?

Teammate: yah, made it work yesterday.

Me: epic! Can you present it to me?

Teammate: wtf, it's not working today!!

Me: no worries, you can sort it out!

Teammate: the latest release you worked on doesn't work properly.

Me: yah, merged code fucked up, I'm fixing that, I'll push a fix today.

And the cycle continues...

So... Heard back from a recruiter today. Lovely lass.

I’d passed over a submission for her tech demo.

The brief was basically just to create a small simple module that calculates shit, nae effort.

But, when the recruiter had me on the phone she said “I know it’s a silly small module but try and run it up like you would a production ready app”.

The job spec and recruiter were keen on me demonstrating TDD, not specific on js version, final runtime, etc. The job was a senior spec at a higher salary range. So it warranted some effort, and demonstrating more than a simple module.

“Okay, cool, nae bother, let’s crack on.”

The feedback in the response from the dev today:
“He’s over-engineered tests, build...”

SUCK MY LEFT TESTICLE YOU FUCKWIT.

Talk to your recruiters, not me.

The feedback included a phrase I never hope to hear from a developer I work with:
“Tests are good but...” 😞

It was a standard 98% test suite from an RGR cycle, no more or less than I’d expect in prod.

The rest of the feedback was misguided or plain wrong. It was useful to see because I know now when they say they have “high standards” they mean: we listen to the dude who put the factory pattern in a JS brief.

Oh shit also: “someone’s done chmod 777” was in there as a sarcastic comment in the feedback. It was his fucking unarchive tool 😞

My response was brief and polite: “cheers for the consideration, all the best, James”

It’s honestly not worth warning them. Or, asking why they’d criticise something they’d asked me to do.

If you want a shitty js module, ask for a shitty js module and no more.

New developers. Tip: There is no silver bullet.

If you like Python, please understand GIL's behavior before making a system that handles thousands of requests.

If you like Java, know that "Write once, run anywhere" is a fallacy. Even application servers don't like the same WAR.

If you like PHP, understand the life cycle of a request before connecting to the database from all corners.

If you like C#, don't make it a small command-line application that will be used on FreeBSD.

If you like C, meet valgrind.

If you like C++, templates are cool, but don't overdo it. And take the opportunity to meet valgrind.

Never use the same tool to do everything. Elect the language and framework for the given need with rationality.

Every time I see a "Java Man", a "C++ Chad" or anything like that, it comes to mind that if he were a carpenter, he would be tightening screws with hammers.

Every lock-in is bad.

I'm intentionally resigning from my remote software development job to teach my company a lesson. The guy who wrote the codes previously really knew how to cook spaghetti 😀😂.

To add a single line takes minutes, because when you do something else breaks, and you'll keep fixing what breaks when you tried fixing what breaks when you try fixing what..... endless loop of bug-fix cycle.

Now they blame it on me.

They won't understand if they don't get someone new, my reputation will fix itself through that..

My first opinion after sighting the codes was, "re-write the whole project using better patterns and architecture", the reply as you can guess, we'll do that later.

I couldn't even upgrade the server to use even PHP 7.1 because the framework breaks, the guy has editted a lot from the vendors files. Don't ever try composer updates.

Two word to describes the situation. "It sucks".

The previous developer needs to be shot, literally.

Bored waiting for a long running test cycle to complete, so...

Monopoly: Software Dev edition.

All properties are companies with apple and alphabet being the most expensive ones, course the online version plugs into stock tickers to accurately reflect the current share price.

All railroads are broadband providers.

You don't build houses or hotels, but patent portfolios and 'landing on another property' becomes 'infringing on a patent'.

Cards:
- Kickstarter refund, collect £200
- Hit by ransomware, pay 1bitcoin.
- You are sued in East Texas, go straight to jail, do not pass go, do not collect dividends.
- Get out of court free card.

Yeah, I'm that bored that I'm rewriting bloody monopoly...

PHP script life cycle

P.S.: 😜

School interferes with programming, programming interferes with school... when will this vicious cycle end?

Fuck you. Fuck you brain / body / wathever regulate my sleep cycle.

Went to sleep early, 9:30 amazing! Allarm is set to 4:30 I get 7 hours of sleep yay.

But no, let's wake up at 23:30 fully wide awake and do not be able to fall asleep anymore.

Now is 8:11 and on my way to the gym and then work I started yawning and I feel like sleeping.

Seriously? I would pick out that part of my brain, chew it spit it and then throw it to rats to feed on it.

Coffe where the fuck is my cofee??

Oh today is also the day we start an awesome new opencsource project that I was looking forward to. AND I AM TIRED AS FUCK.

Messed up my sleep cycle again! Its 5:30 pm here and I have just woken up. Now the night is going to pass by coding runs, gaming streaks and perhaps a movie. In the morning again I have to be at the office to work. Will have to stay awake for 30 hours or so. FML!

First rant, technically a sysadmin but getting into the nitty-gritty of programming with some things to improve my job (and hopefully moving into something more technical).

Have been doing a paid internship at my utility company. I do patch management with SCCM and sometimes the updates break. I've been using Powershell to reset the Windows update cache to make the computers work again. Unfortunately, this sometimes involves logging into machines to do some manual work and I have to notify users before I log in if they're already logged in.

Scripts can be run silently but I've spent a few weeks trying to automatically retry Software Center updates with Powershell … before realizing just today that the system center action "Application Deployment Evaluation Cycle" does indeed do the thing I've been attempting to do with Powershell for weeks now.

Wish me luck as I automate that part of the process and completely automate the sole job they gave me to do. Don't tell on me!

Never buy crappy, consumer-grade SSDs for use in production servers/RAIDs. This might sound obvious but at the company I used to work for, through a series of bad decisions by management and cheapness, we ended up with the cheapest consumer SSDs you can imagine powering all of our storage.

This turned into a nightmare spanning years of failed hard drives and a continues cycle of ridiculousness. Drive failed after a few days, gets taken out, sent back to manufacturer and then replaced with another equally crappy drive destined to fail within days/weeks.

Our ops people were going to the data center multiple times per week to replace failed drives. Lesson I learned: cheaping out on system-critical hardware and software can have long standing consequences and in the end usually doesn't end up actually saving money when you account for time employees have to spend dealing with issues that result from it.

Actually finishing a project.

I am a person who gets a lot of ideas for projects I want to work on, then I start writing the code for them, then I reach a wall, stop and restart the cycle all over again.

Fuck my life.

have you ever felt that you enjoyed and loved your job and coding, then after a while all of the joy, contentment and vigor just left together with the wind?

Well I have, and let me tell you the story of my peope and the feature whirlpool drain of death, slowly `agile`ing you to the death of creativity.

First everything was seemingly good, Its your product, a baby that every one is contributing to make, a great idea in the making.

Fastforward after the baby was fully materialize, and you are watching his first step, usually you are happy seeing his slow growth. But ITS A BIG FUCKING NO. He wants the baby to go faster, bigger and stronger, more than what he can chew. Then you watch as the baby grew into an abomination. A monster of undistinguishable and parts. It grew inhumanly large. BUT it never grew and it never matured. The baby sits there, and were just here injecting all sorts of stuff just to make his father happy. But the end of the day he will ask more and more and more, until the cycle goes on. The baby grows but does not mature, and were here trying to make his father accept the baby. But NO he like more. Sadly we have no power over this. we are mere slaves of the fathers bidding. his bitches, tools and nothing more...:(

I wish, I wish, I could finish off projects that I started even if that means I cannot touch new projects.

Fucking takes me ages to get motivation to start something, but then I start too many things and end up demotivated so I scrap all of them and the cycle continues.

Are you ready for the only really useful advice on devRant that is not judgmental, simple, and instantly applicable?

Here it goes. If you have hiccups,
1. Inhale your full lungs until you can’t inhale anymore
2. Hold your breath as long as you can
3. Exhale carefully

This will “reboot” your breath cycle, and that conflict between breathing and other things that causes hiccups will go away.

Repeat if needed. Breathe slowly and carefully after you finally exhale.

Much obliged if you stop reloading the folder and searching it every five fucking seconds you fucking cunts.

Good god damn this fucking 'feature' of windows 10 grinds my fucking gears. I hit 'x' to stop seeing the visual distraction of the fucking green loading bar when the folders already loaded. Same thing with music. All I want it to do is open and play my fucking song.

Does it do that?

No instead it spends precious cycles updating fucking indexes or sprinkling crack rocks on the corpse of my cpu or whatever cycle fairies at fucking microsoft programmed it to do while wasting my fucking time.

I wish I had a brick and a microsoft programmer within throwing distance, I'd be sorely tempted to nail the motherfucker square in his fucking big fat melon.

Cunts.

fuck count: 8

Fffuuuck you Nvidia, you worthless piece of shit company. There's a part of the world that doesn't use Windows. Grow the fuck up. Torvalds gesture makes complete sense when you get a new kickass laptop, load kickass fedora 25, but are unable to tap into it's graphic potential. You spend 2 days trying to install the fucking driver. The next day you decide to follow one blogpost instead of 2 and You're forced to reinstall fedora and the cycle repeats. The past 4 days have been painfully unproductive.

cycle dejavu

For the first time ever, I locked up a processor while working. Take that, 24 cores!

Unrelatedly, if someone is in the office, could you please power cycle my box? ...Thanks.

this is mostly how i feel today. we're all aware not much actually changes, but y'know, we survived this year, we get to celebrate a new cycle and hope for new and better things

Any day when I'm manic. Can work 12 hours without feeling tired. Also, 30% intelligence boost. Feeling like a god. Solving people's problems in minutes left and right.

It's unfortunate it only last a month tops, with the remaining year being deep depression. Matter of fact, I got diagnosed with bipolar type I when my psychiatrist mapped my awards from released products and articles to the timeline, and it resembled a bipolar cycle.

Management: List your most significant achievement during this cycle.

Me: Developed and implemented a full stack of database micro containers that allow scalability and reusability.

Well , this isn't a rant or a joke , so I just thought I should post it here in case people are going through a similar situation . So I know this guy , who works at this startup , so he had just joined the company and made a huge impression on the boss ( My friend is fantastic in developing ) , so as great as that sounds , it doesn't . After a year or so , he's been promoted and is now kinda a face for the devs of the company and this made his boss very cocky , like he would take so many projects or requirements of his top clients and place them on the shoulders of my friend and give a bad time limit , which is impossible but he always managed to just finish completing it . Naturally it affected his sleep cycle , his daily life and as a result , his mental health . As time went on and as more and more projects were being placed on him..........he finally broke , he used to miss so many days of work , not return any of my calls or texts , miss lunches , have breakdowns . I became very concerned and didn't want him to end it , I went to his place , spoke to him , found out that he had suicidal thoughts . Fast forward a year later , he's still going to a shrink , everyday but he's better now and after forcing him to talk to his boss and now his boss gives him plenty of time to finish the projects and said to be straightforward with how he feels and so on . I know this isn't what you would expect to find here but I just wanted to say after having this experience , please do not keep quiet , be straightforward with your boss and don't overburden yourself , if you're an introvert , tell it to someone you know , to tell your boss , and if you know anyone in a similar situation , do be out there for them . I'm sorry if this kinda spoils your mood , but people have to be aware . Be careful , lots of love people

So first of all I'm not a dev.

I'm a software tester and my test manager is a douche, but this is not it.

Today I went to the end user place along with him to teach them how to test properly and how to manage the software test cycle in JIRA.

I did a demo and showed the users the software the dev team developed and of course there were a lot of rants about it.
Users noted down a list of things to be changed and we kept going.

By the end of the demo, my test manager started discussing the fact that I told these guys to open Bugs without test objects on Jira.

I mean, we don't have a test cycle or test cased yet but these guys found issues already, what's the point?

So here's the funny part.

He then starts telling users (which ignore testing fundaments) to create a test cycle called 'meeting of today dd/mm/yyyy" and create tests below it which were named with the names of who created them.
All of that without a logic and ignoring the fact that these tests were not tests.

I was laughing my ass off while assisting this total mess and I almost lost control.

And this is my manager.

Luckily, tomorrow is Saturday.

HTML & CSS.

To me they just feel wrong.

I have been working with them for a little over 20 years now, and it feels like very little has improved. Sure we learned to make things look a bit nicer, we got new tags and properties, but the syntax is still horrible.

The fact that both are replaced by other imperfect languages (haml, jade, less, sass, etc) is just a confirmation that their paradigms are about as fucked up and impossible to exterminate as cobol.

Which points at another problem: browsers, and how slow the web upgrade cycle is — adding native support for nested style definitions in css, or replacing html with a json document seems like a trivial problem, if it weren't for the dozens of browsers and the excruciating pace at which they can adopt standards.

I tried LSD yesterday!

Backstory: I have a weird combo of bipolar type 1 and autism. During the day, my brain works inconsistently. Here how my day usually goes:
09:00. I wake up. Uninterested, cold, masculine. No thoughts in the background. No OCD.
12:00. Brain warms up. Thought process begins. Thoughts are short in their length
14:00. Thoughts start to get longer. Stress starts to accumulate. Background thoughts start, now typically 2–3 at a time.
16:00. Twitching begins. Thought chains are now 5–6 concepts long, one following the other. Perception level rises quickly. I start to feel more feminine. It is in this state that I start to spot imperfections and mistakes looking at code or text without reading it. I see it like a painting, and mistakes appear as “visually wrong” parts. This does not depend on formatting.
17:00. OCD becomes more severe. I HAVE to touch all the surfaces around me, evenly, as if my hands were text highlighters, and I had to paint everything evenly, without overlaps or spots that are brighter or darker than the others. Some surface textures become irritating, and feel quite unpleasant to the touch. If I go for a run now, like 3 km or so, I feel somewhat relieved.
18:00. Things are getting serious. Creativity levels through the roof. I speak in long, never-ending, profound sentences. Background and foreground thoughts almost become one. I appear visually drunk and happy, despite never drinking alcohol. Femininity rises even further. Sometimes, when I speak to a small group of people, especially if I go with friends to meet new people, and we go to some bar, new people ask to record my voice or to write down whatever I’m saying. To be honest, this reason alone is a huge boost to how I see yourself.
19:00. OCD is crazy now. Surfaces have soul.
21:00 <— Gotta take my meds and go to sleep here to prevent what comes at 22:00
22:00. All thoughts, both foreground and background, fully became one. Now my brain officially disobeys me and thinks on its own, and I can ride it like a surfer at best. Twitching becomes concerning. I develop a 1000-yard stare. I am officially a female. Physical strength is somewhat enhanced. Pain tolerance lowered significantly.
23:00. Derealization begins. The world around me appears two-dimensional and flat, like a picture. It is hard to get home on foot, even in close (less than one km) proximity. Brain is fully numb. All that thought monstrosity that was building up is just noise now. Zero “flops” available to think about something I want to think about, like how much money I have on me or what time it is.

I go to sleep. I see nightmares. I wake up, and the cycle repeats.

Contrary to a popular opinion, I never take any “brain-boosting” meds like antidepressants, and I think now you can see why. I consume neither alcohol nor caffeine. Neither me, nor my doctors want my brain to explode. I only take lamotrigine that helps to “lower down” mania, and quetiapine, a neuroleptic, that slows down my brain, like a neuroleptic. Both are there to slow down my brain, to kinda “throttle” my brain like a CPU to cool it down.

That said, 100ug of LSD just… brought me my usual 18:00 state, but in the morning?

All that small-dose recreational ordeal? The thing that helps people feel more energetic and creative?

People pay money… for that? To feel the way I feel every evening?

Hello, my name is Adam, I'm from Poland.
As a 16 year old dude I thought it would be a great idea to go to an IT focused highschool so I'd get my degree after finishing school but guess what- I completely fucked up.
First, there were the little things, like the teachers favoring other students that already knew stuff, which was okay and all- the problem began when Poziomka appreared (one of our PC service teachers). That motherfucker almost fluked me because of dumb shit like the PC's we worked on took forever to boot, so he's just go and give people F's, "Why?" you may ask- well because "It was obviously the student that made the PC run so slowely".
There were a few more incidents like when we were disassembling and assembling those dumb HP Compaq's PC's on time- and that fucker gave me an F because it took about 10 minutes to boot by itself.

That shit got me so demotivated its unreal, soon I found myself in a pretty dark spot, with my parents divorcing, my whore mother taking all the money- me not finding any reason to do anything in school and the cycle looped.
I'm not gonna pull the depression card here, but what I'm generally trying to say is that although I'm not "awful" at IT in general, so PC assembly, networking, programming (fuck that, I'm fucking awful at it), HTML, I still find it difficult to do anything right.

I have a question, how do I get myself back up? Any ideas?
There's so much material I've gone through in the last three years- and I just wanna make sure to get good- somehow.

I'm just a talentless dumbass kid who just wants to know how to do linux, programming and such, but I don't know where or how to start anymore.
If anyone has any stories where they turned their life around and managed to do IT right- please, tell me how you did it, I just wanna know is there a proper way of doing it.

- Adam

Almost every release cycle

Here comes the sleep time again. Now I will think about all the amazing stuff that I can build tomorrow and make it big out there just to wake up and do the same thing again and again till I go to sleep and repeat this cycle. Peace.

I don't know what you did yesterday, but i did make my company throw away 2 months of progress.
It all started in the beginning, since that i've made numerous complaints about the workflow or code and how to improve it. I've been told off every time, and every time i either told the boss who agreed in the end or wrote code to prove myself. Everything was a hassle and my tasks weren't better.
Team lead: you'll do X now, please do that by making Y.
Me: but Y is insecure, we should do Z.
Team lead: please do Y
Later it turns out Y is impossible and we do Z in the end...
Team lead: please do W now
Me, a few days later: i've tried and their server doesn't give http cors headers, doing W in the browser is impossible
Team lead, a few days later: have you made progress on W?
Me: * tells again it's impossible and uploads code to prove it *
Team lead: * no response *

After that i had enough. Technically i still was assigned to do W, but i used my time to look over the application and list all the things wrong with it. We had everything, giant commits, commented out code, unnecessary packages, a new commit introduced packages that crashed npm install on non-macs, angularjs-packages even though we use angular, weird logic, a security bug, all css in one file even though you can use component-specific css files...

I sent that to my boss, telling him to let the backend-guys have a look at it too and we had a meeting about this. I couldn't attend but they agreed with me completely. They decided to throw away what we have already and to let one of the backend-guys supervise our team. I guess there will be another talk with the team lead, but time will tell.
It feels so good having hope to finally escape this hellish development cycle of badly defined task, bad communication and headache-inducing merges.

I dunno about coolest, but I did sort of cement my reputation as the "database guy" in my first job because of this.

My first job was with a group maintaining a series of websites. Because of the nature of the websites, every morning we had to pull the records from one database on one network, sneaker net the data to a database on another network, and import the data via custom data import function.

However, the live site would crash after 100 or so records were imported. The dba at the live site had to script out a custom data partitioning script to do his daily duties, but it definitely messed up his productivity.

Turns out, the custom mass import function had recycled the standard import function, which was only used to import 1 record at a time, and it never closed its database connections, because it never needed to. A one line fix to production code was delivered 6 months later (because that was our release cycle) and I came up with the temporary work around, which was basically removing the connection limit. It would still crash with the work around, but only with multiple days worth of data. So basically only on Monday. Also developed the test set for the import (15k+ records).

I am back after 5 years

It's been a long time

After working for a shitty company, I ended up working for a startup for an interesting big project as a software architect

It was a good experience just for some stuff, but I hated every moment we needed to build some demo or prototype for potential customers or allies

I was tired... 2 years of demoing is too much. And finally I got a Senior Devops in this company working in Kubernetes

I finally discovered my role and my position, I want to solve problems for other devs and myself. I help anyway in the final product, because fast and reliable build and release cycle need to be a must

I wish everybody could find their main role. I took 12 years to find mine lol

Man it always feels like i know nothing. Like when you don't know HTML it feels like you know nothing .
Then you learn js, backend, some database.
But you don't know react so fuck you you know nothing.

Then you learn react, but you don't know vite, next
So you know nothing.
this cycle never ends
FUCK

Today I experimented a bit with Dockerfile's.
Was quite surprised how far you could go with a spicy salsa of ARG, ENV, SHELL and multi stage builds.

But... For fucks sake....the debugging is like poking a light year long rod into a black hole, trying to fish something out of the event horizon....

In the end I got a nice setup for Java build's, version injectable with ENV/ARG, non root user and version specific behaviour.

As the debugging is non existing...

I filled up more than once my SSD....

It was an annoying brain damaged repetitive cycle of changing Dockerfile, pruning all images if docker build stopped because of missing free space, waiting for all stages to complete, start new.

And caching is a fragile thing that puzzles me .........

Guess more fishing tomorrow.

*Gives a happy deep throat to the beer bottle in hope of death*

Undoubtedly the most common mistake that devs do : Ignoring your personal health, be it mental or physical.

I almost went through a burnout before realising things need to change.

Changed my lifestyle upside down after that
- Switched from wfh to an office job
- I cycle 12kms a day now
- Got a standing desk for myself to be more active
- and have a journal where i literally dump everything off my brain

A call centre manager is dictating the direction for the development of an app I'm working on.

Everything is working perfectly and then I'm asked to implement logic that makes sense to noone else but her. Then a week later shit breaks. Then I'm blamed. Then I implement a "fix". Repeat this cycle over and over.

I've started looking at local postings for a job in construction.

We had 1 Android app to be developed for charity org for data collection for ground water level increase competition among villages.

Initial scope was very small & feasible. Around 10 forms with 3-4 fields in each to be developed in 2 months (1 for dev, 1 for testing). There was a prod version which had similar forms with no validations etc.

We had received prod source, which was total junk. No KT was given.

In existing source, spelling mistakes were there in the era of spell/grammar checking tools.

There were rural names of classes, variables in regional language in English letters & that regional language is somewhat known to some developers but even they don't know those rural names' meanings. This costed us at great length in visualizing data flow between entities. Even Google translate wasn't reliable for this language due to low Internet penetration in that language region.

OOP wasn't followed, so at 10 places exact same code exists. If error or bug needed to be fixed it had to be fixed at all those 10 places.

No foreign key relationships was there in database while actually there were logical relations among different entites.

No created, updated timestamps in records at app side to have audit trail.

Small part of that existing source was quite good with Fragments, MVP etc. while other part was ancient Activities with business logic.

We have to support Android 4.0 to 9.0 of many screen sizes & resolutions without any target devices issued to us by the client.

Then Corona lockdown happened & during that suddenly client side professionals became over efficient.

Client started adding requirements like very complex validation which has inter-entity dependencies. Then they started filing bugs from prod version on us.

Let's come to the developers' expertise,
2 developers with 8+ years of experience & they're not knowing how to resolve conflicts in git merge which were created by them only due to not following git best practice for coding like only appending new implementation in existing classes for easy auto merge etc.

They are thinking like handling click events is called development.

They don't want to think about OOP, well structured code. They don't want to re-use code mostly & when they copy paste, they think it's called re-use.

They wanted to follow old school Java development in memory scarce Android app life cycle in end user phone. They don't understand memory leaks, even though it's pin pointed by memory leak detection tools (Leak canary etc.).

Now 3.5 months are over, that competition was called off for this year due to Corona & development is still ongoing.

We are nowhere close to completion even for initial internal QA round.

On top of this, nothing is billable so it's like financial suicide.

Remember whatever said here is only 10% of what is faced.

- An Engineering lead in a half billion dollar company.

Im listening to 8D music (sound vibrations in 8 dimensions) and it is weird as fuck

Feels like i am in a giant and small room in the same time, at place A while being at place B in the same time because the vibrations cycle around you to create an illusion of offset spatial divergence

During Summer I'm tired because it's too hot.

Now it's getting cold, it's getting harder to get out of bed...

And the heater makes me tired too...

Plus there's the not going out or, moving as much... Which may also be due to being tired.

And well in general, I seem to not feel like doing anything lately... Because I'm tired....

Seems like my routine is consolidating to: sleep, eat, work...

And if I had a choice it would just be sleep...

I need to get out of bed now so can eat and go work..... But I don't wanna.....

Is it just me? Any tips to break the cycle?

So I met this person via a social platform.

They were absolutely silly and weren't able to hold a conversation. So I, like a normal person, just stopped trying to keep things alive.

Over the years, I have realised and learnt that if a person is interested in being friends, they'd put in efforts and I alone will not have to drag things on my shoulder.

I started cutting out people right, left, and center who I felt were taking advantage of me or using me in some way or another.

I ended up saving a lot of time and energy. I no longer feel drained or anxious about something not working out. Not dragging saved me from draining.

Anyway, they reach out to me again after few weeks and I was like let's give it a try to establish a friendship, because befriending people is my weak point.

The cycle repeats. At first I thought it must be because of the asynchronous nature of the platform so I drop my Telegram Id in case they preferred an IM approach.

I swear in the name of sweet lord, the retard does the same behaviour. So, I stopped communication.

And one fine day, the person tells me that they lack social skills and want to learn how to make friends and stuff.

Very fair point. So, me being me, gave them a few tips and critically pointed out their behaviour on how they reply with a one liner after every 2 or 3 business days.

Absolutely no change in their behaviour. They kept texting me the same.

At this point, I was like why am I doing it? I could find better people easily. Because for me, communication is everything. I cannot function without a good communication between two living beings.

So, I asked them why are they even trying to learn social skills when they barely implement it and don't want to change to which they reply saying that so they can use it to befriend people and network to getter better job opportunities.

I fuck them off.

And fuck such people who have intentions, are not clear enough about it, and play people for their own selfish gains.

And this where another learning I got from @scout is have boundaries.

Why do all good people in my life leave? Damn it! I need those good people back and be friends with them and not retards who cannot even communicate beyond one liner.

Is it just my phone or does the gif never play correctly on the first cycle on devrant Android app.....?

Anybody else having screen addiction during the night? It ruins my day-night cycle for years now! FML

My cycle : windows - ubuntu - mint - fedora - elementary - kubuntu - apricity os - debian - windows.

Why? Because that damn linux has fucking problem with hybrid intel/amd gpus

Ever finish a project, feel fulfilled for a hot minute, then feel like you're still not as good as you thought you were and instantly start hacking away again?

This has been my cycle for the past 2 months.

At work, all errors within the site are logged into our database with a subject and error column. SQL errors are logged in the subject field while the traceback is put in the error column. However, a lot of SQL errors are really large and exceed the max character width of the subject field, causing yet another SQL error, and the cycle repeats. This recursive error has been the bane of my existence, because 1) it times my local dev instance out and 2) the error doesn't end up getting logged because the server both freezes and the error can't be inserted in the database. You can't even begin to imagine how many hours I've wasted trying to find what line I changed cause total and utter failure with absolutely 0 error logging. Next thing on my todo list is to fix this fucking issue since the head dev refuses to get it done.

So I am working on a cloud app, Angular on the frontend and NestJS with heavy AWS dependency at the backend. I took my time to learn the stack and I have a couple of years of experience with each piece involved.
Since I am a Level 1 developer, management thought (and I felt same way) it would be nice for me to work with a couple of Level 3 devs.

Well, they hired Level 3 devs:
- a senior Java developer who never touched AWS, any kind of frontend or Typescript
- a senior c++ dev with the same “never touched” as above

And guess what? I have to train them both in Angular, Typescript etc. Kinda defeats the whole purpose of L3, “they will help you to deliver stuff fast”, and adds load on me (I am already a shared resource on 3 teams).
Oh, and yeah, management already promised to release the app by the end of the year and so far I am the only capable and functional developer on the team who has to deliver everything.

I had so much hope for new hiring cycle lol

Cycle counters. Because having a fucking clock is a privilege.

i asked my dad for help with a GRUB issue (EFI file wasn't seen in my BIOS anymore, nor booted when pointed directly at, even after ALL THE CONFIGURATIONS POSSIBLE) and i walked away for a while, content he'd figure it out (there's still a few things he knows more than me about.) I come back 30 minutes later and he's zero-filled my main drive and is halfway through installing Win10. His reasoning? "I'm installing surveillance software since you won't give me your college passwords and I need access to your college's site and your account. I can't do that on Debian."

I didn't give him authorization for this, and I thought he had zeroed my backups drive too, but it turns out it was having I/O issues (my controller is finicky sometimes, a boot cycle with it removed fixed it, luckily I can't write to drives it doesn't like when it's being a shithead)

What do? I can't sue as he owns almost everything I use and the house I live in and would no doubt kick me out and take all "my" stuff, but I feel like this really can't go ignored. I can't just talk to him about it as he thinks anything he wants done has to be done as he sees himself as above all other people, so he just shouts me down...

Ok c++ professionals out there, I need your opinion on this:
I've only written c++ as a hobby and never in a professional capacity. That other day I noticed that we have a new c++ de developer at the office of which my first impression wasn't the greatest. He started off with complaining about having to help people out a lot (which is very odd as he was brought in to support one of our other developers who isn't as well versed in c++). This triggered me slightly and I decided to look into some of the PRs this guy was reviewing (to see what kind of stuff he had to support with and if it warranted his complaints).

It turns out it was the usual beginner mistakes of overusing raw pointers/deletes and things like not using various other STL containers. I noticed a couple of other issues in the PR that I thought should be addressed early in the projects life cycle, such as perhaps introduce a PCH as a lot of system header includes we're sprinkled everywhere to which our new c++ developer replies "what is pch?". I of course reply what it is and it's use, but I still get the impression that he's never heard of this concept. He also had opinions that we should always use shared_ptr as both return and argument types for any public api method that returns or takes a pointer. This is a real-time audio app, so I countered that with "maybe it's not always a good idea as it will introduce overhead due to the number of times certain methods are called and also might introduce ABI compability issues as its a public api.". Essentially my point was "let's be pragmatic and not religiously enforce certain things".

Does this sound alarming to any of you professional c++ developers or am I just being silly here?

Hitting a really deep, deep low in the manic-depressive roller-coaster of the development cycle:

There comes the crunch time. No meeting goes by hearing the odious: "We don't have time for that." - One critical component needs to be finished for Big Sur and instead of addressing the real issues we keep changing design and goal. One main dev already gave up fighting the PO and team lead(!) - and now I'm next. So that dev build this really clean and minimal library as the core part. But now it's just like, yeah, take that nice Porsche engine put it on the old rusty bicycle from the shed,.. but maybe because that's so shitty we need that specially formed exhaust pipe to tune it. Yeah, very 'agile' - Only thinking about it makes me shudder in disbelief and anger. I shouldn't take that shit so serious, be emotional about shit code, I know, but I can't. Let them drive some rounds around the block, if it runs at all,.. because until now we still didn't make it run on the fuckin' street. It's all so insane. Will make some nice fireball, when it goes up in flames.

Well, I have been part of quite some shitty projects. Real suicide commandos set out to fail, and somehow stood them through or made it even "work" though it should never have. But what enrages me here is, that it needn't to be that way. We had plenty of time. Our team was often rowing along in good rhythm. And now I just feel drowned in resignation and sarcasm.

Lord. Please deliver us from the cycle of unfinished programming languages and code benches that are designed to create more work for us. We beseech thee in thy mercy to transmute all this asynchronous lead that is found in javascript into a purer form of threading that is sensible and can be willfully blocked or not so in a way that works and does not divide us through our ugly code. May also we be given the ability to purge from our midst all child molesters and string them up by barbed wire off a line of telephone poles across the entire continental usa and may there be a sudden increase in the number of ravens and buzzards to feed on them, being nice birdies that I miss seeing so much. May half their positively identified population be kept alive and delivered unto us that we might remove their scrotum with a hook-ed barb and something resembling a serrated metallic spork, amen.

and please fix fucking node js. i agree that its asynchronous methods suck ass for literally everything as there is no use for it that seems to work given its a shitty emulated single thread.

Oh look, the testers are using a production version of something when they should be using the TESTING version

iT DoeSnT wOrk!!!!!! aAaAAAaaaA

And the cycle continues...

Typical development cycle:

Spend hours trying to think of a solution to a problem.

Get epiphany and implement possible solution.

Be afraid to compile it in case of bugs or errors

QA: There is a problem
Me: Ok how do I reproduce it?
QA: You do x
Me: I have done x and there isn’t a problem
QA: Oh it only happens sometimes
Me: Fair enough, I’ll try a few times
...
Me: Are you sure x is how you do it?
QA: Oh no actually it’s y

FML

0 bytes of heap allocated per cycle! Figuring out the Unity profiler actually helped me improve my C# optimization. <3

So I started working at a large, multi billion dollar healthcare company here in the US, time for round 2,(previously I wasn't a dev or in IT at all). We have the shittiest codebase I have ever laid eyes on, and its all recent! It's like all these contractors only know the basics of programming(i'm talking intro to programming college level). You would think that they would start using test driven development by now, since every deployment they fix 1 thing and break 30 more. Then we have to wait 3 months for a new fix, and repeat the cycle, when the code is being used to process and pay healthcare claims.

Then some of my coworkers seem to have decided to treat me like I'm stupid, just because I can't understand a single fucking word what they're saying. I have hearing loss, and your mumbling and quiet tone on top of your think accent while you stop annunciated your words is quite fucking hard to understand. Now I know english isn't your first language and its difficult, I know, mine is Spanish. But for the love of god learn to speak the fuck up, and also learn to write actual SQL scripts and not be a fucking script kiddie you fucking amateur. The business is telling you your data is wrong because you're trying to find data that exists is complex and your simple select * from table where you='amateur with "10years" experience in SQL' ain't going to fucking cut it. Learn to solve problems and think analytically instead of copy fucking pasta.

I want a tool called "bogo-npm" which creates a VM and then installs random versions of npm and dependencies in a cycle until the build is successful. It'll probably be the biggest optimization that dogshit ecosystem has ever seen.

I'd just let it run over night and save myself the urges to strangle every single fucking developer who added dozens of dependencies to a stupid near-static website.
And the creator of the abomination called `npm uninstall` which for some fucking reason does the same as `npm install` and then obviously fails because that's the reason I wanted to remove that package in the first place.

We need more heroes like that leftpad dude.

How long is your operation system running?

Linux - since the first kernel release I've ever touched.
Windows - depends on the update cycle, mostly 2 weeks up to 6 month.

And there goes another night with reconfiguring my windows session 🤬.

[Rust]
I have a bunch of computational steps in a Rust program, all very expensive. They all depend on each other, forming a cycle-free and rather small graph of dependencies which is not a tree. The results of each of them for a given input are likely used tens of times by the others, so I would like to cache the subresults dynamically.

How would I go about doing this, considering that caching (rightfully) requires mutable access to the cache and multiple operations often refer to the same subresult?

I can't ask SO because they'd just tell me to use another language or recalculate everything every time, fully convinced that difficult questions can only emerge from design mistakes.

!dev

I have this urge to get better at coding and software architecture and design. But fuck me if I'm not lazy about it.
All these crazy good books and lectures and here I am, doing jackshit to improve. Can't even finish my own personal projects. Bah.

I know how I'm supposed to go about it, how to keep engaged in a cycle of personal betterment. I lack self-discipline to do it though... Tried meditation for a time, but haven't really stuck to it. Currently trying to follow stoics (Seneca, Marcus Aurelius and some others), but the mindset is not so easy to adopt, and the practical philosophies even harder.

Oh well. Life is hard. Blah-blah-blah. Thanks for reading. Just wanted to vent, really.

I always love to stare the application that I develop... First I start with admiring it... then the things that could have been done to enhance the feature.. then the bugs that could only be seen by me.. then all these results in new update of the application and this cycle continues 😂

I keep taking breaks from what I'm working on coming back and adding more spaghetti on top of the spaghetti because if I start rewriting the spaghetti I get in a cycle of rewriting spaghetti several times and getting nowhere

Why am I so indecisive =-=

But also I think I might have to rewrite the spaghetti again. Can my opinions stop changing pls

It's was the forth year of my college, in the corner of the world in south India, I wanted to something to combine both medicine and the coding that I learnt, I started learning about heart murmurs, it's basically a skill based diagnosis that only 1 in 20 heart specialists can make by hearing the heart beat and listening to a small murmur that happens during the systolic cycle or the diastolic cycle. I wrote a program to learn a lot of sample murmurs and try to find (very bad hand made logic) the similarities between two wave patterns, the problem started with noise so I went out and built a new stethoscope with a carbon mic inside a normal stethoscope head and try filtering the sound at source (worked well enough at that time) I then tried to find people to test it on, but alas I was not able to find patients as doctors are not supposed to reveal them etc. I wanted to show them visually how a murmur pattern would look like and I stole some code and made a plotter for the wav file and presented everything. By that time I got a lot of close amazing friends involved and they helped me solidify the project and we won the best project award and I got my first gold medal of my life at the end of my academic life :) it was one of the best moments of my life. Second only to the joy of getting married to wife. May be third if I put getting a job in Microsoft India Development Center.

I still wish I could dig that code up and write it properly with what I have learnt today but work is never ending and I find great problems to solve everyday which I know I can make a difference, may be when I get retired I will dust out that CD with the decades old c++ code and write one last program...

Meanwhile, inside the kernel of my device that has a relatively frequent release cycle...

if (!isLatestVersion()) {
forceUserToUpgrade();
}

forceUserToUpgrade() {
extraSleepForCpuSoDeviceBecomesSlowAndUnusable++;
}

This fucking internal tool does not have any CLI capabilities, so to open each file i need to and get the data i have to manually hit 'File -> Open' select the file, then double click

Then high light the data i want and copy out what I need

If there was even just a cli to cycle over the fucking files to open each in their own instance it would be a good deal less fucking tedious and annoying

Like how the fuck do you not allow passing in a file name on cli to open like fuck i have to do this 40 fucking times FUCK i get this tool is originally from the fucking 90's but still you push updates every 3 months for the databases it accesses at least let me fucking pass in a fucking file to open it from cli

Every side project's life-cycle.

I always write a Google Doc before I start developing a feature to help me think what and how should I implement it and so I can share it with the team.

It is possibly the most frustrating process of the whole development cycle because Word and Google Docs still manage to make it a fuckin ordeal to insert a simple image without bombing the whole text to hell. How is it that after almost 30 years of history it is still shit to write a document?

I’m really bad at closing my tabs. I’ll often have 40+ tabs open when tackling some sort of problem or when doing research. Sometimes I’ll crack open another browser instance to research something unrelated. I use a tab session saver to save all of my instances before a reset. But the funny part is, I almost never go back into my stored sessions. I’ll just open up a fresh browser after restarting and the cycle begins anew.

I need help.

Agile/Scrum is the worst project management style in software development.

Rather than focusing on delivering a feature or changes on the project, everyday there is always a meeting that you need to attend to, other than the daily huddle. And those meetings are none of your concern or why they needed you there

And my Product Owner and Scrum Master does not know even though how software development cycle works. When you discuss technical details or constraint to them, they either look confused or don’t know what to say and just say “If you need anything, always communicate or approach me” even you already told them the issue.

Or maybe we are doing it wrong. But it is been 5 years when they implement this Agile/Scrum and we are still bad at it.

Just ranting

An iterative process of "plan, do, test, improve" shouldn't leave an engineer's head. If we outsource "plan" to a manager, "test" to another blabbering idiot with a corporately purchased donut hanging off his mouth, the cycle becomes too long to actually work. Multiplied by an engineer's despair because he's obviously clever enough to see the whole picture, this is a recipe for disaster.

Throwing man-hours in there won't solve anything.

Why don’t you like sharing your salary with coworkers? I tell people exactly what I am paid if the conversation comes up. It helps to know where you stand, i.e. if you’re being under paid or if you should ask for more in the next review cycle.

I am a fresher in web development. I have already learnt to use nodejs, react, angular, vanilla js and made many projects. Majority of the work I feel is just CRUD based, sure there are some exciting things but they are only of a small percentage.

All that innovation HAPPENING is just glorified way of making a CRUD APP ONLY.
Oh mvc worked great on server side let's bring it to client side
OH mvc is such a mess, who thought about doing this.
Oh react redux is so revolutionary let's remake our app using it,,
Oh es6 fuck yeah, Babel, webpack sure, now my crud app is super performant.
Oh graphql, motherfucking cutting edge CRUD APP......

I need to know what's next, is there any breaking of this cycle

There's this odd thing that I'm experiencing in the moment of falling asleep.
I somehow remain conscious and can feel how the unconscious part of my brain opens a sort of portal to a dream world. I begin to hear sounds and my speed of thinking becomes slower.
That's when I get a panic attack and I am trying it again. After the 2nd or 3rd try, it usually works and I wake up in the next morning as if nothing happened and the cycle repeats again lol

That makes me wonder if a "healthy" way of dying will have this sort of transition as well.

*Writes CloudFormation Template.*
*Launches Stack*

Starts Murmuring,

"The cycle repeated
As explosions broke in the sky
All that I needed
Was the one (JSON Invalid Format :| ) thing I couldn't find
And you (Teammates) were there at the turn
Waiting to let me know

We're building it up
To break it back down
We're building it up
To burn it down
We can't wait
To burn it to the ground

Me: "FML :| "

By working for the matrix all of my biggest propositions worries concerns and probabilities are now being confirmed. Giving 1/3 of your life every day to the matrix, gets you home so exhausted and drained that you need to sleep or rest on couch for 2/3 of your life and before you know it it's time for bed to repeat all of it again by sleeping for 3/3 of ur life. And the matrix cycle repeats till death. You are basically a slave robot who works, rests from exhaustion and then sleeps so you could repeat the whole cycle tomorrow.

This is my biggest fear. This is my worse fucking living nightmare. How can people tolerate this? I mean sure if i was paid a million dollars a year I could tolerate it. But this is bearly bearable. I have to escape this box

Everytime I consult with senior devs on how to transition from my sysadmin job and get my first dev job they always tell me to get a CS degree.

Look. I will get that fucking degree eventually. But I want to build up dev skills and learn from a company before killing myself over math crap for 3 years. But it's like a vicious cycle. Every junior position I apply to rejects me because I have no degree.

I'm fucking frustrated and depressed.
What should I do? I want to break from the IT meme and get a dev job.

In the meantime I'm doing small projects and freelancing in my very little free time. But I feel I'll never truly be a developer until I work as one professionally.

I hate myself. I have insomnia. Sleeping is hard for me. I can be easily waken up by little movements, change of temperature and even little noise. Also I have a nasal cycle. When I'm asleep I can even wake up because of this stupid nasal cycle.

A long deep uninterrupted sleep or breathing in both of my nostril is heaven for me.

Every person project cycle.
1.thinking 2.making bitbucket private repo 3.Making slack channel for contributors.4 Explaining the idea 5.the end.
I seriously need to work after step 5

Ok so I had a phone interview with a start-up for an internship and didn't get a call, for like a week(actually more) but today they called and wanna meet me tomorrow for work. Problem is, I fucked up my sleep cycle, big time. I hope me requesting to meet them at 7pm won't cause a problem!

Finally have some side project in mind but now I don't have the time. When I had time I was not well mentally to do anything. When is the cycle going to break? Work - burnout - recover - repeat 😣

For all things, for all men, that a man compliments a thing does not imply that this man at least attempts to understand this thing. However, for all men, that a man criticises a thing implies that this man at least attempts to understand this thing.

For all computer programs, that a computer program is terrible implies that scrapping the current implementation of this computer program and beginning anew may be the best method of fixing this computer program.

With few exceptions, for all programming languages $l$, given sufficient effort, $l$ source code can be human-readable.

The UNIX philosophy never became outdated.

For all computer programs $p$, $p$ should be written sufficiently well that the author of $p$ can be prideful of $p$.

For all computer programs $p$, a specification for $p$ should be written before $p$ is created.

For all good computer programs, a good computer program can run on terrible hardware.

Every clock cycle is valuable.

Am I the only one spending like 70% of my work-time tweeting and the remaining 30% coding like crazy at super fast speed?

And still make it all work super properly :D

I'm way past the point of being pissed now....

So there's some software (API's, mobile app + website) that I wrote to manage supplier incentive programs in a big hurry last year - which lead to a bunch of stuff being hard-coded in to launch on time. So after last years promotion was done I took down all the services etc was very fucking clear that in order to finish & deploy it to run again I would need at least around 4 months notice.

On the surface its pretty simple but it has quite a large user base and controls the distribution of enough cash & prizes to buy a small country so the setup of the incentives/access/audit trails is not something to be taken lightly.

Then once I'm done with the setup I have to hand it over to be "independently audited" by 3 of the larger corporate behemoths who's cash it distributes (if I get a reply from one in 3-4 weeks it's pretty fast).

I only happened to find out by chance an hour ago that we are apparently launching an even larger program this year - ON FUCKING MONDAY. I literally happened to over hear this on my way for a smoke - they have been planning it since last year November and not one person thought it might be kinda important to let me know because software is "magic" and appears and works based on the fucking lunar cycle.

When your company ask to put your views on Glassdoor and you don't have any good to say.
#vicious cycle .
Life is hell

Tl;Dr: Client has no idea how much development costs

(Un)potential client has been asking to develop an AV solution for Android phones to sell on the play store. Problem is I know they're cheap fucks and won't pay for a proper development cycle. Just for an exercise I put together the minimum cost they are looking at if they cut back on a lot of things and purchase lots of things off the shelf and gave them a bare minimum cost of £4350. Which is utterly fucking ridiculous to think you could develop something even half decent for that. I mean we all know that AV is a bit of a joke for any serious threat, it just protects from the billions of pests in cyberspace, but I mean come on.

Anyway, they are freaking out because apparently that's a lot. Out of interest, what would be your ballpark figures for this.

Fuck you GREEN CHEMISTRY!
Fuck you SULPHURIC ACID
Fuck you NITRIC ACID
Fuck you U.S. PRESIDENTIAL GREEN CHEMISTRY CHALLENGE AWARDS
Fuck you WATER PHASE CYCLE
Fuck you CARBON DIOXIDE

ahhh! finally its over...

shit FUCKING PHYSICS EXAM STILL LEFT !
Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaahhhhhhhh

You know what's worse than having to come up with a new password every time you create an account? Forgetting your password every time you try to log in!

I swear, it's like my brain has a selective memory when it comes to passwords. I can remember every lyric to a song from 10 years ago, but I can't remember the password I created yesterday.

And don't even get me started on password manager software. You would think that having all of your passwords stored in one place would make things easier, but nope. I've forgotten my password for my password manager so many times that I'm starting to think I need a password manager for my password manager.

But seriously, why do we even need passwords in the first place? Why isn’t there an easier one stone kills all solution to all these password authentication nonsense?

I could remember when it was all letters, then forced to use letters + numbers…

then later forced to include symbols…

and then forced to make it lengthier…

and then solve puzzles after getting it right…

and after all the stress now we are forced to find nemo from a set of images.

I thought the misery would end there but nope. Now some platform forces 2FA like dude seriously?

For God’s sake we built self driving cars already! Why can’t one just exist without a password? Why do we always end up in a password cycle?

And please don’t say shit about oauth because if your password master (i.e: google) fucks you in the ass then all your oauth accounts are gone for good!

I'm currently having an existential crisis about the meaning of passwords in our modern society. Shit is crazy when I ponder about it I get worried.

how many of you have a bike?
If you have a bike, share a pic