- Get invited to apply to job
- Technical interview, guy shows up late starts small talk wasting time and gives me the exercise
- Start implementing the first algorithm, finish it passing min test cases then realize there's a solution that would make both algorithms a breeze
- I pitch my solution realizing there's no much time left, cuz we lost almost 20 min of my test hour talking about BS plus the almost 10 min he arrived late, and reassure the interviewer it can be developed faster
- Interviewer says it doesn't matter, we should finish edge cases
- Kay no problem, finish the first algorithm successfully and explain pitfalls on the second part with the current implementation
- I tell him there's a better solution but he doesn't seem to care, he says time's up

Now here's the funny part.

I get called by the recruiter today (2 weeks later) and she says "They are happy with your soft skills but feel there are some gaps with your coding, they would like to repeat the technical interview because they didn't feel there was much time to assess the 'gaps' ".
Interviewers, either I'm competent enough to work for you or not, your tests must be designed to assess that, if you see you can't fit the problem you want in the time you have left change the problem, reschedule or here's an idea...LEAVE THE BS CHITCHAT TILL THE END AND START THE INTERVIEW ON TIME. When I do interviews I always try to have one complete free hour and a one algorithm exercise because I expect the candidate to solve it, analyze it and offer alternatives or explain it, I've never had someone finishing more than 2 an hour.

You can keep your job I'll keep my time. I'll write a similar problem on the comments to pass on the knowledge for people who enjoy solving these kinds of problems, can't give you the exact same thing, also tip guys don't do NDA's for interviewing it makes no fucking sense trust me no one cares about your fizz buzz intellectual property.

Finally resigned.
I didn't hate my work but I need to grow. I was 4 years experienced and I was working on entry level positions. That's because for getting promoted I need to work like I'm on the next level for a year consistently, I don't know if I was working on next level but I felt confident that I can, so I switched companies finally. I don't know if work will be a lot what will I do but I have enough hard skills, my soft skills might not be that good but I'm finally doing something to achieve growth in that area. I'll be scared, anxious, helpless and all but let it be. I'll sprint, rest and repeat.

Forgot to secure my mongo db instance, found half the data gone, and a new db holding me at ransom , learn_how_to_recover_your_data , good thing offline backups are a thing.

Recovered in no time, never will I ever repeat this mistake

It's highly important that these wet wipes are not, and I repeat NOT, used by non other than professionals.

Note to self:

Don’t use npm, use yarn!
Don’t use npm, use yarn!
Don’t use npm, use yarn!

Don’t use what??👂
Npm! Use yarn!

Well done!! Now repeat this 5 times a day.

Bring the fun and curiosity back.

School education? Mostly rinse and repeat, learn from heart and do as you are told.

First job? Take these bread crumbs, shit out gold ingots, please.

There are few who had either very kind and gifted teachers / persons in their life or had a strong will / desire to learn by / for themselves - but it's hard to combine fun and curiosity with the - most of the time - very harsh reality and environment we live in.

I'd really wish that it would get back to fun and curiosity and not the endless myriad of bitching, hissing and fighting it usually is.

What I find most tiresome in education is the overflow of information with no value - most content is outdated, wrong, harmful, not precise and especially not helpful.

Thinking about good education I've got very fond memories of hanging out in IRC chats, talking with people who were "ancient" (la me 15-20, them 40 plus ;) ) and not being "shood" away, but rather getting fed by book recommendations, hints, appointments when they had more spare time to explain in private IRC sessions etc.

The atmosphere was always a "we might not have time for it, but we'll try and don't worry if you don't understand it".

When I'm trying to find information today... It's really 90 - 95 % filtering, 4 % try and error, 1 % finding what I need.

Me a month ago: "I'm done with full-time corporate work. I'm going to shift to freelance only so I can enjoy my life and not be in a grind, bowing and scraping to a manager all day."

*Recruiter finds me and offers me a full-time opportunity*

Me now: "Well, I guess I can look into it..."

Me 9 months from now: "I'm done with full-time corporate work. I'm going to shift to freelance only so I can enjoy my life and not be in a grind, bowing and scraping to a manager all day."

Repeat until dead.

On the further subject of "new trends" that piss me off, being in an important meeting, asking someone an important question about work they haven't completed, and getting back:

"Oh sorry I was *multitasking* then, could you repeat that?"

No you cloth-eared dufus, you weren't multitasking, you were focusing on only one thing - and it wasn't the meeting that you called and the meeting you're meant to be listening to. Arse.

When I write “grid-template-columns: repeat(auto-fill, minmax(max(15rem, (100% - (var(--columns) - 1) * 1rem) / var(--columns)), 1fr));” in my coworker’s code and it fixes the CSS grid

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

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

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

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

Imagine you work in a mechanic’s shop. You just got trained today on a new part install, including all the task-specific tools it takes to install it.

Some are standard tools, like a screwdriver, that most people know how to use. Others are complicated, single-purpose tools that only work to install this one part.

It takes you a couple of hours compared to other techs who learned quicker than you and can do it in 20 minutes. You go to bed that night thinking “I’ve got this. I’ll remember how this works tomorrow and I’ll be twice as fast tomorrow as I was today.”

The next morning, you wake up retaining a working, useful memory of only about 5% on how to use the specialized tools and installation of the part.

You retrain that day as a review, but your install time still suffers in comparison. You again feel confident by the end of the day that you understand and go to bed thinking you’ll at least get within 10-20 minutes of the faster techs in your install.

The next morning, you wake up retaining a working, useful memory of only 10% on how to use the specialized tools.

Repeat until you reach 100% mastery and match the other techs in speed and efficiency.

Oops! Scratch that! We are no longer using those tools or that part. We’re switching to this other thing that somehow everyone already knows or understands quickly. Start over.

This has been my entire development career. I’m so tired.

Spouting "we'll get there" on repeat literally does fuck all you fucking cunt

Last sprint is a mess.

Working on three products that are related one with another a little bit.

1. Bug reports are coming in;
2. We fix it and give for QA to test;
3. QA starts testing and it doesn’t work;
4. Because another team updated something in product A and product B depends on it.

Repeat for straight 14 days

what is the point of having massive HR departments if something as expected and frequent as university hiring can't go smoothly?

i managed to reach the interview round for a big 4 firm only for the interviewer to not show up for 4 hours from my time slot (i waited the entire time - took periodic screenshots for proof), HR to say "we'll reschedule your interview, this happened because of internal miscommunication" more than THREE months ago, and dip. until december they'd repeat the same. now they've ghosted. thanks, virtual hiring.

how is it the candidate's fault? found out this isn't rare by speaking to a few others from my network who i knew were interviewing for the same firm. for students whose lives can change completely based on the outcome of an opportunity that they came across due to sheer luck and could definitely make use of because of their hard work - this is so heartbreaking and demotivating.

My daily routine :`)

wake up between 5:00 am to 11:00 am -> eat unhealthy breakfast and sometimes miss breakfast -> watch useless youtube videos -> beat my meat -> do some coding -> watch more useless videos -> eat lunch -> do some more coding -> watch more useless videos -> eat dinner -> and then sleep

REPEAT

NEED HELP!!!

RAAAAAAH fuck fuck fucking shit!!! Fuck jest Typescript "on the fly" compilation esModuleInterop typeroots, missing definitions jest ts-ignore and xtest everywhere, manual npm linking with different pkg mgrs & pub to a private registry, building docker images locally and doing tag management across git, docker & kubernetes then cross fingers that prod which has 0 common setup with local & test somehow works, open architecture "tickets" and wait months before they resolve, then repeat ad infinitum. How the fuck can I be productive when I need to be all over the place all the time and deal with these meta-code shenanigans. I just wanna code, damned

!dev

I feel like I never lived/live my age. I feel like I have wasted childhood (who the fuck wastes their childhood?!), teenage years, university years, most of my 20's. And now, I'm in this state where I'm stuck thinking about what I should be doing to not repeat the same mistakes and how to make up for them (which is in itself repeating the same mistake again, lol). I should go to bed.

I propose renaming the title "project manager" into "plim". Why? Well, there is an old soviet nursery rhyme:

I came up with a new word
A funny word called Plim
And I repeat it over:
Plim, Plim, Plim!
It jumps around shouting
Plim, Plim, Plim
Nobody cares about it
Plim, Plim, Plim

!rant
Communication is IMPORTANT, and the way to approach someone is also IMPORTANT.

I experienced that my colleague is from China, and his English accent is so strong (in the context of not understandable, like the word 'folder' he pronounces it 'foda', and the word 'code' he pronounces it 'korr') that I have to ask him to repeat himself (which sometimes I felt guilty to ask him to repeat for thrice, and I am still not able to understand) or maybe we can do it over text. It is much easier to understand him that way and I can leverage these texts to see a bigger picture of the message.

From this, I realised I need to work more on understanding what he is going to say and what he actually meant.

Any advice for me?

The HR for my last employer sucks.

After I left, my employer changed record keepers for the 401k before I could rollover the funds to an IRA. I thought, “It will be fine. I’ll wait until they finish setting up the new record keeper. Then, I can do the rollover.”

When the blackout period was about to end, I didn’t receive any instructions about the new record keeper. The funds had been transferred already and I called the old record keeper to confirm it was done by my former employer. I think, “Maybe they forgot to contact me because I’m no longer an employee.”

I email HR and ask when I can expect instructions on how to access the new record keeper. Idiots send me instructions for the old record keeper and how to file for a distribution. HR had actually called the old record keeper for these instructions when the funds were no longer with the old record keeper. WTF 😤

It takes all of my strength to write a civil email. I remind them that funds were transferred nearly 2 weeks ago by them to a new record keeper. I repeat that I need instructions on how to access the new record keeper and I don’t need instructions on how to file for a distribution from the old record keeper.

I’m effing glad I don’t work there anymore. I can’t deal with that HR’s idiocy anymore.

When writing my bachelors thesis i worked five weeks 16-17 hrs a day without taking a single day off.

I didn't repeat this when doing masters.

I procrastinate. Which creates more bad dev days. Rinse, repeat. #Derp

I'm learning Rust as a case study for my own programming language. It's funny how many approaches exist to the humble loop.

- In classic procedural languages, a loop's job is to repeat actions, and as such it provides a multitude of tools to control this repetition.

- In all languages with iterators, a for-in loop is a construct that does something with every element of a collection. In languages with both iterators and generator functions, this can even be used to define a sequence in terms of another.

- In Rust, a loop is an expression that obtains its value through repeated execution. It can also be used like a classic loop, of course, but this is the interesting part.

- My little language is a functional language, so "loop" is the Y combinator. To loop means to define the value of an expression in terms of itself. It's the only looping construct, gets special treatment from the type checker and it's also used in recursive type definitions.

That moment when you find a function called with faulty arguments or a referece mistaken and fix it and code actually works now aaaaand you wake up.. i started to dream about the same code cause i keep rewriting it for different reasons.. what a life

Tech Lead = "Super quick question" + "one small doubt" back to back for 8 hours, then coding in the evening because making some progress is the only way to take the stress away. Rinse and repeat, while slowly developing an alcohol dependency. Be kind to your leads, kids.

Unclogging a workflow that stretches > dozen porjects, from building to analysis of build (static / lint check etc.)… Deployment.

It's frustrating.

Touching one thing and everything falls apart.

Thus small changes, fixing the rest of workflow, testing ...

Repeat .

Going now since 1 1/2 weeks. Possibly another or two weeks more.

It is soooooooo boring tedious annoyingly frustrating slowmotion shit

-.-

Any advice on how to find proper customer as a freelancer? Should I go on fiverrr and pay for coldcalling and an assistant?

Because honestly I'm sick of corporations employing me (my company) for the sake of not paying taxes but still expecting a 9 to 5 and all the corporate bullshit.

I just want to get customer, do UX, pay a designer, get figmas, implement, invoice, repeat. Not have 3 hours spring grooming calls stuck between a team meeting with management, a demo and a mid-spring alignment review. Is that too much to ask?

> Start a new project
> Search for modules / libraries you will need
> Find something promising
> See that it's not well maintained
> I'm just gonna send a quick PR
> Proceed to rewrite most of it.
> Huh ..
> Repeat~

Years ago I was in my late 20s.

Years and years ago.

If you asked me if I'd be drawn into a colossal waste of time as the whole country seemed to quite suddenly turn insane, i'd have called you crazy.

If you said 'you will have the same jobs at points others, you'll be tricked into driving around places under false pretenses and you'll have sex with 500+ women and keep forgetting because they'll find a way to tire you out or take advantage of some subject matter mirroring a childhood trauma' i'd say you were crazy.

well... none of you said that, so you're all crazy. otherwise now i'd say you were all honest and upright.

other than that my first day of repeat work was fine. thanks for asking. it feels good to do honest things for money.

maybe they like making me slowly filthy from some weird sex thing.

maybe this is a mating ritual of some sort lol

'fuck me you dirty dockworking ex jailbird on your way to becoming a developer all over again, you remind me of dad !"

A philosophical question about maintenance/updating.

There is no need to repeat the reasons we need to update our dependencies and our code. We know them/ especially regarding the security issues.
The real question is , "is that indicates a failure of automation"?

When i started thinking about code, and when also was a kid and saw all these sci fi universes with robots etc, the obvious thing was that you build an automation to do the job without having to work with it anymore. There is no meaning on automate something that need constant work above it.

When you have a car, you usually do not upgrade it all the time, you do some things of maintance (oil, tires) but it keeps your work on it in a logical amount.
A better example is the abacus, a calculating device which you know it works as it works.

A promise of functional programming is that because you are based on algebraic principles you do not have to worry so much about your code, you know it will doing the logical thing it supposed to do.
Unix philosophy made software that has been "updated" so little compared to all these modern apps.
Coding, because of its changeable nature is the first victim of the humans nature unsatisfying.

Modern software industry has so much of techniques and principles (solid, liquid, patterns, testing that that the air is air) and still needs so many developers to work on a project.
I know that you will blame the market needs (you cannot understand the need from the start, you have to do it agile) but i think that this is also a part of a problem .
Old devices evolved at much more slow pace. Radio was radio, and still a radio do its basic functionality the same war (the upgrades were only some memory functionalities like save your beloved frequencies and screen messages).

Although all answers are valid, i still feel, that we have failed. We have failed so much. The dream of being a programmer is to build something, bring you money or satisfaction, and you are bored so you build something completely new.

!Rant?

Hey, have been having several job interviews, does anyone have any advice on how to approach being interviewed by people from India, have been doing a lot of job interviews for a lot of companies in the US and seems like I'm interviewing for a position at India, it's very difficult to understand them and often they get offended when asked to repeat themselves... I try to be as positive and optimistic as I can but often poor audio on their part and very thick accent makes it difficult... any tips? this happen to more people? am I the only one?

Thanks...

Every time I have a large code base...

When you manage updating numerous 3rd party libraries by hand, git submodules sound like the greatest thing ever.

Replace all 3rd party sources with git submodules.

Realize how much of a pain in the ass they are and managing them yourself seems totally worth it again.

Replace submodules with folders of the 3rd party libraries.

Repeat...