Tech Industry: “We need more developers!”

NewDev: “Hire me”

Tech Industry: “only experienced developers please! We don’t have time to train juniors ”

Older Dev: “Hire me”

Tech Industry: “no, you want too much money and too much time off“

Mid dev: “Hire me”

Tech Industry: “only experienced devs who are a culture fit!”

Robot dev: “Hire me”

Tech Industry: “You are Hired”

Manager: Why is no one innovating?

Me: You hired all of us based on culture fit so you have optimized only in that direction. Everyone is same ... like you

Manager: You are right.

employee: I want growth in my role

company: *installs ping pong table*

employee: autonomy?

company: *creates fully-stocked snack room*

employee: fulfilment.

company: *employs a live DJ in the office*

employee: *quits*

company: some people just aren't a good culture fit.

Summing up many ridiculous meetings I've been in.

Many years ago we hired someone for HR that came from a large fortune 500 company, really big deal at the time.

Over the next 6 months, she scheduled weekly to bi-weekly, 1 to 2 hour meetings with *everyone* throughout the day. Meeting topics included 'How to better yourself', 'Trust the winner inside you'...you get the idea.

One 2-hour meeting involved taking a personality test. Her big plan was to force everyone to take the test, and weed out anyone who didn't fit the 'company culture'. Whatever that meant.

Knowing the game being played, several of us answered in the most introverted, border-line sociopath, 'leave me the frack alone!' way we could.

When she got the test results back, she called an 'emergency' meeting with all the devs and the VP of IS, deeply concerned about our fit in the company.

HR: "These tests results were very disturbing, but don't worry, none of you are being fired today. Together, we can work as team to bring you up to our standards. Any questions before we begin?"
Me: "Not a question, just a comment about the ABC personality test you used."
<she was a bit shocked I knew the name of the test because it was anonymized on the site and written portion>
Me: "That test was discredited 5 years ago and a few company's sued because the test could be used to discriminate against a certain demographic. It is still used in psychology, but along with other personality tests. The test is not a one-size-fits-all."

VP, in the front row, looked back at me, then at her.
HR: "Well....um...uh...um...We're not using the test that way. No one is getting fired."
DevA: "Then why are we here?"
DevB:"What was the point of the test? I don't understand?"
HR: "No, no...you don't understand...that wasn't the point at all, I'm sorry, this is getting blown out of proportion."
VP: "What is getting blown out of proportion? Now I'm confused. I think we all need some cooling off. Guys, head back to the office and let me figure out the next course of action."

She was fired about two weeks later. Any/all documentation relating to the tests were deleted from the server.

Minimum wage employers and restaurants asking "and why should we hire you?".

You have 40 vacancies in your area for just your company alone.
You're paying $13.25 an hour when only a year ago you were paying $9.75.

Why should we hire you?

F*ck you, pay me, that's why.

You're not f*cking NASA
You're a God damn chain restaurant with a 40% turnover rate, who's employees probably shoot up in the bathroom on the rare occasion they even get a break.

I looked at the guy with all the annoyance I could muster, stared him down for a good five seconds and said. "You pay a few dollars over minimum. You're job is not important enough to even ask that question. Have a nice day." And got up and left.

Dude followed me and stuttered " hold up. I was just..."

But I was already out the door.

You were just what mark? Asking a dumbfuck question as if you had any leverage at all?

Your competitor *across the street* is offering 50 cents *more* per hour, and has guaranteed breaks.

What, did you forget 2008 and how you treated millions of people as disposable? The little part where you and most american industries demanded passion, without pay raises? Promotions without benefits? The jobs that if you worked hard, rather than a promotion or a pay raise, your reward was more work and less hours to finish?

You assholes thought we forgot about that? How you shipped millions of jobs overseas, blamed it on "automation" (chinese and indian slave labor), and then pointed the finger at millions of impoverished people as "lazy" in places like Detroit and Pittsburgh and told them "you just got to work harder and smarter!" Or "just get a small loan and create the next google!" from the comfort of your yachts? I'm looking at you bane corp.

No, now the shoes on the other foot motherf*ckers. Hows it feel needing all *us* commoners? "Why should we hire you?"

No, why should *I* WORK FOR YOU?
Cuz I saw THREE dirty tables coming in. A line of people that could be being served. A line that could have been optimized with the proper table count and some simple changes. A menu that doesnt even incentivize your biggest sellers and a dozen other things your store is doing wrong.

Think mark, think!

This is one of those braindead questions employers paying sub $18 an hour ask, because they suffered so much brain drain from years of payola profits from too-big-to-fail wallstreet bailouts, that they forgot they are not king midas, unless they are the king midas of shit, because increasingly everything corporate America touches turns into shit.

And while were on the subject, stopping bringing in outside management to stores. It destroys team cohesion, staff morale, pisses off people *on site* who *actually know* the team, the stores daily activities and processes, and who are better fit for that role. You bring in disinterested outside management, and it's one of the biggest red flags I've ever seen: these smarmy selfcongratulating f*cks who know nothing about the particular store, have no connection to the staff, go on firing sprees or alienation-sprees to hire in friends, fuck up the schedules because again they know nothing about the employees, and then move on after a few years to greener pastures, leaving a barren radioactive wasteland of chain smokers and burnt out staff in their wake.

Dear corporate America, your free ride on the public's good will is over. It's over.

Now you're in the bitch seat. Come sit at my desk and explain to me, EXPLAIN TO ME, why I should sweat and labor to save your shitty company hemorrhaging money like a bleeding crack-addicted hobo dying with a sucking chest wound from a chicago skidrow friday-night drive-by?

You dont deserve it. Your management and company culture is worse than incompetent. It's full of smiley guys expounding about their passion for customer service while giving each other sloppy BJs in broom closets, a veritable cornucopia of cult-like corporate dick suckers *and* dickheads, proclaiming, no...PROFESSING (hence "professional") their undying allegiance and dedication to their corporate family with the intensity of cujo, foaming at the mouth, or Mitt Romney preparing for a photoshoot, plastic smiles and feigned laughs.

Dont forget to wipe your chin, asshole. It's not Ronald McDonald your blowing, but it's definitely not Gordon f*cking Ramsey either.

Would you like fries with that?

"Do you easily get offended?"

"We have a bro culture here. [Some other stuff and examples] So do you think you can fit in here?"

"Tell us about a time you had to communicate with people who are not as technically capable as you."

I can remember more but cba tbh.

Probably the most awkward feeling call happened to me just recently.

I was to interview a guy that's like 10 years older from me with 10y more experience in mostly unrelated tech. I was prepared to have some respect for the guy, and was a bit anxious, but that changed quickly.

The first fucking thing he says, on the fucking job Interview is essentially "I've worked in tech for 20 or so years, and I don't appreciate being tested" great start .. needless to say, I tried to reformulate all my prepared Interview questions so they sound as casual as I could while still trying to get him to tell me *anything*. Most of the time I just felt like "why are we even here dude, you clearly don't care about any of this"...

About 12 or so questions later It was finally clear that none of his experience is useful, and even the exp he has sounds like past companies kept him around as a number...

I want to try a few more edge cases, hoping to find anything we could work with, when he calls me out on it and says "Well now you're testing me, I don't like being tested" at which point I pretty much gave up on the dude and let my HR colleague talk.

Then out of nowhere the guy brings up his mortgage, and how he needs money, and how no one wants to give him a job, and that if we don't want him, we should just tell him now.

Then he starts asking how many people we're interviewing, which is obviously stuff we can't answer, I just said "normal amount" to dodge the question at first, but that just made him more closed off and he just silently remarked "so you can be picky..."

That was one of the most painful interviews I had so far. Me and ny colleague pretty much instantly agreed that he's not a good culture fit for us. Probably not a fit for any company really, not with that attitude.

PS: it was a video call, though he had his camera turned off at first, so it was only me with a camera for half the call. He turned it on just about as I had enough of him.

Help.

I'm a hardware guy. If I do software, it's bare-metal (almost always). I need to fully understand my build system and tweak it exactly to my needs. I'm the sorta guy that needs memory alignment and bitwise operations on a daily basis. I'm always cautious about processor cycles, memory allocation, and power consumption. I think twice if I really need to use a float there and I consider exactly what cost the abstraction layers I build come at.

I had done some web design and development, but that was back in the day when you knew all the workarounds for IE 5-7 by heart and when people were disappointed there wasn't going to be a XHTML 2.0. I didn't build anything large until recently.

Since that time, a lot has happened. Web development has evolved in a way I didn't really fancy, to say the least. Client-side rendering for everything the server could easily do? Of course. Wasting precious energy on mobile devices because it works well enough? Naturally. Solving the simplest problems with a gigantic mess of dependencies you don't even bother to inspect? Well, how else are you going to handle all your sensitive data?

I was going to compare this to the Arduino culture of using modules you don't understand in code you don't understand. But then again, you don't see consumer products or customer-specific electronics powered by an Arduino (at least not that I'm aware of).

I'm just not fit for that shooting-drills-at-walls methodology for getting holes. I'm not against neither easy nor pretty-to-look-at solutions, but it just comes across as wasteful for me nowadays.

So, after my hiatus from web development, I've now been in a sort of internet platform project for a few months. I'm now directly confronted with all that you guys love and hate, frontend frameworks and Node for the backend and whatever. I deliberately didn't voice my opinion when the stack was chosen, because I didn't want to interfere with the modern ways and instead get some experience out of it (and I am).

And now, I'm slowly starting to feel like it was OKAY to work like this.

Just need to get this off my chest. Started a new job 3 weeks ago at a company that has been around ~18 years, it is only recently that they have started to grow more rapidly. I was brought in under the guise that they wanted to embrace change and better practices and so said I was up for the challenge.

In my 2nd week I was asked to produce a document on tackling the technical debt and an approach to software development in the future for 3 consultants who were coming in to review the development practices of the company on behalf of the private equity firm who has taken a major stake in the company. I wrote the document trying to be factual about the current state and where I wanted to go, key points being:

Currently a tightly coupled monolith with little separation of concerns (73 projects in one solution but you have to build two other solutions to get it to build because there are direct references.).

Little to no adherence to SOLID principles.

No automated testing whatsoever.

Libraries all directly referenced using the file system rather than Nuget.

I set out a plan which said we needed to introduce TDD, breaking dependencies, splitting libraries into separate projects with nuget packages. Start adhering to SOLID principles, looking at breaking the project down into smaller services using the strangler pattern etc. After submitting what I had written to be part of a larger document I was told that it had been tweaked as they felt it was too negative. I asked to see the master document and it turns out they had completely excluded it.

I’ve had open and frank discussions with the dev team who to me have espoused that previously they have tried to do better, tackle technical debt etc but have struggled to get management to allow them. All in all a fairly poor culture. They seem almost resigned to their fate.

In my first 2 weeks I was told to get myself acquainted and to settle myself in. I started looking at the code and was quite shocked at how poorly written a lot of it was and in discussions with my manager have been critical of the code base and quite passionate and opinionated about the changes I want to see.

Then on Friday, the end of my third week, I was invited to a meeting for a catch up. The first thing I was told was that they felt I was being too openly critical in the office and whether I was a good fit for the company, essentially a stay or go ultimatum. I’ve asked for the weekend to think about it.

I’ve been a little rocked by it being so quickly asked if I was a good fit for the company and it got my back up. I told them that I was a good fit but for me to stay I want to see a commitment to changes, they told me that they had commitments to deliver new features and that we might be able to do it at some point in the future but for now I just needed to crack on.

Ordinarily I would just walk but I’ve recently started the process to adopt kids and changing jobs right now would blow that out the water. At the same time I’m passionate about what I do and having a high standards, I’m not going to be silenced for being critical but maybe I will try and tackle it in a different way. I think my biggest issue is that my boss who was previously a Senior Developer (my current position) has worked at the company for 12 years and it is his only job, so when I’m being critical it’s most likely criticising code he wrote. I find it hard to have the respect of a boss who I had to teach what a unit test was and how to write one. It makes it hard to preach good standards when by all accounts they don’t see the problems.

Just wondering if anyone has suggestions or experience that might help me tackle this situation?

Got reminded of this job search bullshit they say after interviews, when they say you're not "fit for the culture" but they want you to be "challenging the status-quo".
Like, take a fucking pick. Either you want someone who follows and fits in, or you want someone who innovates and stands out. 😒

Working in the embedded systems industry for most of my life, I can tell you methodical testing by the software engineers is significantly lacking. Compared to the higher level language development with unit tests and etc, something i think the higher level abstracted industry actually hit out the of park successfully.

The culture around unit testing and testing in general is far superior in java and the rest.

Down here in embedded all too often I hear “well it worked on my setup... it worked at my desk”.. or Oh I forgot to test that part.. or I didn’t think that perticular value could get passed in... etc I’ve heard it all. Then I’ve also heard, you can’t do TTD or unit tests like high level on embedded... HORSESHIT!

You most definitely can! This book is a great book to prove a point or use as confirmation you are doing things correctly. My history with this book was I gonna as doing my own technique of unit testing based on my experience in the high level. Was it perfect no but I caught much more than if I hadn’t done the testing. THEN I found this book, and was like ohh cool I’m glad I’m on the right thought process because essentially what they were doing in the book is what I was doing just slightly less structured and missing a few things.

I’ve seen coworkers immediately think it’s impossible to utilize host testing .. wrong.

Come to find out most the of problems actually are related to lack of abstraction or for thought out into software system design by many lone wolf embedded developers.. either being alone, or not having to think about repercussions of writing direct register writes in application or creating 1500 line “main functions” because their perception is “main = application”. (Not everyone is like this) but it seems to be related to the EEs writing code ( they don’t know wha the CS knows) and CS writing over abstraction and won’t fit on Embedded... then you have CEs that either get both sides or don’t.. the ones to understand the low level need but also get high level concepts and pariadigms and adapt them to low level requirements BOOM those are the special folks.

ANYway..the book is great because it’s a great beginner book for those embedded folks who don’t understand what TDD is or Unit testing and think they can’t do it because they are embedded. So all they do is AdHoc testing on the fly no recording results no concluding data very quick spot check and done....

If your embedded software engineers say they can’t unit test or do TDD or anything other than AdHoc Testing...Throw the book at them and say you want the unit test results report by next week Friday and walk away.

Lol

Man, I'm sure there are a million of these posts right now but...

The hiring market and hiring culture nowadays is so damn frustrating. I have a decade of experience in multiple senior/lead/principal roles at both big name companies and high-growth startups, along with a very well-written resume.

Even with this, I can barely get an interview these days. I'll apply to a role that lists qualifications for which I'm an exact fit, and either get a quick auto-denial or just never hear back at all. It doesn't matter if I custom-craft my resume and cover letter to match the job description or just send my standard resume and cover letter. We all love those pandering and patronizing "We know that this isn't the news you wanted to hear, but keep trying! Maybe you'll be good enough for us someday!" auto-denial email.

Sometimes I'll receive a denial, look back at the job posting, that they needed somebody with NLP experience or something, and say to myself "Fair enough, that makes sense." Other times, I'll look at the posting and say "Oh come on, I check every single box." It makes you wonder "What the fuck are you actually truly looking for?"

Sometimes I'll look at the company's current employees and see that almost every single one is ex-FAANG, indicating that the company will almost only hire other ex-FAANG employees (despite there being thousands of other well-qualified candidates out there who are just as talented and skilled as those ex-FAANG candidates.)

Other companies seem to be "brand shopping" for ex-FAANG employees after all the recent FAANG layoffs, hoping to land a bargain on an ex-Google engineer so they can brag that their product was built by the same people who built Google.

Then there's the question of even making it past the ATS and in front of an actual human's eyes. The hiring culture seems to be an ATS SEO game nowadays. God forbid that you didn't include the super secret magic keyword in your resume, else you'll automatically be filtered out and denied.

It's just incredibly frustrating and makes you wonder what kind of candidate you need to be to even get a first round interview nowadays. Do we all need to have a glowing personal recommendation from the ghost of Steve Jobs in order for a 50-person startup to even open our resumes?

dev, ~boring

This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.

I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:

1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by

I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.

At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:

"Hierarchy and structure should arise from an understanding of a problem domain"

As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.

In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.

Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).

I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:

1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth

Given that, I can devise a heuristic, organic framework for growing a team:

- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it

Last thing isn't derived from the train of thought, just things I feel are true:

- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy

/rant

I recently quit a job which I excelled at technically, but professionally I struggled. The best way to put it is that I was incompatible with my newly appointed manager. My frustration with that manager led to many inappropriate comments that I made in front of him and a couple of other senior leaders. To be clear, I never cursed at them or called them names or raised my voice, but I did make (multiple) comments about their ignorance of projects or lack of experience in this speciality. I’m sure you can tell that didn’t go over well.

Ultimately, my behavior got me put on a PIP by my manager. He explained that I was excellent at the job, but not mature enough to do well. This obviously greatly upset me, and I quit on the spot. I know what a PIP means and I wasn’t about to get fired. I had been at the company for about three years and have dozens of excellent professional references (at this company and others) from as high up as the C-suite to as low as individual contributing peers who I worked closely with. They can all honestly and passionately speak to my technical and soft skills very highly. However, this doesn’t seem to matter in my situation.

Overall, I excel at interviews. Within days after quitting I had over eight different interviews lined up. I made it to final rounds of five and got two offers already (still waiting to hear back from the other three). The offers were both contingent on passing employment and background checks. Well, I gave my references, have no criminal history and never lied on any part of my background or history (though I did not admit to my emotional issues with my previous management team). Needless to say, I was shocked when both offers got rescinded.

One company claimed it was due to a change in the role, and the other told me frankly that the “manager did some digging on my history and unfortunately doesn’t feel like I would be a culture fit.” I looked up the manager on LinkedIn and lo and behold, they are connected with my former manager. This has me worried as back-channel references are super common in my industry, and my industry is not very big overall. My manager appears to be very well connected with many of the companies I am interviewing with or hope to in the future.

I will admit that my behavior previously was very disrespectful and probably deserved the reprimand, but now I feel that I am not able to move past it and learn from this experience as my reputation in the industry seems to be damaged. I’m still fairly early in my career overall and am learning how to handle office politics. It’s been a big struggle for me, but I do get better with each passing year.

Anyway, I’ve decided to wait for the other three final stage companies that I’m in talks with before I officially decide that this manager is my blocker, but assuming he is, what do you recommend I do to get past this? Should I talk to him? As this is all fresh, I’m not sure I can do that now, but maybe in a few months? Either way, I need a job now and can’t afford to go more than two months without a paycheck (and I don’t qualify for unemployment as I quit). What do you recommend I do?

I have been growing this creepy stache for a month now. I am hoping the "not fitting company culture"-ness of it will steadily attain me work-from-home privileges.

If it does fit the company culture, I am fucked in more ways than one.

Didn't get to the next interview stage because of "culture fit" 😔
What does that even mean?

Worst recruiter experience wasn't mine, but it was one I overheard:

Buddy of mine who, like me, was older does a couple rounds of interviews at a nice place and gets a call back from the company recruiter. He puts the recruiter on speaker phone so I can hear too.

They are very nice and tell him they selected another candidate, bummer but no big deal.

Hey I the age of ghosting at least they called right?

He is still upbeat and asks if there was anything he could do better interview or technical stuff.

She tells him "We weren't sure you would fit into the culture."

This is a bit odd as this guy is outgoing and one of those folks that everyone loves being around and working with, just a naturally likeable guy.

He asks what she meant about culture fit and she responds "Well you're older..."

He thinks he misheard her and asks again "Your older and we don't think you will fit in that way."

I dedicate this to all of those hr gurus from top tech companies that rejected me cause they think I won’t fit their culture despite me crushing all their technical interviews, fuck them and their soft skills stupid questions.
I won’t fit there anyways cause I can express my own thoughts using sarcasm and irony and I’m not scared of doing it cause I don’t care about your amazing company culture that prefer robots not people with a little sense of humor. I don’t care about my failures cause there was so many I don’t give a fuck. And by the way if you ask me why I want to work in your amazing company I would always say cause you asked me to work for you and now you treat me like shit. Then 10 years later you blame everyone for toxic culture lol.

I need to rant about life decisions, and choosing a dev career probably too early. Not extremely development related, but it's the life of a developer.

TL;DR: I tried a new thing and that thing is now my thing. The new thing is way more work than my old thing but way more rewarding & exciting. Try new things.

I taught myself to program when I was a kid (11 or 12 years old), and since then I have always been absolutely sure that I wanted to be a games programmer. I took classes in high school and college with that aim, and chose a games programming degree. Everything was so simple, nail the degree, get a job programming something, and take the first games job that I could and go from there.

I have always had random side hobbies that I liked to teach myself, just like programming. And in uni I decided that I wanted to learn another language (natural, not programming) because growing up in England meant that I only learned English and was rarely exposed to anything else. The idea of knowing another fascinated me.

So I dabbled in a few different languages, tried to find a culture that seemed to fit my style and attitude to life and others, and eventually found myself learning Korean. That quickly became something I was doing every single day, and I decided I needed to go to Korea and see what life there could be like.

I found out that my university offered a free summer school program for a couple of weeks, all I had to pay for was the flights. So a few months later I was there and it was literally the best thing I'd done in my life to that point. I'd found two things that made me feel even better than the idea of becoming the games programmer I'd always wanted to be. Travelling and using my other language to communicate with people that I couldn't in English. At that point I was still just a beginner, but even the simple conversations with people who couldn't speak English felt awesome.

So when I returned home, I found that that trip had completely thrown a spanner into my life plan. All I could think about after that was improving my language skills and going back there for as long as possible. Who knows what to do.

I did exactly that. I studied harder than I'd ever studied for anything and left the next year to go and study in Korea, now with intermediate language skills, everyday conversations no longer being a problem at all.

Now I live here, I will be here for the next year and I have to return to England for one year to finish my degree. Then instead of having my simple plan of becoming a developer, I can think of nothing I want to do less than just stay in England doing the same job every day, nothing to do with language. I need to be at least travelling to Korea, and using my language skills in at least some way.

The current WIP plan is to take intensive language classes here (from next week, every single weekday), build awesome dev side projects and contribute to open source stuff. Then try to build a life of freelance translation/interpreting/language teaching and software development (maybe here, maybe Korea).

So the point of this rant is that before, I had a solid plan. Now I am sat in my bed in Korea writing this, thinking about how I have almost no idea how I'm going to build the life that I want. And yet somehow, the uncertainty makes this so much more exciting and fulfilling. There's a lot more worrying, planning and deciding to do. But I think the fact that I completely changed my life goals just through a small decision one day to satisfy a curiosity is a huge life lesson for me. And maybe reading this will help other people decide to just try doing something different for once, and see if your life plan holds up.

If it does, never stop trying new things. If it doesn't (like mine), then you now know that you've found something that you love as much as or even more that your plan before. Something that you might have lived your whole life never finding.

I don't expect many people to read this all, but writing it here has been very cathartic for me, and it's still a rant because now I have so much more work and planning to do. But it's the good kind of work.

Things aren't so simple now, but they're way more worth it.

So after 7 months of soul crushing searching I was able to land an awesome job I never thought I'd get! I didn't really get hired for my projects, I think I was more of a culture fit that knew enough of what they were talking about. My colleagues are awesome, helpful people but they are also clearly way ahead of me as devs. I know that many new hires have similar feelings and it's more a matter of drive + time. I understand that and I'm ready for the marathon ahead of me but I have one HUGE concern... I don't understand unit testing. I've never written unit tests in JavaScript or Java (just on paper I wrote random assert statements for a college exam question that somehow turned out correct). More importantly, I don't understand when to write unit tests and what my main objectives should be when writing them. At work they talk about unit testing like it's just as basic as understanding version control or design patterns, both of which I have had no problems asking questions about because I at least understood them generally. I come here looking for resources, mainly things I can go through over the weekend. I understand that I'm going to have to ask my colleagues for help at some point but I DON'T want to ask for help without any solid base knowledge on unit testing. I would feel much more comfortable if I could understand the concepts of unit testing generally, and then ask my team members for help on how to best apply that knowledge. I'm sorry for begging, I'll definitely be looking for resources on my own too. But if anyone could point me to resources they found to be helpful & comprehensive, or resources that they'd want their co-workers to use if they were in my position I would be very grateful!!!!

When you're told you are a great culture fit, and have great experience - but not ENOUGH experience.

Feels bad man.

Hey guys. I am in a situation where I need to decide wether to take on a new project or not. And if not, how to turn down that client so that I would not burn any bridges. So I need your opinions on this matter in order to make the final decision.

To make things clear heres some background info. 10 months ago I quitted my fulltime position in another EU country and went back to my own home country. 10 months forward till today and I have my own ltd company which currently has 5 projects. Its doing pretty well money wise. All projects combined, I already earn more then I ever did and I need to work max 10 hours a week since all projects are remote projects so I dont waste time on useless meetings and etc. However I dont feel fulfilled or challenged anymore because surprise surprise doing well paid projects doesnt guarante your sense of fulfillment.

So I noticed that I have lots of spare time which I spend diving into rabbitholes with hobby projects. I decided that its time to scale my company and take on more projects and maybe even hire more people.

So I started searching for other projects I could work on (prefferibly remote projects or flexible ones where I could come in 2-3 days a week in office and work remotely rest of the week). Reason being that I am already out of sync with fulltime position lifestyle and I am totally result oriented, not punch in my hours and go home oriented.

For exampleIf i get my weekly tasks I prefer to do them in 1-2 days (even if it requires doing double shifts which rarely but happens) but then I want to have rest of the week off. Thats how my brain works and thats how Im wired. I cant stand fulltime positions especially in enterprise bigger companies where I come in and do maybe 2 hours of actual work everyday because of all useless meetings and blockers from backend/etc. Its soul crushing to me.

So I posted linkedin ads and started searching for new clients/projects. One month ago I went to an interview for an android project in a startup.

The project looked interesting enough. Main task was to rewrite their android app from java to kotlin. Apparently their current current app was built by a backend developer who wants to focus solely on backend.

So during the interview they showed me their app which was quite simple frontend wise but not so simple backend wise from what I was able to figure out.

Their project lead (also a backed guy) asked me my estimation of price and completion of task. I told them maybe 2-3 months to do everything properly.

Project lead was basically shocked because all other candidates told him they can rewrite the app from java to kotlin in 2-3 weeks. I told him that everything is possible but his app quality will suffer and for a better estimation he would we would need to sign an NDA so I could evaluate the costs. So we ended the interview.

After that we kept in touch for one month (it took them one month to google a generic NDA and sign it digitally with me).

So heres the redflags I noticed:

1. They dont respect my time. Wasted 1 month of my time and after signing NDA gave me 2days to estimate their project and go to a meeting and give them detailed info about what I can offer. I thats not a brain rape then I dont know what it is

2. They are changing initial conditions we talked about. We agreed on rewriting the codebase and be done with it. Now they prefer a fulltime worker who would be responsible for android app as his own product. So basically project lead was not able to find a fulltime dev so now hes trying to convert me (a company owner) to his fulltime worker.

3. Lack of respect. During the interview he started speaking in his own native language to me with some expression (he seemed pissed off at that moment when he switched languages).

4. Bad culture fit. As I said Im used to relaxed clients and projects where I dont need to be chained to a desk a monitored and be micromanaged. I mean lets sign a contract give me access to your codebase and tell me what to do, I will produce results and lets be done with it.

5. Project lead is a backend guy who doesnt understand how complicated android apps can be. No architecture and no unit tests are in his frontend app. He doesnt care about writing proper app since he ships it in his own device so he doesnt need to worry about supporting custom devices or different api levels of android and etc. But not having any architecture? Cmon.

So basically I am confused. Project lead needs a fulltime dev but hes in contact with me in hopes that I would sign a fulltime contract. But how I can work fulltime if all what I can see are redflags?

Basicaly I thinkthis was a misundersanding. Im searching for fulltime remote projects and hes offering fulltime inhouse projects. Project lead never outsourced so hes confused as well.

As you can see decision is already basically made to turn him down, I just need to know how to tell him to fck off in the most polite manner and thats it.

Ah, culture fit. It's funny that what highly determines you getting the job is how well you get along with the team in the warm-up phase (meeting the team). If in a casual conversation with the guys you already clash personalities, they will find a way to push you out.

I realized that now...

Got called by a recruiter, the team wanted to know if I am culture fit. They schedule a remote skype interview for 3 hours and check if I am culture fit. Next is onsite interview, they asked me if I want to fly to that location which is 2 hour technical. And one of the guy in previous round mentioned they dont give offer unless they do onsite. But I have to pay out of my own pocket expense. I am approx 4 years experience and the position is Senior SW. I dont know are they really interested?

i need some advice on how to deal with office culture. i am a covid graduate and this is my first wfo job. it is technically hybrid but quickly turning into full time office, and there are several examples of scenarios, where i am not only feeling just frustrated, but hurt and retaliation.

my whole team is in a different city except 4 of us : pm, sr ios dev, me(android dev) and a sr android dev. in our office, there are 50 more people , but i rarely need to contact anyone except my team from another city or these 3 folks. also, we 4 are new joinees like just joined in last 2 months.

so let's discuss the problems.

1. there have been very shitty decisions that are leading to loss of everyone just because a few are unlucky. here's an example. on may 1, international labor day, we 4 had a leave showing. but it was not showing for other people. maybe because ourbleave calender was aligned to other city or maybe coz we are new, idk. but someone told the boss of manager, and he mailed to us that there is no leave :/ wtf

2. another news: our is shifting from we work to another co-working space. it is being heard that office will be now 3/5 days instead of 2/5 . when we joined, it was showing 3/5 days in our hr portal, but hr assured that it is 2/5 days. and we would still go 2/5 days only. but like that holiday scenario, people are buzzing and talking, and they might end up getting our 2/5 culture tonget fucked too. this is very stupid, since i am wasting 4 hrs everyday travelling.

3. let's talk about the snakes in the 4 ppl group. the ios dev and manager are sweet looking girl snakes. ios girl is the meek snake and pm is the wicked snake. once i discussed with ios girl about how we need to rush every morning at 8 am to reach office as our standup is at 10. i told her that i would raise this matter in standup and when i did, she was just mum as fuck. didn't even voted a fucking yes when the boss said "ok let's have a vote on it" . i mean man what the fuck are your scared of? the boss won't kill you bitch for clocking 30 mins late

4. the other snake is pm. i am pretty sure she was one of the people for which that leave was not showing and she informed the boss's boss. day before that i told her jokingly that once i leave the office, I won't be opening my laptop and since today it was decided that tomorrow is the holiday, I am unreachable and therefore enjoying the vacay due to lack of latest info.
the bitch fucking whatsapped me to say that she got a call from boss that tomorrow's a working day. it would have been the perfect fucking leave.
I am pretty sure a lot of people are hating me for leaving so early too. i oeave at 5pm , as i have to be at gym by 7. also 1 minute past 5 and i would be travelling in a jam packed metro, so yeah, no thanks. but this bitch is definitely telling my boss about this.

5 finally the biggest snake is this *cough-cough* "sr" android guy. dude's code is so shittu and hacky, i can sense that he didn't tried to understand the class and just added a function at any place he felt fit. he also is a schemy bitch, as he has somehow convinced noss to let him wotk just 1/5 days in wfo.

but i didn't cared about him much until now. yesterday i sent a link regarding latest Android dev update in the official channel as a fun read, and his reply was "probably should have seen theeynote yesterday" bitch it wasn't even mentioned in that keynote! i just checked its summary after his message, but then it was too late to retaliate.

and now that i see, he always tries to be smug and cool. not that i care, roast me all you want in front of your crush, I won't mind, but if you're trying to show people that am not an able dev, then buckle up bitch, either you or me are counting last breaths.

Just be true to yourself and to them. Know your own terms when looking for a job, and know if their terms fit with you. Ask them a lot of questions. These questions should provide you a glimpse of what their company culture is like. Try to have fun during the entire process. Don't stress out. And believe in yourself!

****these tips are actually somewhat meant for me but we're all in this together in the process of job hunting

The company is bad-mouthing the dev that I replaced:
"oh he liked to do things in a separate environment first and it took him time to complete tasks"
Sufficied to say he was not a good culture fit, so they let him go.
Clearly I am in a place with "Just do it" attitude