Me VS Dentist:

Me: Hey Doc, it hearts on the left side of my jaw, can you take a look at it maybe?

Dentist: Awh that’s nothing. If you just keep it clean there is no problem. Let’s make a picture just to be sure.

Also Dentist: i can’t see it with my bare eyes but the picture indicates an upcoming problem on the right side. I HAVE TO REPAIR THIS!

No fucking complaints there but still.

This reminds me of IT people and car mechanics. They can tell you anything to earn cash from you.

Oh look. The monitoring channel is in flames, smartphone is vibrating so hard it's having a seizure.

Hm. Nah it's fine. Not my...

Damn it. Incoming call. -.-

I'm actually on vacation (more like you need to trim down overtime before management get's angry).

They decided to test the new hardware / os stack I set up in the last weeks. I'd actually be happy about it If I wasn't on vacation and would be part in something that I invested a lot of time...

Well now I am. Guess what. It's running too good.

And that's not a joke. It's partly due to an upgrade in infrastructure (got rid of some last remaining 1 Gbps networks)… but also because I changed quite a lot on the OS / VM side plus we changed from XEN to Proxmox... With major tweaks, too.

The whole stack can now handle peak traffic where it would choke before, and even go beyond the old peak traffic.

Enough of introduction, the simple reason why shit burned down was because they tried out the current development branch and let it ran.

The development branch had an currently unfinished ratelimiter framework, since I didn't had time for an full burn in and didn't knew what the maxima / limits were. And since I hadn't finished that, I didn't finish the traffic shaping either.

Hm. Guess it's not good when you let a bunch of heavy parallelized data generators / analyzers run for free....

In the end, we simply shotgunned the docker development machines, because thanks to network congestion / retransmissions and feedback, they were not really cooperative via network / REST.

But hey: To infinity and beyond. XD

When morning walk ended up in a photo walk

Me :

I will use .Trim() before ToLower(), so ToLower has potentially less characters to iterate over.

Also me :

What ? Only 5.000 rows ? Let’s load them all ! It’s faster then use “where” and “group by”. No problems !

Developers after Microsoft picked up npmjs...

Hey, guys!

I'm new here and I want to introduce myself and meet you too.

My name is Mariana, I'm 21 years old and I live in Brasilia, capital of Brazil.

I'm a beginer in the world of development and I joined on this community to know more about this world. I am currently studying js, react and react native, but I am passionate about database, in the future I want to work with data science.

And you? Feel free to introduce yourself too! :)

Yeah, I might be late but finally get to watch season 6 of Silicon Valley 😁😁

I don't like WFH too much but I'm saving a lot of money working from my house ✌🏻

Read. Everything. CAREFULLY.

And do some research if needed.

Books are there for a reason.

Seems pretty obvious, uh?

Just do your Job😂🤪!!

I had a problem visualizing giant job/schedule dependencies trees a few years ago and basically wrote a program to convert the dependencies so it could be read in by a JS graph program that actually did the work. The output was a Gantt chart but really messed up, overlapping arrows, not very readable.

Today someone asked me for my app and but in a better format/visualization.

I so I was thinking how do I do this... Figure out which nodes are leaves, how to combine visually.

Programmatically you just link all the Nodes together. So I was thinking like how u need to use BFS and Mark when each more is traverse and on its first traversal, add it to a Map<Depth,List<Node>> then print each level, etc.

But not so straight forward.... But finally realized that I'm not trying to draw a Tree (or a tree where the rootams are actually in the middle and the top n bottom are leaves)... But actually a Graph.... A DAG....

SO FINALLY I googled and found GraphViz...
https://graphviz.gitlab.io/gallery/

And in the gallery I opened some pictures and printed at the bottom was like 1996...

And I'm now wondering "how the fuck did they do this?" Calculate where all the vertices should be placed so they can be linked with lines and and not look like a big mess...I guess like a yarnball

junior dev @30, not bad. 🙏👍💪

!rant
Just started working for a new company. Super cool. Just like the last one (as far as perks), except they actually trust their devs.

Old company: Make sure your code is extensible
Devs at old company: You know it's not written in stone right?
Old company: Does that mean you can make it do this?
Devs at old company: No. That's the wrong code base

New company: I need a feature. Get it done when you can
New company devs: Well, guess I'll take some time to refactor all this stuff while I'm at it
~Some time later~
New company: Thanks, that feature works great!

No staring over shoulders, asking when it will be done. No asking why we want to refactor something. As long as work continues to flow, there are no issues. It's great!

Also, if we want to try a new tech, we just have to put together a short paper explaining why it will work better in that situation than the tech that's already in place.

................

This is so accurate...

(From random twitter post)

...........

Working on my automatic garden ! :d thx Raspberry

confused screaming!!

Part of a product I used to work on contained a one time password generator that randomly strung together a few words from a word list.

Nothing wrong with the security, but this word list hadn't been filtered, so we did have a "bug report" from a customer who had a one time password that contained a questionable phrase:

"fucking pork Muslim"

...Call me a terrible person, but I never did get around to fixing that...

Just my shaved pussy in the middle of the work weekend.
(At this point I really hope I'm attaching the right image)

Updated. Got my second monitor. The laptop itself is only kept open for the fingerprint reader.

We just moved offices, and I got a desk by the wall, so I took full advantage.

Writing clean code.
Writing useful comments.
Commit before experimenting.

Just anything to prevent Technical Debt. Just because it works doesn't mean it should be kept as is. Later down the line you'll need to add a new feature and you'll spend 2x more time fixing the things you took for granted.

I got a raise 😊

Side projects are one of the biggest battery booster you can have.

For me it's common to get burnt out with fixing a bug or refactoring some pretty old logic, and working in side projects is a nice break to recharge the batteries without necessarily getting your mind totally out of programming. It doesn't matter if they are yours our someone else's, they can do wonders.

(Also, it's good to learn different stuff from what you are used to, like frontend developer working on some back-end logic in a side project)

Yeah... I'm not complaining 😁

Seems like my heavy Desktop-PC became portable for a x24 download-speed 😂

*80 GB for GTA V Steam-Version are worth it...

I miss visual studio.

Moving from .NET on windows to Java on Linux is not fun.

VS > Eclipse

Gilfoyle <3

Got a job as an Android Developer 🎉🎉🎉