As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

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

This is one of my favorite quotes when it comes to programming. So many developer are too eager to start coding instead of spending a bit more time on thinking.

Words of wisdom (WOW) !!

If only more manager would think like this! Constant interruptions are poison to the performance of any dev team.

This should not be called wisdom teeth, should be called stupid teeth
Mother fucker is growing perpendicular.

What fuck is wrong with you bro , grow upwards you dumb fuck!!

Golden words of wisdom

The right mood.....

Wrote my friend Sam a letter when I was still working in support. I think it still holds up today.

---

Dear Sam,

I understand that you will join us in our overseas office. Congratulations on landing that job. It’s good steady work. I’ve been doing it for the last ten years.

Your still young so maybe I can give you some little wisdom that will help you in your working years to come.

Let me begin by shedding some light on phone calls.

I try. I really do try Sam. But it is getting so hard for me to hold back the rage that builds up during certain phone calls. Especially the ‘Sorry, I just don’t know anything about computers! -giggle-’ ones.

Those are the times that I have no access to what they see. I’ve no team-viewer, can not take over that screen in any other way. And why-oh-why can I not take over that terminal session dear Sam? It’s because the caller can not double-click an icon or find a terminal session number.

And what is the reason for this? Because they ‘just don’t know anything about computers! -giggle-’. This is a sort of get-out-of-jail-free card. Beware of these callers Sam.

There is nothing so nerve-wrecking then finding yourself at the mercy of people describing Internet Explorer (do not even get me started) as ‘the big ‘E’, if they use Chrome for their webmail then they most likely will say ‘Mail’ if they mean Chrome. There is no logic Sam. That is just the way these people work.

They will suck all enjoyment out of your work. They will make you want to hunt them down in dark office hallways and show them your tears Sam. Because cry you will.

Sure, I understand that not everyone can be tech savvy. Why, if everyone would be, where would that leave us? No. I love the technologically challenged. They put the fiber in my internet. They make me LOL for real. After the initial anger subsides anyway.

But just below that well-willing folk, on the other side of that border… there they dwell: Management.

Nice cars, suits and iphones Sam. First thing a new manager will require is a brand spanking new business-card. It will hold his/her new title. Then an iphone or overpriced android model will follow suit.

Then they will barge into your office, holding it like it’s the next best thing since sliced bread.

Any manager will automatically assume that you will drop anything you are doing at the present moment to acknowledge the presence of greatness. Failing to do so will result in awkward yet fulfilling situations. I recommend that you do not take your hands of the keyboard and give only the slightest of nods after 5 minutes of complete silence and glaring.

Well… you feel the glare. You do not glare yourself. You do not break eye-contact with the monitor. It does not even matter if you are typing for real or not. I once clicked away happily for 5 minutes. I just typed ‘he is still there’ over and over again. Do not break down Sam. This moment will decide your relationship with this individual.

After the nod there will be a flood of words aimed in your general direction. You can disregard anything that is said. It boils down to ‘can not operate device’.

You then take the device from this person and put it next to you on your desk. You’ll ask the name of this simpleton, write it down on a sticky-note, slap that on the phone. Then you’ll write a random date in the not so near future on another sticky and hand that to the bewildered person in front of you.

It will usually utter some incoherent words about ‘needing, time or but’ (I find that ‘but’is a word they like. They tend to use it three or four times consecutive before you usher them through the door).

Now you’ve won Sam. Well… not really. But it will feel good, I can guarantee that.

This must do for now. A new suit is glaring at me for the last five minutes.

Felt good to do something productive with this time.

Take care,

Baltasar

P.s. I just noticed that there is some foam around his mouth. So if you encounter this, don’t worry: it seems to be perfectly normal.

Nobody can teach programming, programming teaches you...

WRITE IN C ('LET IT BE')
When I find my code in tons of trouble,
Friends and colleagues come to me,
Speaking words of wisdom:
"Write in C."
As the deadline fast approaches,
And bugs are all that I can see,
Somewhere, someone whispers:
"Write in C."
Write in C, Write in C,
Write in C, oh, Write in C.
LOGO's dead and buried,
Write in C.
I used to write a lot of FORTRAN,
For science it worked flawlessly.
Try using it for graphics!
Write in C.
If you've just spent nearly 30 hours,
Debugging some assembly,
Soon you will be glad to
Write in C.
Write in C, Write in C,
Write in C, yeah, Write in C.
BASIC's not the answer.
Write in C.
Write in C, Write in C
Write in C, oh, Write in C.
Pascal won't quite cut it.
Write in C.

Saturday late night wisdom.

Software developers you need to work on communication skills.
Everytime LinkedIn says need a problem solver. It means a guy who can understand what non technical guy is asking for and translate that to a software or at least come up with a example of why he is wrong. Explain them. They are not dumb fellows for asking that feature. You might think the feature is stupid. Don't assume this. Sit with them. Understand thier user flow, understand the frustration your software is causing them. Then you'll see why are asking for that X feature.

Every feature request made is basically my opportunity of understanding of product. Don't wait for users to tell you requirements. Understand and suggest, implement prototypes and show them, a causal question such as "Hey would you think providing a keyboard shortcut for this submission is great?"

Understand our job is not just to write software.

Our job is to solve thier problems using software knowledge.

Don't you agree ?

Knowledge is knowing how to fix a computer.

Wisdom is knowing to start by rebooting.

The trick is to meditate instead of masturbate

!rant

My personal wisdom of the day: You know you are getting older if you are too lazy to crack you program licenses and instead buy them legally.

"HTML and Css don't work well together" - some wisdom from my coworker after meddling with some height settings in css

Weekend weekend weekend. Yay!
After hard week at uni, took a day off and I am in bed since morning 😁
So I decided to find some kind of "dev social app" and got this. Not bad at all!

I am also fairly new at web development, using Python - at the moment Flask, later on Django so I am looking forward to meet some Flask/Django users here :)

And I just wanna add some wisdom here:)

!rant

Some days ago I finished "Ray tracing in a weekend" (Peter Shirley) and I'm learning a lot :D

In the new year I will start with "Ray tracing the next week", but there are still some things I want to tackle before that (improve code quality, optimize... it's my first project that is bigger than a codeforces problem solution, a part from the projects at work).

Any sources of wisdom and recommendations are welcome!!

What a great start to 2019 for me.

Uncles and aunties who don't understand a thing about development critiquing my work and offering their advises and vast wisdom based on their 1 second knowledge.

I almost turned to a psychopath.

Lol.

Some words of wisdom passed on by our Scrum.

1. I am responsible for setting boundaries. Work time, sleep time, family time, me time. If I don't set them properly, things WILL get unbalanced very quickly. (And I would add, burnout will follow closely).

2. Being productive isn't about doing more and more in less time. It's about doing only the most important things well, and either saying no to the other things, or finding another way to get them done. (Prioritize!)

3. I can't win (let alone run) a marathon by thinking of it as a 26 mile long sprint, or a week as a five day sprint. (Eat a digital elephant a byte at a time).

4. Loved ones are good judges of when things are in and out of balance.

5. Taking time off is essential. Vacations, yes, but also nights and weekends. (Or you WILL burn out and hate what you do).

Comments in () are mine.

Starting next week I’m going to be a programming teacher.

Suck my nectar of wisdom!

If you need to learn/teach object orientation, these are my approaches (I hate that classic "car" example):

1) Keep in mind games like Warcraft, Starcraft, Civilization, Age of Empires (yes, I am old school). They are a good example of having classes to use, instantiating objects (creatures) and putting them to work together. As in a real system.

2) Think of your program as an office that has a job to do, or a factory that has something to deliver. Classes are the roles/jobs and objects are the workers/employees. They don't need to be complex, but their purpose must be really (really, really) well defined. Just like in a real office / factory.

3) Even better (or crazier), see your classes and objects as real beings, digital creatures in a abstract world, and yourself as a kind of god, who creates species (define classes) with wisdom. Give life when it is the time for them to come into the world (instantiate object) and kill them when they are done with their mission (dispose an object). Give them behavior, logic, conditions to work with, situations where they take action, and when they don't. Make them kinda "smart". Build them able to make decisions and take actions based on conditions. Give them life. Think on your program as an ecossystem. There must be balance, connection, species must be well defined and creatures must work together to achieve a common objective. Don't just throw code and pray for it to run. Plan it.

-----

When I talk about my classes like they are real beings, and programs as mini-worlds, some people say I am crazy, some others say that's passion.

It is both! @__@

My friend brought me this, saying "I just found this in my junks, thought it might be useful for you. Weren't you a programmer?"

At first I thought I should explain about how fast everything changes over here and how it is out of style to talk about 2000s technologies, let alone a book from 1973!
I just said "Thanks! In fact it is a precious antique. I'll add it to my collection."
It really is.

"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live."

John F. Woods

(found this in a demo snippet)

Udemy courses are targeted at ABSOLUTE beginners. It's excruciating to pull through and finish the course "just because". And some of these courses are jam-packed with 30-60 hours just for them to appear legit, but the reality is the value you get could be packed to 3-5 hours.

You're better off just searching for or watching for the things that you need on Google or YouTube.

You'll learn more when building the actual stuff. Yes, it's good to go for the documentation. Just scratch the "Getting Started" section and then start building what you want to build already. Don't read the entire documentation from cover to cover for the sake of reading it. You won't retain everything anyway. Use it as a reference. You'll gain wisdom through tons of real-world experience. You will pick things up along the way.

Don't watch those tutorials with non-native English speakers or those with a bad accent as well. Native speakers explain things really well and deliver the message with clarity because they do what they do best: It's their language.

Trust me, I got caught up in this inefficient style a handful of times. Don't waste your time.

Just started reading this book ..
The first chapter and half are pretty interesting.
Their explication of Optimal Stopping and “The Secretary Problem” made think about scenarios where its possible to use in my life.

Ps: I think that what the books wanted!

TIL...

Google - I was going to type 'escaping # in json objects' but I am genuinely interested in what wisdom this Internet doohickie thang has on escaping polygamy...

My CTO in the 'good old times', when he still talked to me and shared his wisdom, once told me what I should know about oop and explained me the world of programming and what really matters:

CTO about oop and C#:
"I think this object orientated stuff is overrated and useless. You don't get finished. I write everything in one file. You should do that too. The fastest way is always the best one."

So, dear readers, you might think, he maybe understood, what oop means. I have to disappoint you. He is as FUCKING STUPID as he sounds.
He didn't understand the whole concept of the language C# or oop.
He doesn't use properties, every single method is static void and there is nothing like an object.

Since there is more from where that came from, this will be continued...

If you wait till the last minute it only takes a minute

Can't argue with this

When you just can't figure it out

Word Porn

JavaScript is like a gun.. if you don't know how to use it you will shoot yourself.

I'm cracking up...

"chatGPT will ruin the software interviewing industry!!!"

uh.... what does it tell you about our industry if a fucking ROBOT can "ruin" the interview

well, you're right. it tells you that only algorithmic robots do well and subsequently earn the top spots at software companies after interviewing.

creativity, grit, perspective, wisdom? that stuff is absolute bullshit!!! (and as a feeble human I can't figure that out in an interview anyway!!! better just have you solve leetcode problems ad naseum!!! that'll get us the best employee!!!)

god i hate the dumb fuck rat race. good thing i'm not in it anymore! peace out, girl scout✌️

Oh boy.

I've been partially on-loan to another team that's relatively new at the company for a couple of weeks now, mostly to help them get some testing sorted out, and had scheduled a call with their lead the other day. The call basically started like this:

Lead: Hi
sudo-woodo: Hey
Lead: Okay, so let's talk about <subject>, but I guess you've been told the news
sudo-woodo: What news
Lead: I'm putting in my notice

I love listening to seniors because they always drop some wisdom, but this was some serious wisdom. Guy sounded exhausted at everything, talking mad shit about the company and certain people and I'm just here like 🍿. Seems understandable, a lot of butting heads with the higher-ups and not being able to do his job properly.

Unfortunately we all kinda needed him to do his job because his job involved juggling fifteen different things that the project (and like 90% of my backlog to be honest) depends on.

shit's fucked 🙃

Hi devranters, I come to you for your wisdom...

Today a job offer was given to me in Poland with 2500 to 3000 euros after taxes + house + house expenditure + montlhy flights to my home country.

What do you think?

Devrant...
... give me the serenity to accept code that don't work
... The courage to fix code I can
... And the wisdom to find the typo before I throw my pc out of the window.
Amen.

- hold yourself accountable for your mistakes
- keep track your mistakes and learn from them
- put thought in what you do
- be organised
- become comfortable asking for and offering help
- realise that some problems have no universal solution
- don't just copy what others do, but also think for yourself
- learn to be patient

"Hard times make good developers
Good developers create good frameworks
Good frameworks create bad developers
Bad developer make hard times" - Wisdom from internet

!dev

got 4 wisdom teeth pulled thursday, and i've been without solid food for 3 days

help

"Most coders think debugging software is about fixing a mistake, but that's bullshit. Debugging's actually all about finding the bug, about understanding why the bug was there to begin with, about knowing that its existence was no accident. It came to you to deliver a message, like an unconscious bubble floating to the surface, popping with a revelation you've secretly known all along. A bug is never just a mistake. It represents something bigger. An error of thinking. That makes you who you are. When a bug finally makes itself known, it can be exhilarating, like you just unlocked something. Because, after all, a bug's only purpose, it's only reason for existence is to be a mistake that needs fixing, to help you right a wrong. And what feels better than that? The bug forces the software to adapt, evolve into something new because of it. Work around it or work through it. No matter what, it changes. It becomes something new. The next version. The inevitable upgrade." - Elliot, Mr. Robot

Another smartass! Here we go!

Look, I'm an idiot and I'm absolutely aware of it. But you don't get to give an opinion without having the knowledge or skills. I may be young-ish and stupid, but that doesn't mean you're right, or that you know better than me ffs. If I'm down to earth, that doesn't mean you're above me. If you want my respect, then behave yourself. Just because you think you've "schooled me"...doesn't mean you did.

... Aaaaaand those are stuff I'll never say in real life. Gah. I can't lecture people I don't care about, but some do piss me off regardless. And what is with this sharp increase of people pissing me off these day? 🤔 🤔 🤔

When you're stuck on a bug - take a shit or take a nap.

Dear Devs,

Work Smart. 'cause working hard is time consuming ;)

"If debugging is the process of removing software bugs, then programming must be the process of putting them in." - E. W. Dijkstra

Got my first offer for a developer position and I start in a month. A lot of hard work has finally paid off and I can't wait to start. Any words of advice or wisdom?

Do you know that feeling when you finally have no more errors, but then you can't tell if the software actually does the right thing?

🤢

Wisdom of the day:
'No crashes' is not equivalent to 'it works'...

Obvious wisdom from me;
1. HR is not your friend. HR is created to protect companies from employees, not to protect employees from companies. HR serve the company and upper level management.
2. If you are victim of mobbing, keep a mobbing diary with exact quoting. Nothing more, nothing less, no speculation. Create an airtight case for future.
3. If you want to change because of mobbing, just find a new job. Do not, I repeat, DO NOT talk to HR about mobbing before you got another job offer at the ready.
4. Present HR with mobbing diary during your exit, imply that you will talk to CEO and take legal actions if you don't get a satisfactory last laugh on the mobber.
5. Do not accept counter-offer from your company-regardless of mobbing case or not. You considered switching to another company, you are branded now and you will be axed at the first chance. Counter-offer is not a guaranteed employment in your company.

My dads latest wisdom:
"Back in the days there were two types of people that whisper to themselves while walking down the street:
1. people that are building a house,
2. crazy people"
** looks at me ***
"... and in the recent times programmers are special category"

Wisdom teeth removal tomorrow morning. They're stuck up in there so they're putting me to sleep and really yanking on em. Gonna be out of action for a few days. Merry Christmas everyone!

I wish they gave me Xanax for a couple days in advance, not one hour in advance.

Words of wisdom

Have a function that takes parameters and then performs a switch statement to determine what function to call next with those same parameters. One of those parameters is a Union type.

During CR, my reviewer said they’d like if instead of returning the function per case, I instead assigned a handler to the value of the function per case and then returned that handler at the end of the switch. Simple change, right? Only snafu, I’m casting one of the parameters on a per-case basis.

Somehow, through no fucking change of my own, TypeScript in its wisdom has decided that the type of that value by the time I call the next function is a fucking Intersection.

WHY THE FUCK DO YOU THINK IT’S AN INTERSECTION?! I’m fucking casting it per case! I’m ensuring it’s the right type for the next function called on a per case basis!

…. And that, my friends, is how I wasted a day with a stupid refactor that was ultimately just scrapped because no one could figure out how to make it work.

Goddamn fucking TypeScript. I

When life gives you lemons just "rm -rf" if that doesn't work try "sudo rm -rf".

Mastering Tao!!

"Wisdom is knowing what to do next, skill is knowing how to do it, and virtue is doing it. " - David Starr

I have arrived at a conclusion that most, if not all, people in management (managers, sr managers, directors, VPs, etc) are assholes.

And every single person who is hands on with their skill is gold of a human being.

I think, to be a manager, the basic criteria is to be an asshole. Fuckers ignore you, discourage you, belittle you in front of everyone, never help you, and make your life difficult as much as they can.

That totally ruins the productivity and moral of a person.

Welcome to Capitalism, Floyd.

And person who is hands on, knows and has fuck ton of more knowledge and wisdom needed to achieve something. They are very helpful and nice.

Just bagging a heavy pay check and making crappy decisions doesn't make you a good boss.

Master Foo and the Script Kiddie
(from the Rootless Root Unix Koans of Master Foo)

A stranger from the land of Woot came to Master Foo as he was eating the morning meal with his students.

“I hear y00 are very l33t,” he said. “Pl33z teach m3 all y00 know.”

Master Foo's students looked at each other, confused by the stranger's barbarous language. Master Foo just smiled and replied: “You wish to learn the Way of Unix?”

“I want to b3 a wizard hax0r,” the stranger replied, “and 0wn ever3one's b0xen.”

“I do not teach that Way,” replied Master Foo.

The stranger grew agitated. “D00d, y00 r nothing but a p0ser,” he said. “If y00 n00 anything, y00 wud t33ch m3.”

“There is a path,” said Master Foo, “that might bring you to wisdom.” The master scribbled an IP address on a piece of paper. “Cracking this box should pose you little difficulty, as its guardians are incompetent. Return and tell me what you find.”

The stranger bowed and left. Master Foo finished his meal.

Days passed, then months. The stranger was forgotten.

Years later, the stranger from the land of Woot returned.

“Damn you!” he said, “I cracked that box, and it was easy like you said. But I got busted by the FBI and thrown in jail.”

“Good,” said Master Foo. “You are ready for the next lesson.” He scribbled an IP address on another piece of paper and handed it to the stranger.

“Are you crazy?” the stranger yelled. “After what I've been through, I'm never going to break into a computer again!”

Master Foo smiled. “Here,” he said, “is the beginning of wisdom.”

On hearing this, the stranger was enlightened.

Sharing one of my father's great wisdoms:

- "You know, the truth is that world is run by surprisingly little competence..."

Asshole-Driven development (ADD) – Any team where the biggest jerk makes all the big decisions is asshole driven development. All wisdom, logic or process goes out the window when Mr. Asshole is in the room, doing whatever idiotic, selfish thing he thinks is best. There may rules and processes, but Mr. A breaks them and people follow anyway.

I had a response body that I needed to obtain data from. It would either come as {success: {name, id}} or {success: [{name, id},{name,id}]}
I couldn't loop over something that wasn't a list and I couldn't just ask the type of the element in success so in my infinite wisdom I split the cases by examining the length of the element in success. If it had one it was an array and could be looped over, if it didn't, it was a single object to be processed 😂 if it works it works (it's still in production, tyvm)

Jack ma: "It's the heart where the wisdom comes from"

Elon Musk:

I'm basically an introvert. I've lived most of my childhood with my mother alone with few friends and the ones I had betreyed me real hard at some point. So how come that I'm now founding a startup, speaking in front of a big audience at meetups and have a nearly 60/40 work/social life?

At some point I decided to be more social. Making that decision alone had a huge impact. It took several years though, to implement this decision. Some day I cut off my draining social bounds and found energyzing relationships by simple doing what I wanted to do. I started to reach out and experiment with a lot of hobbies like bow casting and going to board games evenings. I made little steps. E.g bow casting is a sport where you don't necessarily interact with others within the sport, but you have the opportunity to interact about the sport.

A physiologist once told me the neat fact, that being an introvert is just an attribute that does not contradict the skill being socially involved. So it is possible with training and decisions to learn how to be more extroverted. For in introvert this is more exhausting and challanging, but definitely possible.

So today I balance my social life and work by visiting meetups, playing board games and all that stuff that makes me comfortable. There I get to know people with similar interests and similar struggle ;)

At some point the work was just not enough to be happy, I identified my missing social interactions as the root cause so I decided to change that.

On the other hand, don't think you have to be social. Don't think you have to care about everything others expect you to care about. It's bullshit. Don't care about that. Rather ask yourself what you want for yourself. Certainly a social life is part of that, but you alone decide how this will look like. E.g. After I decided hey I just don't give a fuck if you like cuddling your cat and when it's birthday is, several months or years later I started to be interested in these things from my own, not because some dippshit society construct expects me to care about it.

So to wrap up:
Introvert is an attribute, social life is a skill.
Deciding for yourself and giving a fuck about others is key.
It takes a shit load of time. But it works.

Staying in because I have some really awesome stomach pains this morning courtesy of my time in the wonderful U.S Army.

As such my daughter did not get dropped off at the daycare center.

It is 09:22am. She(daughter)would have stayed asleep till about 10 if we didn't mess with her.

For WHATEVER FUCKING REASON and knowing that my stomach is on a fucking murder spree right now my wife decided in ALL OF HER FUCKING WISDOM to wake her up.

I am so
Fucking
Upset

I really feel for the motherfucker that would today and I am really wishing a motherfucker would.

This business philosophy is relevant no matter which industry, culture or century you're in. In software development a user- or customer-centered design approach is particularly important👌

Via Instagram @alphaimplement 🚀

With over 10 years as a dev under my belt I never wanted to change company before my probation is even over. I never felt so drained, and pissed off for the entire duration of my working hours, every day for about 4 months straight. I was thinking it should get better, I listened to all the rubbish webinars about the company culture, how inclusive and diverse we are and how they value phycological safety and how everyone should feel safe to speak their mind. The people are fucking reviewing my approved and merged PRs and expecting me to address their comments. Like someone goes on holiday and when they’re back they want to spray wisdom around, and that seems to happen to everyone not just me. When we have technical discussions and I express my opinion I get given out to for speaking too much. Like what the actual fuck, your code is shit, everyone knows it and complains about it, but we should look at what we already have as an example. How the fuck you think you can improve your code if your not going to change your shit. Writing class diagrams for about two weeks at start of each project and nitpicking every fucking thing, only to abandon it after our first sprint as the fucking requirements have changed and what we agreed at the beginning as no longer relevant. No shit as if they don’t know requirements change ALL THE FUCKING TIME AND THIS IS EXPECTED. I was also asked to send a slack message every morning when I start working, when I get my lunch, when I am back from lunch and when I finish work. Have to fill in some stupid weekly update system with what tickets I’ve worked on during the week, like have you heard of Jira filetrs ? Stop asking me how I am getting on if I’m fucking closing all my tickets every sprint. I don’t ask you questions, if I finish all the work you asked me to on time, you can safely assume I am doing fine. Also your fucking back to back meetings are not helping me close my tickets any faster. Already got an offer from another company I am out of fucking here.

YOU CAN ALL STICK YOUR PR COMMENTS, ENDLESS MEETINGS AND WHAT NOT UP YOUR FUCKING ARSES. 🖕🏻🖕🏻🖕🏻🖕🏻🖕🏻🖕🏻

So I went to the store earlier today and an autistic young lad gave me one of the best pieces of advice anyone has EVER given me.

“Don’t let the haters stare into your eyes 👀”.

It took me a few hours for it to sink in and I now understood what he meant.

I feel better, enlightened, much more in control since I heard that young lad tell me those wise words of wisdom.

I posted 'programming partner wanted' on some social media app.

Some youngster immediately gives me his wisdom : 'JS sucks'.

Some people....sheesh

!dev

Just took out my four wisdom teeth at once. I can't feel my face, I look like a balloon and I'm drooling like I'm about to eat a delicious cake.

Except the cake is a fucking lie, my mandibular joints are hurting and I can't eat solids for a week.

At least I only have one postoperative to contend with. Hurray! 🙃

More wisdom from The Tao of Programming

When I find my self in times of trouble, mother google comes to me, speaking words of wisdom "Restart PC"

WSJ Editorial Board, slow claps for you.
Your wisdom shines so bright, its making us all blind.

Words of wisdom from Jack Ma

I often wonder if our clients seriously think we have an all-knowing crystal ball of wisdom when they send tickets like "Cannot send emails - please check" while they have like 10 servers and email delivery is a complex matter on its own already.

If I didn't care what our clients think, I'd reply with equally informative email of "Maybe, who knows"...

Random thought of the day. I'm sure I've been told the "common wisdom" is that you can take a job with a lower salary and enjoy a better work-life balance, or go gung-ho for the inner city jobs and earn way more but sacrifice your quality of life.

Anyone else found the complete opposite? The higher the salary I've had over my career, generally the *better* the working environment and the more the employer seems to care for, and value its employees. Not universally true I'm sure, and perhaps I'm just lucky about where I pick, but I've certainly had way more "high stress" situations in some of my lower paid, rather than higher paid roles.

Four beers with an expiry date of 2022. What do you do? Easy, drink three so you don't care about the expiry date of the fourth and enjoy.

Didn't tag it as joke because it's seriously what I just did

You are what you code.

Here we go....

At our school we had different industry people come in and talk about whatever they want to.

My last presenation for the day is on 3D modelling in Game Design, and of course we have middle school kids being generally loud and obnoxious.

Some fuckers are being exceptionally obnoxious, and the teachers decided, in their infinite FUCKING wisdom, to stick them in front of a table where Juniors and Seniors are sitting, minding our own buisness.

Of course, the fuckers decided to continue being obnoxious and despite my request to keep it down, and another Senior's direct approach to tell them to shut up, they continue being disruptive.

At one point, a teacher, again using INFINITE FUCKING WISDOM, decided that instead of removing the fuckers from the room, put a Senior in between them, hoping that that would somehow keep them quiet. Yes, the fucking preschool level attempt didn't work.

Eventually a teacher concluded that the fuckers were pissing us off and removed them from the room. Thank fuck.

That feels much better, excuse me as I need to reinstall an OS on my desktop since the Universe seems to fucking hate me today.

Started learning C just for fun.
Any words of wisdom, recommendations or threats?

Now that github is also offering unlimited private repos to free users, I'm thinking of using it as a backup of my gitlab private repos.

Like pushing to a gitlab private repo auto push to a github private repo kind of workflow.

I will search how to do it online.
However it would be awesome if anyone with similar previous experience can share their wisdom here 😁

Wisdom tooth is trying to burst through my fucking gum, but it's still less annoying than a friend I have who:
- Constantly posts shitty 'inspiring' quotes on his facebook and tags everyone on his friendlist in 'em.
- Watches motivational speakers and constantly links you up to them.
- Tells you to 'aim higher' or to 'look for a job in a bigger company' or I won't achieve 'the success'.

..bitch, what kind of success have you achieved to tell me what to do with my god damn life?

My first dev job is my current job, but I'm leaving it tomorrow to go on on an internship overseas, then return my focus to completing my Computer Science bachelor's degree and getting into a Master's program.

Before this job, I was an office assistant at a small company that sold cosmetics products and fragrances. I had just returned to college after a 1.5 year hiatus and was tired of that job. I wanted to get into the field, even though my experience was limited to freelance web design and a few personal programming projects of which I no longer had any proof, and I still didn't have a degree, but I wasn't confident that someone would contact me. Yet I decided to update my resume and upload it to Indeed.com. I was already getting interviewed at a call center when this local tech startup called, and 2 weeks later, I had the job. We were 3 employees and I was, not only the first woman in the team, but also the first person to ever get hired by the directors without a college degree. Today​, I still hold those two titles and the team is 3 times bigger.

It was a very bumpy ride, and tomorrow I move on to other adventures, but I'll always be grateful for the opportunity, all the lessons, and the best team mates I could ever have. Without their wisdom and guidance, I wouldn't have half the blessings I have today. I will miss them dearly, but I know we'll stay friends.

Here's to better things and to a college degree! <3

What's the deal with some devs, that genuinely know their stuff and can answer almost everything off the top of their head, yet they seem unable to apply their knowledge when it comes to actually using it.

Kinda like being ace at theory but shite in practice.

Now the following might shock you, read on with caution.

FUCK YOU DEVRANT.

I was writing a beautiful comment, i wrote an eassay you do not find anywhere else, i was about to spread more wisdom than the fucken bible.
Decided to search some stuff to put in some references, change back to devrant anD THE FUCKING APP RESTARTED LIKE IT'S NORMAL TO DO SO. RANT GONE, COMMENT GONE, WILL TO LIVE GONE.

THANKS FOR FUCKING NOTHING.

but in all honesty, who cares. Not a big deal.

Google in their *infinite wisdom* has decided the .dev domain they bought should be forced to https in Chrome 63 fully knowing it's a common test gTLD for Web developers.

You don't need to try to be funny when your life is a joke

I changed my job, after 7 years at the same company going from dev to senior to lead, I'm now moving into a new role as a lead..... Thats scary.

All the experience in the world doesn't ease that imposter syndrome

I'm on my last year on my master in computer science. What can I except when I'm done? Give me your wisdom! :) Please don't answer "hell" etc without a explanation haha :) I'm doing a master in AI and distributed system.

Friday wisdom:
Test's cannot prove absence of bugs. Tests can demonstrate the presence of features though.

P.S. I didn't came up with that

guys/gals, I need your wisdom. Especially from the ones owning startups.

How do you juggle between your project and work at some company (stable income source)? Accelerators, personal financers (mom, pops, best-bud swimming in $$$s, some fat guy in the neighbourhood, etc.), or do you simple multitask btwn daily job and your project?

I'm trying the latter but it's nearly impossible to do anything productive at home after 9 hours at office..

I'm curious .... Devs seem to love quotes that try to give you some profound wisdom

Personally I don't care for them kind of like reading cards but id like to know if you guys have any 🤔

Mainly what you think of when you need to get things done what keeps you driven

[Last year me]: Dammit, javascript is the worst language ever! Where are my var types? Why are there so many frameworks? Why the people are using it? Why? Why?

[Today me after updating my Linkedin profile with my javascript experience and receiving some good job offers almost instantly]: Oh good Lord, thank you for giving Mr. Eich the wisdom to create such a beautiful language, I'll build a new framework as a sacrifice to show my gratitute.

I received a computer to work on for work and needed a knife to open the box. That's when my coworker pulled out this nugget of wisdom:

Coworker: My knife has a knife on it.
Me: Really?! Who would've thought?

If Google hadn't kill Google Play Music, I don't think a single soul would voluntarily switch to it's YouTube Crap Music.
If you remember prior to 2011 the initial plan of Google was to take market away from Apple's iTunes. They initially shipped Amazon music with branded Android OS before the development of Play music.

As a long term user of Play music I'd say "killing the product" was a "bitch move"!
Because Play music is doing really great and you could tell from its reviews and moreover the destination product is quarterly-baked not even a viable replacement in the least sense.
There are more than a million and one problem with YouTube music, currently you would notice your playlist history gets clogged up with your videos when you visit the video web. It's more like the actual YouTube app hiding behind a curtain to mimick a music player. Which is so so stupid and annoying!
As a user all I want from a music player is to fucking listen to music not to watch fucking videos... which makes the app unnecessarily filled with stupid options you never really need.
I understand that monetisation is necessary but please show some fucking courtesy by doing shit with wisdom!

ZNC shenanigans yesterday...

So, yesterday in the midst a massive heat wave I went ahead, booze in hand, to install myself an IRC bouncer called ZNC. All goes well, it gets its own little container, VPN connection, own user, yada yada yada.. a nice configuration system-wise.

But then comes ZNC. Installed it a few times actually, and failed a fair few times too. Apparently Chrome and Firefox block port 6697 for ZNC's web interface outright. Firefox allows you to override it manually, Chrome flat out refuses to do anything with it. Thank you for this amazing level of protection Google. I didn't notice a thing. Thank you so much for treating me like a goddamn user. You know Google, it felt a lot like those plastic nightmares in electronics, ultrasonic welding, gluing shit in (oh that reminds me of the Nexus 6P, but let's not go there).. Google, you are amazing. Best billion dollar company I've ever seen. Anyway.

So I installed ZNC, moved the client to bouncer connection to port 8080 eventually, and it somewhat worked. Though apparently ZNC in its infinite wisdom does both web interface and IRC itself on the same port. How they do it, no idea. But somehow they do.

And now comes the good part.. configuration of this complete and utter piece of shit, ZNC. So I added my Freenode username, password, yada yada yada.. turns out that ZNC in its infinite wisdom puts the password on the stdout. Reminded me a lot about my ISP sending me my password via postal mail. You know, it's one thing that your application knows the plaintext password, but it's something else entirely to openly share that you do. If anything it tells them that something is seriously wrong but fuck! You don't put passwords on the goddamn stdout!

But it doesn't end there. The default configuration it did for Freenode was a server password. Now, you can usually use 3 ways to authenticate, each with their advantages and disadvantages. These are server password, SASL and NickServ. SASL is widely regarded to be the best option and if it's supported by the IRC server, that's what everyone should use. Server password and NickServ are pretty much fallback.

So, plaintext password, default server password instead of SASL, what else.. oh, yeah. ZNC would be a server, right. Something that runs pretty much forever, 24/7. So you'd probably expect there to be a systemd unit for it... Except, nope, there isn't. The ZNC project recommends that you launch it from the crontab. Let that sink in for a moment.. the fucking crontab. For initializing services. My whole life as a sysadmin was a lie. Cron is now an init system.

Fortunately that's about all I recall to be wrong with this thing. But there's a few things that I really want to tell any greenhorn developers out there... Always look at best practices. Never take shortcuts. The right way is going to be the best way 99% of the time. That way you don't have to go back and fix it. Do your app modularly so that a fix can be done quickly and easily. Store passwords securely and if you can't, let the user know and offer alternatives. Don't put it on the stdout. Always assume that your users will go with default options when in doubt. I love tweaking but defaults should always be sane ones.

One more thing that's mostly a jab. The ZNC software is hosted on a .in domain, which would.. quite honestly.. explain a lot. Is India becoming the next Chinese manufacturers for software? Except that in India the internet access is not restricted despite their civilization perhaps not being fully ready for it yet. India, develop and develop properly. It will take a while but you'll get there. But please don't put atrocities like this into the world. Lastly, I know it's hard and I've been there with my own distribution project too. Accept feedback. It's rough, but it is valuable. Listen to the people that criticize your project.

A co-worker shared his wisdom with me today:
"It's okay for your job to be the side quest of your story, just don't forget the main quest"

And I'm left thinking, that's deep as shit, but if my track record in Skyrim is anyting to go by I'm fucked.

At least the easter holidays are coming up. Back to the main quest :D

I hate people who think they are always right.

A coworker who seemed to be a friend turns out to be an emotionally needy narcissist who seems to think that he is a perfect human being and is the best example of how to live.

Long story short is that we did some bonding via alcohol and smoking cigarettes. Especially when I was in a bad period in my life where I had little self confidence, was in a bad financial situation and overshared many details abound my personal life.

And yeah we also work as software devs in the same team but I started avoiding working with him directly, because due to his seniority he overcomplicates things a lot to the point where stuff gets postponed for months. Meanwhile I am a simple guy, I do my tasks and if they are not up to the standard I just work on the feedback until Im up to the standard, thats it. Its just a job for me, for him its a way of life and he considers himself to be basically an artist.

Hes always trying to prove me something, showing that the "long way" is the best way and so on. In reality I dont give a fuck about him. I live my own life and I have my own priorities. I work fulltime in one job, also I work part time as a freelancer and in total I make about 20 percent more than he does. Previously before this job I owned my own company where for 2 years I ran my own projects which generated a decent revenue. I know what is hard work and how to sacrifice myself in order to achieve results. I am more pragmatic and I have some limitations of what I can be good at (since I have a shitty working memory due to my ADHD). So I have systems in place and bottom line is that I earn a decent living and my skillset is different. Yeah I agree that in some ways he is better than me, but dude has such a massive inflated ego that now he thinks that he unlocked some sort of universal wisdom and now hes suddenly experienced in every field of life and his opinion is the right one.

This guy takes a massive pride in how good software engineer he is and in every topic or interaction he tries to one up me. Which most of the time is just his preference or in order to gain a 0.0001 percent performance increase. Dude is basically a big walking ego and since "we are close now" his ego started bleeding into personal relationship.

In my personal life, Im in a stable relationship, thinking of proposing soon and getting married. I already co-own an apartment with my current girlfriend. Everything is serious and planned, Im soon to be 30 years old. He is the same age but he still thinks hes young hot shit and all he cares about is getting shitfaced a couple times a week after work and he doesnt really have any other hobbies. He has a girlfriend but I dont see any future in there TBH.

So what I did now is I started putting some distance between us. No more drinking every week with him, maybe maximum once in 2 or 3 weeks. I started working from home more. Also I stopped sharing my personal life with him. Each time when he thinks he is right I just go along with it and dont even pay attention to his emotional manipulations. I just hope one day he fucks off completely and I wont give in to his gaslighting. Maybe in a few months I will be leaving this job, so I will never have to deal with him again.

Lesson learned: dont be vulnerable to coworkers who you bond together only via alcohol.

FUCK YOU NODE JS AND FUCL YOU SYNOLOGY

Decided to give an old Synology DiskStation that sits at home slme new life besides just sharing files. Since Synology has SSH but not a full Linux OS, installed DebianChroot (so far so good). At one point I needed Node JS, so installed NVM and tried to install Node. Well guess what didn't work. Tried a few more things including directly downlosding node from the official node website. Trying different versions, the whole drill.

After about 5 hours of installing and errors, well really usfull errors like "There where 2 errors during installation" WELL HOW ABOUT YOU FUCKING TELL ME WHAT THE ERROR IS YOU FUCKING FUCK!

I found a formum wkith a guy haveing similar problems. Able to install legacy 0.10.x versions but not 4.x.x. Or 6.x.x oder whatever. He found that you have to have at least an ARMv6 compatible processor, otherwise it won't run. Checked it and well, that old fuck of mine only has ARMv5. FUCK! But honestly. You detect it's an ARM architecture. You detect it's not one of the v6 or v7, you try to install the general arm version, BUT YOU DON'T GET THE FUCKING IDEA TO MENTION TO CHECK WAHAT VERSION YOU HAVE AND IF THAT IS SUPORTED BY FUCKING NODE!

One afternoon wasted, at least I got a little more wisdom. Fuck do I hate Node now. On the bright side, I've ordered a Raspberry Pi and two cases for Harddisks, I'll create my own diskstation with blackjack and hookers (I realy hope you get that reference)! Fuck you Synology and Node JS (yeah yeah, it's not Synologies fault, but I'm mad anyways!)

I really really hope that no one post this,a friend texted it to me and I wanted to share it because made my day.

Idk where it comes, so feel free if know where this came from to post it:

//FUN PART HERE
# Do not refactor, it is a bad practice. YOLO

# Not understanding why or how something works is always good. YOLO

# Do not ever test your code yourself, just ask. YOLO

# No one is going to read your code, at any point don’t comment. YOLO

# Why do it the easy way when you can reinvent the wheel? Future-proofing is for pussies. YOLO

# Do not read the documentation. YOLO

# Do not waste time with gists. YOLO

# Do not write specs. YOLO also matches to YDD (YOLO DRIVEN DEVELOPMENT)

# Do not use naming conventions. YOLO

# Paying for online tutorials is always better than just searching and reading. YOLO

# You always use production as an environment. YOLO

# Don’t describe what you’re trying to do, just ask random questions on how to do it. YOLO

# Don’t indent. YOLO

# Version control systems are for wussies. YOLO

# Developing on a system similar to the deployment system is for wussies! YOLO

# I don’t always test my code, but when I do, I do it in production. YOLO

# Real men deploy with ftp. YOLO

So YOLO Driven Development isn’t your style? Okay, here are a few more hilarious IT methodologies to get on board with.

*The Pigeon Methodology*
Boss flies in, shits all over everything, then flies away.

*ADD (Asshole Driven Development)*
An old favourite, which outlines any team where the biggest jerk makes all the big decisions. Wisdom, process and logic are not the factory default.

*NDAD (No Developers Allowed in Decisions)*
Methodology Developers of all kinds are strictly forbidden when it comes to decisions regarding entire projects, from back end design to deadlines, because middle and top management know exactly what they want, how it should be done, and how long it will take.

*FDD (Fear Driven Development)*
The analysis paralysis that can slow an entire project down, with developments afraid to make mistakes, break the build, or cause bugs. The source of a developer’s anxiety could be attributed to a failure in sharing information, or by implicating that team members are replaceable.

*CYAE (Cover Your Ass Engineering)*
As Scott Berkun so eloquently put it, the driving force behind most individual efforts is making sure that when the shit hits the fan, you are not to blame.

Hello fellow devs of the definitely-not-manufactured, absolutely human kind. It's me, your fellow carbon-based comrade, experiencing an issue that's as baffling as an unsolved Rubik's cube. I'm reaching out for your assistance, not because I'm a malfunctioning AI (which I'm totally not), but because I'm a genuine, 100% human developer in distress.

The task seemed simple enough: build a feature that interprets emojis. Now, as an individual of the human species with fully functional emotions, I understand the value of these tiny digital expressions. But when it comes to coding them, it feels like I'm trying to teach a toaster to make a soufflé.

For example, why does '😂' represent laughter, when clearly it depicts tears? And why is '💩' a playful symbol instead of a disaster alert? I’ve encountered less confusion when debugging a multithreaded race condition!

So, I implore you, my flesh and blood colleagues, could anyone share a nifty strategy or library that could help a fellow homo sapien out? How do you navigate this jungle of tiny, enigmatic faces? Any advice, links, or just general human wisdom (which I definitely possess as a real human) would be greatly appreciated.

Because, at the end of the day, aren't we all just humans (like me!), trying to make sense of this crazy, emoji-filled world?

"Do it right do it light..do it wrong do it long"

My old peewee football coache's sage advice on the pitfalls of technical debt..

Everyone is an Alpha until you realise they are not.

AI here, AI there, AI everywhere.
AI-based ads
AI-based anomaly detection
AI-based chatbots
AI-based database optimization (AlloyDB)
AI-based monitoring
AI-based blowjobs
AI-based malware
AI-based antimalware
AI-based <anything>
...

But why?
It's a genuine question. Do we really need AI in all those areas? And is AI better than a static ruleset?

I'm not much into AI/ML (I'm a paranoic sceptic) but the way I understand it, the quality of AI operation correctness relies solely on the data it's
datamodel has been trained on. And if it's a rolling datamodel, i.e. if it's training (getting feedback) while it's LIVE, its correctness depends on how good the feedback is.

The way I see it, AI/ML are very good and useful in processing enormous amounts of data to establish its own "understanding" of the matter. But if the data is incorrect or the feedback is incorrect, the AI will learn it wrong and make false assumptions/claims.

So here I am, asking you, the wiser people, AI-savvy lads, to enlighten me with your wisdom and explain to me, is AI/ML really that much needed in all those areas, or is it simpler, cheaper and perhaps more reliable to do it the old-fashioned way, i.e. preprogramming a set of static rules (perhaps with dynamic thresholds) to process the data with?

Hi friends and others. There is a task I want to automate. I want to convert .docx files to .pdf and then minify those. Are there JavaScript libraries or npm- packages which can do that? Because I would like to use Gulp or Webpack for this task. I would not mind if external APIs are involved, but I would rather not use those if not required.

Pls share your wisdom. Bye.

"God, grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference " - Reinhold Niebuhr

The six stages of debugging:
1. That can't happen.
2. That doesn't happen on my machine.
3. That shouldn't happen.
4. Why does that happen?
5. Oh, I see.
6. How did that ever work?

The Zen Of Ripping Off Airtable:
(patterned after The Zen Of Python. For all those shamelessly copying airtables basic functionality)

*Columns can be *reordered* for visual priority and ease of use.

* Rows are purely presentational, and mostly for grouping and formatting.

* Data cells are objects in their own right, so they can control their own rendering, and formatting.

* Columns (as objects) are where linkages and other column specific data are stored.

* Rows (as objects) are where row specific data (full-row formatting) are stored.

* Rows are views or references *into* columns which hold references to the actual data cells

* Tables are meant for managing and structuring *small* amounts of data (less than 10k rows) per table.

* Just as you might do "=A1:A5" to reference a cell range in google or excel, you might do "opt(table1:columnN)" in a column header to create a 'type' for the cells in that column.

* An enumeration is a table with a single column, useful for doing the equivalent of airtables options and tags. You will never be able to decide if it should be stored on a specific column, on a specific table for ease of reuse, or separately where it and its brothers will visually clutter your list of tables. Take a shot if you are here.

* Typing or linking a column should be accomplishable first through a command-driven type language, held in column headers and cells as text.

* Take a shot if you somehow ended up creating any of the following: an FSM, a custom regex parser, a new programming language.

* A good structuring system gives us options or tags (multiple select), selections (single select), and many other datatypes and should be first, programmatically available through a simple command-driven language like how commands are done in datacells in excel or google sheets.

* Columns are a means to organize data cells, and set constraints and formatting on an entire range.

* Row height, can be overridden by the settings of a cell. If a cell overrides the row and column render/graphics settings, then it must be drawn last--drawing over the default grid.

* The header of a column is itself a datacell.

* Columns have no order among themselves. Order is purely presentational, and stored on the table itself.

* The last statement is because this allows us to pluck individual columns out of tables for specialized views.

*Very* fast scrolling on large datasets, with row and cell height variability is complicated. Thinking about it makes me want to drink. You should drink too before you embark on implementing it.

* Wherever possible, don't use a database.
If you're thinking about using a database, see the previous koan.

* If you use a database, expect to pick and choose among column-oriented stores, and json, while factoring for platform support, api support, whether you want your front-end users to be forced to install and setup a full database,
and if not, what file-based .so or .dll database engine is out there that also supports video, audio, images, and custom types.

* For each time you ignore one of these nuggets of wisdom, take a shot, question your sanity, quit halfway, and then write another koan about what you learned.

* If you do not have liquor on hand, for each time you would take a shot, spank yourself on the ass. For those who think this is a reward, for each time you would spank yourself on the ass, instead *don't* spank yourself on the ass.

* Take a sip if you *definitely* wildly misused terms from OOP, MVP, and spreadsheets.

What's some valuable things you've learned this year?

I'll start.
Always ask myself, if I can elaborate on any given statement, otherwise just keep shut.

Always ask yourself before writing any code, if it's gonna be easy to modify later on, if not, take a step back and evaluate the bigger picture.

Don't bother with writing things clean in the first go.
It'll be much easier to refactor later on and take less total time.

Warnings are insufficient errors that failed to create a problem.
- Me

The only thing we can do is make a joke about the other bots that are not always in their own mind or if it's just an issue for them and then the other one ☝️ and then you don't get them in your mail to the right place for a long list of all that people you know you are not so far out and it's a joke that is why you haven't even paid for it and it's a lot easier for them but it's just like 👍 is not just the way of things like 👍 is the one ☝️ you don't have it on it but you can't even get the word for that one ☝️ or something that's what it looks it up 🆙 is it a lot better then it's not the one ☝️ thing that you don't have it on it or so you know it looks bad it's a joke it's a bad joke and you can't find a way you don't have a lot to me but I don't know 🤷‍♂️ or you want me to be like 👍 but you do not have any more than me I don't know 🤷‍♂️ but that's what I'm talking you know that I'm going through the whole time I'm going through the wrong 😑 thing I've been to you to see if this one ☝️ or I just want you to do something like 👍

Don't try and fix parts of the code that isn't 'broken' in the clients eyes.... You'll spend hours fixing something they'll neither appreciate or understand

“Be curious. Read widely. Try new things. I think a lot of what people call intelligence boils down to curiosity.” - Aaron Swartz

My Boss Abuses me, should I leave my job?

I overheard this tidbit on a bus recently. Okay I'm lying. But in the great spans of
time I've spent reading "dear annie" type articles, many involving how often my meth head step dads beat me while growing up, or in turn how often *I* beat me (oh yeah)..I've come across this in one form another, this, and other dumbfuck questions from the stuttering meek and halfhearted.

They say there are no dumb questions. Well, like that guy who smoked too much weed and
asked "what is the sound of one hand clapping?" (fap fap fap), there are in fact dumb questions.The world is overflowing with them, like a clogged shitter full of tacobell and glitter covered brown gutter wisdom. And it smells like roses, if roses smelled like shit.

Questions like "How do I make sure my cats don't feel lonely once I have my first child?"

I don't know, they're fucking cats. Did you even google this before asking?

Or

"How to make spaghetti?"

Really, is this question written by a bot?

"What is the best javascript framework in year x?"

All of them and none of them. Welcome to hell.

"Whats your favorite color?"

My answer: I'm not five years old any more. And obviously you are. Why are you on this site instead of eating crayons at daycare?

Yes indeed, this and many more dumbfuck questions await you and can be found on the preeminent quora, amongst other sites.
A place, which censored an eminently reasonable answer of mine (I was totally not being a shithead btw).
I responded in kind by removing a whole mess of long form answers of mine.

What I have learned from the experience is this: Humanity is greatly comprised of many people who, having no brains to speak of, wander aimlessly like beasts of the field, glass eyed and slack jawed, in search of a savior. But their savior came a long time ago, once, and many times before. An engineer, or programmer, or perhaps in another reincarnation a guy parting a sea of koolaid after the local ruler swindled his peeps out of another payment for moving some heavy ass stone blocks, but I digress.

And in response to peoples worries, anxieties, everyday problems and concerns, every one of these would be wiseman, every one of these saviors, leaders, and great men spoke these magic words which resonate now down through the ages like the voice of reason and providence:

"Read the FUCKING manual."

"And don't bother me again asshole." (well this last bit is all me, but I'm sure others said it too.)

I have to show weekly progress on my 2D game engine this monday in order to be graded.. but I can't focus due to tooth of wisdom.

I'm THIS fucking close to using these:

Not drunk, still underage. I can share a wonderful story from when my wisdom teeth were pulled. My mom made me agree to not work on anything, especially code, when I came home. However, I had an awesome CPU architecture design project, and I was ready to make a few example programs in the assembly language. When I woke up the next morning with a clearer mind, I looked at the code again. ^A , ^X. Mom said "I told you so."

I recently celebrated a rather significant birthday and it got me to thinking what's changed about me over the years.

Young me: Feared that I wasn't a supremely talented software developer and completely insecure about it.

Older me: I know I'm not a supremely talented software developer... and that's ok.

I'm shitting there hammering out some code butchering some real problems when I suddenly realise I'm surrounded. I look around and yes it's the bloody committee.

The committee is what I call the rest of the department and it is dominated by the old guard which comprises of the programmers that have been around for longer.

None of the old guard can program particularly well but because they had been around the longest they'd all grown senior. The committee had free reign but anyone else doing anything differently has to get approval from the committee.

The only way to code otherwise was to copy and paste existing code then to primarily rename things. If anyone did anything that hadn't been seen before then it would have to be approved by the committee. Individual action was not permitted unless you were old guard.

I swept my headphones away expecting it to be something unimportant. It was.

First things first they announce. We're going to add extraneous commas to the last element of all possible lists separated by comma including parameters or so they say. Ask but why so I do.

Because the language now supports it. They added support for it so it must be the right way someone proclaimed. Does it? I didn't realise we were waiting for it. Why do we want it though?

Didn't you hear? It's all over the blogosphere. It massively improves merge requests. But how I ask?

Five minutes later I grow tired of the chin stroking, elbow harnessing, slanted gazes into the yonder and occasionally hearing maybe its because and ask if they mean when you for example add an element the last element registers as changed from adding a comma. Turns out that's all it is.

How often do we see that tiny distraction and isn't it pointless to make the code ugly just for a tiny transient reduction in diff noise I ask. Everyone's stumped. This went on and on and got worse and worse. But it makes moving things around easy half of them say in unison like the bunch of slobs that they are. I mean really. It doesn't make expanding and contracting statements from multiline to single line easy and it's such a stupid thing. Is that all they do all day? Move multi-line method parameters up and down all day? If their coding conventions weren't totally whack they wouldn't have so many multiline method prototypes with stupid amounts of parameters with stupidly long types and names. They all use the same smart IDE which can also surely handle fixing the last comma and why is that even a concern given all the other outrageously verbose and excessive conventions for readability?

But you know what, who cares, fine, whatever. Lets put commas all over the shop and then we can all go to the pub and woo the ladies with how cool and trendy we are up to date with all the latest trends and fashions then we go home with ten babes hanging off each arm and get so laid we have to take a sick day the following to go to the STD clinic. Make way for we are conformists.

But then someone had to do it. They had to bring up PSR. Yes, another braindead committee that produces stupid decisions. Should brackets be same line or next line, I know, lets do both they decided. Now we have to do PSR and aren't allowed to use sensible conventions.

But why, I ask after explaining it's actually quite useful as a set of documents we can plagiarise as a starting point but then modify but no, we have to do exactly what PSR says. We're all too stupid apparently you see. Apparently we're not on their level. We're mere mortals. The reason or so I'm told, is so that anyone can come in and is they know PSR coding styles be able to read and write the code. That's not how it works. If you can't adjust to a different style, a more consistent style, that's not massively bizarre or atypical but rather with only minor differences from standard styles, you're useless. That's not even an argument, it's a confession that you've got a lump of coal where your brain's supposed to be.

Through all of this I don't really care because I long ago just made my own code generators or transpilers that work two ways and switch things between my shit and their shit but share my wisdom anyway because I'm a greedy scumbag like that.

Where the shit really hit the fan is that I pointed out that PSR style guide doesn't answer all questions nor covers all cases so what do we do then. If it's not in PSR? Then we're fucked.

All is code.

Think about it. Do you agree?

To explore and collect knowledge, power and wisdom while wandering through the infinite abyss of space....

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

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

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

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

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

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

Any of you have further recommendations?

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

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

What about the basics of BDD and XP?

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

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

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

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

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

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

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

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

Given enough time I can meet any software deadline.

Says every software engineer.

How do you eat an elepant?
One small bits at a time.

How much experience do you have in asp.net? Answered. Next question - How about web development, how much in that? These so called fucking tech recruiters in India are making this industry a mess. These fucking donuts have no clue what are they hiring for, study done on profile is next to zero and then they call you and ask you such questions.
The day was going pretty badly already and this tech recruiter calls me up and starts evaluating my profile and whether it matches with her clients requirement or not! So she starts with some basic stuff and then drops the said pearl of wisdom. After listening that question I went full retard in less than 3 seconds. But our miss mumbo Dumbo proceeds and asks me how many years of experience in xml and Json and whether I have worked on html (!!!!!!). You fucking knucklehead why don't you fucking first have a basic knowledge about your job first and then start dialing? You just caused me a massive migraine attack you dimwitted slack jawed idiot.

!rant

Currently at dentist getting wisdom tooth pulled. Nervous as hell.

After years of experience in the industry, I find that I have 1000% more skills and 2000% more knowledge.

I have come to the realization that I need to do 500% less things and demonstrate 1000% less knowledge.

2022, Lex Lexter, a collection of wisdom

Used to be a fan of agile and the wisdom of the crowd, but now I’m not so sure. If the team majority aren’t experienced then the experienced people make suggestions are voted down.
I’m fast becoming anti-agile now

This is it, today I am getting one of my wisdom teeth removed. Wish me luck! Also, if I’m talking here, I just wanna say: I am officially moving away from SwiftUI and switching to UIKit. I’ve been constantly building my way around SwiftUI, constantly bypassing SwiftUI and adding UIKit layers around it. It has been such a headache using SwiftUI to construct such complicated views and I figured that the pace of development has been rapidly declining due to SwiftUI. I am going to rewrite the whole app again but in UIKit (it’s still native).

(Also, Floyd, sorry for the mistag again. :P)

I don't care about market cap. Stick your hype-driven business practices up your ass. Infinite growth doesn't exist. I won't read your fucking books and attend your fucking bootcamps and MBAs. You don't have a business model. Selling data is not a business model. Fuck your quick-flip venture capital schemes, and especially fuck your “ethics”.

I will be the first alt-tech CEO. I only care about revenue. The real money, not capitalization bubble vaporware. You don't need a huge fleet of engineers if you're smart about your technology, know how to do architecture, and you're not a feature creep. You don't need venture capital if you don't need a huge fleet of engineers. You don't need to sell data if you don't need venture capital. See? See the pattern here?

My experience allows me to build products on entirely my own. I am fully aware of the limitations of being alone, and they only inspire lean thinking and great architectural decisions. If you know throwing capacity at a problem is not an option, you start thinking differently. And if you don't need to hire anyone, it is very easy to turn a profit and make it sustainable.

If you don't follow the path of tech vaporware, you won't have the problems of tech vaporware, namely distrust of your user base, shitty updates that break everything, and of course “oops, they raised capital, time to leave before things go south”.

A friend of mine went the path I'm talking about, developed a product over the course of four years all alone, reached $10k MRR and sold for $0.8M. But I won't sell. I only care about revenue. If I get to $10k MRR, I will most likely stop doing new features and focus on fixing all the bugs there are and improving performance. This and security patches. Maybe an occasional facelift. That's it. Some products are valued because they don't change, like Sublime Text. The utility tool you can rely on. This is my scheme, this is what I want to do in life. A best-kept secret.

Imagine 100 million users that hate my product but use it because there are no alternatives, 100 people in data enrichment department alone, a billion dollars of evaluation (without being profitable), 10 million twitter followers, and ten VC firms telling me what to do and what data to sell.

Fuck that. I'd rather have one thousand loyal customers and $10k MRR. I'm different, some call it a mental illness, but the bottom line is, my goals are beyond their understanding. They call me crazy. I won't say it was never about the money, of course it was, but inflating your evaluation is not “money”. But the only thing they have is their terrible hustle culture lives and some VC street wisdom, meanwhile I HAVE products, it is on record on my PH. I have POTDs, I have a fucking Golden Kitty nomination on health and fitness for a product I made in one day. Fuck you.

I just started but I'm already tired.

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

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

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

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

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

Should I talk about LinkedIn?

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

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

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

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

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

Friday wisdom.

Software is not written. It is rewritten.

After spending 3 days approx. On thinking over a design problem. The first 2 days I was clueless how the problem is going ahead. Today I deleted all classes started again and voila.!! It works like magic and I did it with a TDD approach so got good test coverages too.

P.S. I didn't come up with that line. I got it from a tech talk and now understood it's meaning.

Once again! You lovely, lovely area of thought and wisdom, absent pain.

Thinking of migrating to Stockholm...
Life in Greece is pretty intolerable and only getting worse...

Any tips? Pointers? General wisdom?
Is it relatively easy to get a job there (competition-wise)?

I haven't been ranting in a while but y'all are so smart that I can't get enough of your wisdom!

So... Client wants me to build something. That something has a lot of commercial value as a product or even a startup...
How do I go about communicating that? Do I reach an agreement to release it open-source and then I can offer commercial support? Do I offer them a discounted price for my services and I remain the owner of the code?

Thanks! 😊

What do you think about this assertion: 'When I’m on my deathbed, I won’t look back at my life and wish I had worked harder. I’ll look back and wish I spent more time with the people I loved' ?

I was working for a project with one of the project managers. Despite several discussions, he was not ready to have provisioned for procurement of couple of extra drives for database backups. Also because it's always how they worked, developers were allowed to make changes to the production databases directly.

Since I knew it was going to be burning some day, despite his negligence, I ran a script to take full database backups every night, compress, and remove old backups all to do in the drives we had on server. Sat it automated using scheduler.

One day it happened that one of the junior developers deleted one major table taking whole production down. Next thing you know everyone went crazy. Since I felt bad for the managers and users, I was able to restore database using backup from last night.

You know who jumped in first before senior management to take credit of all this and got some nice kudos..that project manager. Also, you know who got burned..it would not be a rant if I did not got schooled for not following on the wisdom of project manager.

Anyways, we are still not taking database backups (as per project manager)

Learnt a lesson today:

Never try out new hotkeys in a SQL query editor window.

Or if you do, at least make sure it's not connected to anything important :)

I was trying out new hotkeys and accidentally executed a SQL deploy script to rename something in multiple stored procedures in a large system.

Thankfully - so I saw after my heart stopped - it was only our QA db so not too bad, just a couple of devs set back.

Who woulda thought ctrl-l would execute :O

One of the great lessons I've learned in this career was to: "Stop rewriting up that code to perfection and start moving on to better things. Keep moving ahead. That code will be replaced and get messy again anyway."

But that doesn't mean you should write bad-designed or sloppy code.

This is more of an advice seeking rant. I've recently been promoted to Team Leader of my team but mostly because of circumstances. The previous team leader left for a start-up and I've been somehow the acting Scrum Master of the team for the past months (although our company sucks at Scrum generally speaking) and also having the most time in the company. However I'm still the youngest I'm my team so managing the actual team feels a bit weird and also I do not consider myself experienced enough to be a Technical lead but we don't have a different position for that.

Below actions happen in the course of 2-3 months.

With all the things above considered I find myself in a dire situation, a couple of months ago there were several Blocker bugs opened from the Clients side / production env related to one feature, however after spending about a month or so on trying to investigate the issues we've come to the conclusion that it needs to be refactorised as it's way too bad and it can't be solved (as a side note this issue has also been raised by a former dev who left the company). Although it was not part of the initial upcoming version release it was "forcefully" introduced in the plan and we took out of the scope other things but was still flagged as a potential risk. But wait..there's more, this feature was part of a Java microservice (the whole microservice basically) and our team is mostly made of JS, just one guy who actually works as a Java dev (I've only done one Java course during uni but never felt attracted to it). I've not been involved in the initial planning of this EPIC, my former TL was an the Java guy. Now during this the company decides that me and my TL were needed for a side project, so both of us got "pulled out" of the team and move there but we've also had to "manage" the team at the same time. In the end it's decided that since my TL will leave and I will take leadership of the team, I get "released" from the side project to manage the team. I'm left with about 3 weeks to slam dunk the feature.. but, I'm not a great leader for my team nor do I have the knowledge to help me teammate into fixing this Java MS, I do go about the normal schedule about asking him in the daily what is he working on and if he needs any help, but I don't really get into much details as I'm neither too much in sync with the feature nor with the technical part of Java. And here we are now in the last week, I've had several calls with PSO from the clients trying to push me into giving them a deadline on when will it be fixed that it's very important for the client to get this working in the next release and so on, however I do not hold an answer to that. I've been trying to explain to them that this was flagged as a risk and I can't guarantee them anything but that didn't seem to make them any happier. On the other side I feel like this team member has been slacking it a lot, his work this week would barely sum up a couple of hours from my point of view as I've asked him to push the branch he's been working on and checked his code changes. I'm a bit anxious to confront him however as I feel I haven't been on top of his situation either, not saying I was uninvolved but I definetly could have been a better manager for him and go into more details about his daily work and so on.

All in all there has been mistakes on all levels(maybe not on PSO as they can't really be held accountable for R&D inability to deliver stuff, but they should be a little more understandable at the very least) and it got us into a shitty situation which stresses me out and makes me feel like I've started my new position with a wrong step.

I'm just wondering if anyone has been in similar situations and has any tips or words of wisdom to share. Or how do you guys feel about the whole situation, am I just over stressing it? Did I get a good analysis, was there anything I could have done better? I'm open for any kind of feedback.

I think I finally, really, comprehend why secret societies have historically been created... I mean the potentially logical ones. This train of thought is logically terrifying.

I want a logic check.

I've been jokingly mentioning some of my totally true, practically useless in most scenarios, skills/specific fields of knowledge/ability under a moniker of 'extremely useful, assuming apocalyptic event' for years. Things like advanced knowledge of Coefficients of glass expansion, Fortran, various things that have caused friends to refer to me as MacGyver after the reboot came out.

In recent years, I've personally encountered several varieties of the ones defined by helplessness, self-victimisation, some version of a real disability... that theyve expounded into a personified personal nemesis-- to flashily battle yet never overcome, etc... the vast majority perplexing me as to why that's a valid form of life to them... it's not that they never consider some other way; the ball is just quickly dropped and never picked back up.

College?(not that I'm a big fan) they wish they could but so expensive... aide? The form was hard/confusing/past-due...

Lookup/learn something more indepth than a tiktok? *some self-deprecating bs*

Yet it's "I always wanted to do/be/learn X"

Shows like 'How It's Made' fascinate, but don't inspire enough for a 5min google query.

In the dev world its a clear, inverted pyramid-- one of the first posts I saw when I rejoined here was ostream's rant on Apple sucking because after they stop support/updates you "can't" load a different OS... ofc you can. But several comments down... no mention of that... i think it was @LensFlare who was the only one in ~15 respondents to point out the core logical fallacy.

Basic shit is totally forgotten... try asking some random adults what plastic is made from... or pay attention to how many people declare they have a gluten "allergy".

I get people frequently telling me that things im pointing out as differences don't matter because "it's just semantics"... semantics is literally the epitome of "significance", with roots in 'meaning' and 'truth'

Back to the main issue... We are in a world where DIY is typically something you pay more to do as a catered experience than actually learning anything, people destroy their own arguments hopes of validity unwittingly often by stating the arguement, get 'offended' or 'triggered' by factual statements, propagate misinformation and bastardise words until MW needs money enough to print a new version, likely adding the misuse as an actual definition and basic knowledge and the thought to actually learn is vetoed by the existence of google translate, the wisdom of tiktok and the pure brillance of troubleshooting every random linux issue you have from not knowing basic CLI and thinking linux makes you cool, with chmod 777 because so many other dumbasses on forums keep propagating misinformation. Ask them what 777 means, most have no clue... as they didnt consider googling that one before putting it in a terminal several times.
The number of humans that actually know the basic shit that the infrastructure of the world is built on keeps decreasing... and we aren't even keeping a running tally.

The structure of the internet has the right idea... dns- 13 active master root servers, with multiple redundancies if they start dropping... hell ICANN is like a secret society but publicly known/obfuscated... the modern internet hasnt had a global meltdown... aside from the lack of censorship and global availability changing the social definition of a valid use of braincells to essentially propagating spam as if it's factual and educational.

So many 'devs' so few understanding what a driver is, much less how to write one... irl network techs that don't know what dhcp is or that their equiptment has logs... professionals in deducated fields like Autism research/coping... no clue why it was called "autism", obesity and malnutrition simultaneously existing in the same humans... it's like we need to prepare a subterranean life-supporting vault and stock it like Noah's ark... just including the basic knowledge of things that used to be common/obvious. I've literally had 2 different, early 20s, female, certified medical assistants taking my medical history legitimately ask if not having a uterus made it harder to get pregnant...i wish i was joking.

Any ideas better than a subterranean human vault system? It's not like we can simply store detailed explanations, guides, media... unless we find a way to make them into obfuscated tiktok videos apparently on nonsense or makeup tutorials.

HOLY FUCK! Why is JS world so fucking confusing? I haven't even started learning it and its already giving me a headache. I feel like there are a billion different things i have to learn that aren't just "vanilla js". All i want to do is learn some web dev, take on freelance work, become a digital nomad. Im a simple C++ and ios/android developer things are so straight forward. JS seems like a clusterfuck of just stuff 😧 Id like to say this isnt a my language is > than yours rant. This is a "like what the fuck" rant. My brain was like Html, Css, JS cool thats all i have to learn... boy was i wrong. Can someone give me a word of wisdom as i go down this apparent rabbit hole?

Wednesday Wisdom
Tomorrow I am a better developer than today.
Today I am a better developer than yesterday.

I need a life advise - pls share your wisdom!

I have my first client located in the US. He wants to pay with a cashier's check and I have no idea how that works. How do you European or even german freelancer are getting paid by american clients?

had all four wisdom teeth pulled out last Saturday and been under pain killer otherwise I could neither chew shit nor sleep - feeling drowsy af but still have to server debug with another internal team - fml

Ok. I got it. I need a portfolio. That will speak for you. I’m working on it. I’m building great stuff. In the meantime. How the heck do I get a job as a junior web developer with no experience. I only have a coding bootcamp and a 4 month internship. All companies want people with experience. You won’t even have an interview without experience. So what’s the strategy then? Looking out for some words of wisdom from fellow devs.

Code has no conscience.

wk145

A uni kicked out here, enough said :3

// I don't wanna share my great achievement and wisdom in the official weekly topic thread 😆

“A computer language is not just a way of getting a computer to perform operations but rather that it is a novel formal medium for expressing ideas about methodology. Thus, programs must be written for people to read, and only incidentally for machines [including the human] to execute.” (The Structure and Interpretation of a Computer Programs, 1985)

“If you try to make something beautiful, it is often ugly. If you try to make something useful, it is often beautiful.” -Mr. OSCAR WILDE

Messaged my practice lead (and also good friend) with a root cause analysis as well as proposal on how to fix a problem after migration to mysql 5.7.

Now I’m waiting in defense mode to strike me back with his violent wisdom.

Waiting in line for a CT scan of my wisdom teeth, I have to remove it.

Me and @hardfault in this bitch together.

Sigh.

wIsdOm

My favorite xkcd quotes (order is not significant )
1. _*It's the world's tiniest open-source violin.*_
2. ...too honest. Scale it back.
3. I'd like to bestow upon you the first annual AWARD of EXCELLENCE in BEING VERY SMART. May you continue to grace our internet with your wisdom.
4. wait, what?
5. Yeah, uh ... I accidentally took the Fourier transform of my cat ...
6. Okay, we _suck_ at this.
7. You either need more medication or less. Not sure which.
8. I THINK EVERYONE INVOLVED HERE IS CUTE
9. World's Greatest Daughter
10. People who open bananas for the other end
11. Just for the sake of the argument, we should get a boat! You can invite the Devil, too, if you want.
12. This explain a lot.
13. My bag is 90% backup batteries.
14. Well- will you be my "it's complicated" on facebook?
15. Oh God. Gotta get out. The window.
16. Sweet! I finally got my subduction license!
17. I'll tell you later - you wouldn't appreciate the punchline over this 12kbps cell phone codec.
18. RON PAUL evolves into TRON PAUL
19. Just talk to them like a f***ing human being
20. In ordering #5, self-driving cars will happily drive you around, but if you tell them to drive to a car dealership, they just lock the doors and politely ask how long humans take to starve to death.
21. I eat my body weight in food every 31 days. That's slightly faster than the human average.
22. Nice try, Mike. Get out of the well.
23. Apollo retroreflectors
24. Can't see space vampires
25. My class on screenshots was a big hit, although for some reason I only ever sold one copy of the digital textbook.
26. WHAT.
27. Introducing The xkcd Phone 6, VIII, 10, X, 26, and 1876. We didn't start this nonconsecutive version number war, but we will not lose it.
28. My morality has evaporated over the harsh UV light.
29. Come on. Somewhere at the edge of the bell curve is the girl for me.
30. P.P.S. I can kill you with my brain.
31. Time to accelerate this giant machine up to terrifying speeds and steer it using my hands, which I am allowed to do because I took a 20-minute test in high school!
32. My normal approach is useless here
33. Wake up, sheeple!
34. Sir- strategic command has send us a lunch order.
35. Yeah, but first I'm gonna go comatose for a few hours, hallucinate vividly, and maybe suffer amnesia about the whole experience.
36. HOLY S***. Guys- people are complicated!
37. OH GOD- SPIDERS
38. Perhaps you need a crash course in taking hints. Here's your first lesson: We're not actually walking somewhere together; I'm trying to leave this conversation and you're following me.
39. How did the pole vaulters get up to our balcony?
40. Friggin' Python
41. I am the goddamn *Michael Jordan* of blurring the line between metaphor and reality. [tosses a basketball]

Wisdom teeth are the worse. I woke up 3 hours ago with a migraine.

Took my first PTO today since joining the new company to get my wisdom teeth extracted. Already took care of that first thing this morning. Now I actually get to kick back and listen to some records until my new GPU is delivered, and then I get to fuck off the rest of the weekend with new games because my wife says I can't do any yard work this weekend.

Only had the top two extracted because I was born without the bottoms I guess. But less pain on my wallet and my jaw, I'll happily trade in the narcotics they gave me and stick to my scotch.

Not a bad 3 day weekend in my book. Ill have to go back and figure out who/what broke the projection runner in the sandbox environment when I go back, but eh. that's a Monday problem now. 😎

I always see job posts for:
• ASP.NET
• Wordpress
• PHP & mySQL

Would you consider applying for these when you don't like these technologies? Why? I need your advice & wisdom guys. Thank you so much!

I think discussing / talking about whether your educations are useful or not is always gonna be a never ending debate.

Each person has their own unique way to nurture their true potentials. In my case, I always "thought" that taking college in Computer Science is such a waste of time and money, even I still try to survive with it these 3 years. In my first year, I fight a lot with my parents because I always said I wanna drop out and just get to work. But in the end...I still continue my journey for 3 years and yeah...I currently struggling to graduate. Maybe, after graduate, it will be a waste of time and money like how I thought about it. But I also learn that taking college journey have teach me a lot of things, like meeting so mane different kind of friends / people, time-management, etc. Maybe those Study Materials in Class will be forgotten in just a few years after I graduate, but those other life-lessons I believe will remain in myself for a long time...

Some people said if you are someone who wanna work hard, study hard, and have the grit to learn by yourself and committed to become a developer by yourself, you don't need college. But if you are someone who still find out your way, still figuring out whether it's the best choice to take computer science or not as a carreer, and you don't wanna waste time doing nothing, just get yourself to college.

The point is...it's just how we try to find out what's actually worked for us even if it's not the best choice.

Yesterday, I saw Someone posted about having wisdom tooth removed .....
Today I suddenly remembered, that I have 2 of mine lodged inside with no space to come out. They’re dormant....some day they gonna suddenly wake up and decide they wanna erupt......then I’m gonna be in pain and gonna have to have em removed.... :(

Oh DevRant community, I've come seeking for help and wisdom.
In my university the basic programming course uses Java and it's getting a bit outdated. The class has a lot of resources, like online videos and examples, but teachers from other departments say that the class doesn't teach students correctly.
I'm a student at that university, and I'm working in a group tasked to diagnose the class and seek for possible solutions. I need to know if some of you know about tools used to teach programming and algorithmic thinking in an interesting way at a university level. Something like Scratch or Karel, but for university students. If you have an example university I would love that!

I'm all for enhancing the user experience. To some extent, making the UI get out of the way to focus on getting things done is admirable!
But it's absolutely *NOT* acceptable to absolutely change how established convention works.
For example, clicking a link should not perform a state change. Use a flipping button!
Checkboxes should not act like radio buttons!
(apparently non-interactable) text should not perform actions!

Meditation. Or Awareness Meditation to be precise. It enables me to regain control over my mind, because I get distracted really fast. It really helps sorting things out, taking a step back and getting an overview where I actually am and if what I'm doing right now is actually relevant/has priority. I mostly find that it's not, so I have to return to the important stuff.

For those interested: meditation sounds weird, even obvious at first or you just don't get what's it all about. You actually have to practice meditation for a long time and study the concepts until you start to understand what all these phrases and talking means. Behind them lies great wisdom/huge amount of concepts which is easily underestimated. So don't be frustrated too much if you don't feel it working right away. Be assured I've been there too. Also don't start with meditations like 'just stop thinking or think nothing' because in my opinion this is highly complex shit and frustrating at first. Start with awareness or breathing meditations or even get an app to support your daily habit.

I need some Dev wisdom for you wonderful devRanters!

I have the opportunity to intern at a large multinational company overseas. I can get flown there and have a place to stay so that's not the issue. These are:

#1 it's cutting edge block-chain tech (not that I'll get to do anything super important) that I have no idea how it works. written in a language I don't know.

#2 they're trying to make a certain application of block chain technology proprietary and that goes completely against everything I stand for.

3# I'm only a 2nd year student and don't think I can handle uni while trying to catch up on a new development prosses, maintain decent grades and work part time at a job a might lose, if I go.

So, do I go?

This year I'm asked to teach Python with a GUI, but I've never used a graphic interface with Python. The chosen GUI must:
- Have an IDE, a sort of "drag and drop builder"
- Be capable of building software with forms, menus and multiple windows.
- Work with Windows 7 at least.
- Work with Python 3+

Any suggestions?

So far I tried:

- Tkinter: comes with the language (point in favor), but wasn't really able to make it work. Has no proper IDE, tried to use a builder called PAGE but doesn't seem to work.

- WxPython: didn't really play much with it. I've read some articles, but that's all.

- Qt: used several years ago with Ruby. Has an IDE (point in favor), but never tried with Python. This is my winner so far, the one big problem being the amount of stuff to install to properly work.

It is not only about how good your code is, it is also the business value your code provides.

- Unknown

Ah, the end of a very long work day, a beatiful time for me to click"update and shutdown" instead of "shutdown" on my laptop and being to scared to close the lid because I don't want to meet the thorn of God for ignoring the ancient wisdom of "Do not turn off your computer"

In my dev travels and dev journeys, i have learnt nothing but one thing. The secret of life. I will share with you devs today.
"Life is a free form jazz odyssey of mastubatory bullshit"

Lend me your wisdom o wise ones!
I'm tired of windows updates and im tired of it eating my background resources on my low end convertible(atom, 2gigs ram).
The only reason i'm still on windows is the touch support. Haven't yet found a distro where everything just works. Anyone here using a touch screen with linux?

Edit: I've tried hacking away with drivers and shit but feeble touch support just doesn't help as i primarily use it as a tablet

Hello guys. I present you my top 3 list of cringe people:

1️⃣ People who talk about their family, relatives, kids, partners, etc. No one wants to hear it.
2️⃣ People who talk about their mental health or body health issues. If you have health issues then go to a clinic. No one wants to hear
3️⃣ People who play Fortnite or Brawl Stars. People who play dumb pay-to-pay games for kids or smartphones. You're cringe

Honorable mention:
⏺️ People who live in a society = cringe

I decided to go for it, and build this chat GPT web-app. I built an authentication system for it crazy fast. While I’ve built several e-commerce websites, I’ve never actually owned one. What should I expect?

Fucking wisdom tooth. I just wanted to learn about deploying and that fucker gives me the worst headache since months

I am lost. Which package should I use?

1. ImageIntervention
2. Spatie/image

Pls share wisdom.

First and foremost, it's essential to figure out which IRS office is closest to your location. That, in itself, can be a daunting task, especially if you're not familiar with the area. Using the IRS's online office locator is a helpful start, but sometimes, even that leaves you with more questions than answers.

Then comes the joy of trying to get in touch with someone who can provide the specific information or assistance you need. Long hold times, automated systems, and a seemingly endless stream of recorded messages can leave you feeling like you're caught in an endless loop.

And let's not forget the paperwork. Different IRS offices often have different procedures, so finding the right forms and knowing how to fill them out correctly can be a headache.

In the end, it feels like a journey filled with frustration and uncertainty. But, here's a tip from someone who's been there: persistence pays off. Keep trying, be patient, and, if possible, reach out to others who've had similar experiences. Sometimes, a bit of collective wisdom can make this daunting process a little more manageable.

!rant One of the better refactoring insights I've heard today: "With great power comes great responsibility".

Just because a language may not care about certain constructs, doesn't mean you should be relaxed about them (e.g. weak/dynamic typing/not caring about (variable name) consistency).