A bit long story about language barrier.

So I worked at an Asia company. The company decided to close a Northern Europe site which was considered to have low productivity. I was sent to that site to learn and take their job back to HQ.

One day when I was there, we got an email from a developer in HQ, requesting feature changes in the software maintained by the Northern Europe site. I heard the local developers were discussing about the email in their language. I don't speak their language but I could feel that they were confusing. So I walked to them and ask if I could help. They show me the email written in English by the Asian developer in HQ. And I was surprised that even I (who speaks the same native language with HQ dev) couldn't fully understand what the mail wanted to express. So I called back to HQ and talked to the developer directly, in our native language.

Turns out, he actually tried to say a completely different thing with that was written in the email.

Until that moment, I finally know why the site was considered to have low productivity. The men in HQ just couldn't describe the requirements correctly. And sure you got false result when you give wrong requirements statements.

I was so angry and felt sorry about the developers in that closing site. They were far more talented and experienced than most my colleagues in HQ. But they were laid off only because communication errors in HQ developers.

> project nearing deadline [✔]
> an IDE that hangs itself [✔]
> awkward status meetings that turns into pointless discussion [✔]
> confusing requirements [✔]
> getting addicted to tea [✔]
> losing track of time [✔]
> sleepless nights [✔]
> overgrown hair and beard [✔]
> did I shower today ? [✔]
> no srsly did I ? [✔]
> I don't know where am going with this [✔]
> I should probably get some sleep [?!]

Man, I think we've all gotten way too many of these.

Normally most interactions that I have are through email. Eventually some would try to contact me via phone. These are some:

"Hey! We are calling you from <whatever company name> solutions! (most of them always seem to end on solutions or some shit like that) concerning the Ruby on Rails senior dev opportunity we were talking about via email"
<niceties, how are you doing, similar shit goes here...eventually>

So tell us! how good/comfortable would you say you are with C++?"

Me: I have never done anything serious with c++ and did just use it at school, but because I am not a professional in it I did not list it in my CV, what does it have to do with Rails?

Them: "Oh the applications of this position must be ready to take in additional duties which sometimes happen to be C or C++"

Me: Well that was not anywhere in the offer you sent, it specifically requested a full stack Rails developer that could work with 3 different frontend stacks already and like 4 different databases plus bla bla bla, I did not see c++ anywhere in it. Matter of fact I find it funny, one of the things that I was curious about was the salary, for what you are asking and specifically in the city in which you are asking it for 75k is way too low, you are seriously expecting a senior level rails dev to do all that AND take additional duties with c++? cpp could mean a billion different things"

Them: "well this is a big opportunity that will increase your level to senior position"

Me: the add ALREADY asks for a senior position, why are you making it sound that I will get build towards that level if you are already off the bat asking for seniors only to begin with?

Them: You are not getting it, it is an opportunity to grow into a senior, applicants right now are junior to mid-level

ME: You are all not making any sense, please don't contact me again.

=======

Them: We are looking for someone with 15 years experience with Swift development for mobile and web

Me: What is up with your people not making these requirements in paper? if I knew from the beginning that you people think that Swift is 15 years old I would have never agreed to this "interview"

Them: If you are not interested in that then might we offer this one for someone with 10 years experience as a full stack TypeScript developer.

Me: No, again, check your dates, this is insulting.

===

* For another Rails position

Them: How good are you with Ruby on Rails in terms of Python?

Me: excuse me? Python has nothing to do with Ruby on Rails.

Her (recruiter was a woman) * with a tone of superiority: I have it here that Python is the primary technology that accompanies Rails development.

Me (thinking this was a joke) : What do you think the RUBY part of Ruby on Rails is for? and what does "accompanies Rails development" even means?

Her: Well if you are not interested in using Rails with Python then maybe you can tell us about your experience in using Javascript as the main scripting platform for Rails.

Me: This is a joke, goodbye.

====

To be fair this was years ago when I still didn't know better and test the recruiters during the email part of being contacted. Now a days I feel sorry for everyone since I just say no without even bothering. This is a meme all on itself which no one has ever bothered to review and correct in years for now. I don't know why recruiters don't google themselves to see what people think of their "profession" in order to become better.

I've even had the Java/Javascript stupidity thrown at me by a local company. For that one it was someone from their very same HR department doing the rectuiter, their shop foreman was a friend of the family, did him the service of calling him to let him know that his HR was never going to land the kind of developer they were looking for with the retarded questions they had and sent him a detailed email concerning the correct information they needed for their JAVAscript job which they kept confusing with Java (for some reason in the context of Spring, they literally wanted nothing with Spring, they wanted some junior to do animations and shit like that on their company's website, which was in php, Java was nowhere in this equation)

I think people in web development get the short end of the stick when it comes to retarded recruiters more than anywhere else.

Supervisor: Go interview the client for requirements
Client:i want insert,update blablabla and searching,
Me: Delete?
Client:Nope we want store the data blablabla forever..
*after few weeks*
Supervisor:Can i see the progress?
Me: sure
Supervisor: where is the delete function? I want the delete button !!
Me: :/ *why the hell i hav to meet the client if i need to fllow my supervisor requirements*

#PracticalStudent #Internship #Confusing

*Dev is non-native english speaker

Dev: we need the VPN ip.
Me: the server ip or the connected device ip.
Dev: the server.
Me: gets the ip.
Dev: this doesn't work, is this the VPN ip ?
Me: Gives the device ip. Works.
Dev: OK. Works now.

Could have just asked for the client IP in the first place but s/he didn't know how to.

I have been trying to freelance for people who don't speak english as a first language and getting the Requirements is the hardest part of the job. 😫 .

P.S. Suggestions needed from remote freelancers. What's your workflow like.

I subscribe to many copywriting newsletters. Here's an article that shows how it's like on "the other side", marketers struggle, too.

How Kevin's Massive Mistake
Completely Changed His Life

Kevin H. made a huge mistake.

The biggest, he would say, if he could tell you himself.

And he knew it immediately.

It was, he said, "instant regret."

Within milliseconds, he was asking himself "What have I done..."

Kevin, see, had just jumped the rail of the single most popular suicide spot in the world, the Golden Gate Bridge.

On average, the site gets another distraught jumper every two weeks. Kevin was one of them.

It wasn't like he hadn't tried to quiet the voices in his head. Therapy, drugs, hospitalization.

Time to die, those voices still said.

And yet, in the minutes his bus dropped him off at the bridge, he hesitated and paced with tears in his eyes.

"I told myself if just one person comes up to me and asks if I'm okay... if one person asks if they can help... I won't do it. I'll stop and tell them my whole story..."

But nobody did, so he jumped.

It was in those next milliseconds, he would later say, he knew it was the biggest mistake of his life.

He didn't want to die.

But now, he was sure, it was too late.

From its highest point, it's a 245-foot plummet into the icy bay waters below.

Out of the 1,700 people that have jumped from the bridge since it first opened in 1937, only 25 have survived.

Kevin, against all odds, would be one of them.

He slammed into the water like hitting concrete. Three of his vertebrae instantly shattered.

When he surfaced, he couldn't hold his own head above water. But, incredibly, a sea lion kept pushing him up.

The Coast Guard soon arrived and pulled him out.

From there, he began a long recovery that required intense surgery, physical therapy, and psychiatric care.

While still under treatment, a priest urged him to give a talk to a bunch of seventh and eighth graders.

Afterward, they sent him a pile of letters, both encouraging and full of their own pained thoughts.

He also met a woman.

Today, Kevin lives in Atlanta and he's been happily married for the last 12 years.

And he tours the country, sharing his story.

So why re-tell it here?

Obviously -- I hope -- you don't get lots of copywriters looking to snuff it after a flopped headline test.

Just the same...

We've talked a lot in this space about the things one needs to get by in this biz.

My friend and colleague Joe, over at the publishing powerhouse Agora Financial, likes to list requirements.

You need intense curiosity...

You need a killer work ethic...

And you must, MUST have... resilience.

Meaning, you must have or find the capacity to bounce back from failure and flops, even huge ones.

Now, again, Kevin's story is an extreme and in this context -- I hope -- a hyperbolic example of somebody giving up. In the worst way possible.

It is also, though, a metaphor.

See, I get a lot of notes from some of you guys... and at conferences, I get to talk to a lot of people...

And I often get the sense, from some folks, that they're feeling a little more overwhelmed than they let on.

Some are just starting out, and they've got a lot on the line. For some, it's everything. And some are desperate to make it work.

Because they have to, because their pride or livelihoods or a family business is at stake, because it's a dream.

And yet, they're overwhelmed by all the tips and secrets... or by piles of confusing research or ideas...

For others, even had some success, but they're burned out, feel antiquated, or feel like "imposters" that know less than they let on, in an industry that's evolving.

To all those folks... and to you... I can only say, I've been there. And frankly, go back there now and again.

Flops happen, failures happen. And you can and will -- even years and decades into doing this -- make the wrong choices, pick the wrong projects, or botch the right ones.

The legendary Gene Schwartz put it this way, according to a quote spotted recently in fellow writer Ben Settle's e-letter...

" A very good copywriter is going to fail. If the guy doesn't fail, he's no good. He's got to fail. It hurts. But it's the only way to get the home runs the next time."

Once more, nobody -- I hope -- is taking the trials of this profession hard enough to make Kevin's choice.

And believe me, I don't mean to make light of the latter. I just want to make sure we hit this anvil with a big hammer. To drive home the point that, whatever your struggle, be it with this biz or something bigger, that you don't want to give up. Press on.

As Churchill put it, "Success, is the ability to go from failure to failure without losing your enthusiasm."

Or even more succinctly when he said, "If you're going through hell, keep going."

Because it's worth it.
.
John Forde

!rant

27 days ago I asked here for advice on how to mentor software engineer student that was terrible at coding.

So, we are in the middle of the mentoring, my approach is for her to get used to normal engineering tools, in this occasion she is learning Git and "kanban" (basically we are using Clubhouse for this one) and Github PR submission and approval (I'm the one who approves them, naturally) by doing.

With git, things are hard because we cannot share a terminal session (via upterm) due to her using Windows on her laptop (WSL is an option for using upterm but her internet is so damn slow doing the configuration takes way too long), otherwise teaching her use git would be smoother than it is currently, with the other tools she is gaining a good grasp of them, it pleases me that the bottleneck is with Git itself.

She is working on a hangman game with Python, nothing fancy just the terminal. I made the stories with the requirements in Clubhouse for her to work on each as a unit removing some "thought process" of reading requirements and implementing solutions (at Uni it seems the professor writes a document of several pages detailing the background of the project and the requirements, I can see how it can become confusing for some students like her).

She will start Uni again this August 10th, there is a chance that our first "session" at this will end by then, my fear is that she forgets how to use the tools she learned, so I need to find a way to encourage her to keep using them somehow.

I am the technical lead in a project which uses a C# based framework. It's a lot of drag and drop, and C# scripts can be embedded for fancy stuff.

Scripts in general are not hard to do, it's harder to understand the business rules rather than the code itself.

I got hired as a junior to build this project from scratch as an MVP, and we need another junior to add enhancements and minor changes required from our end users. Since management wants me to move on working on more mid-senior development stuff, I'm supposed to be only supervising the juniors work (in the hopes that one day they'll be able to work on their own).

We've had bad luck filling this position. Our last hire is a guy like 17 years older than me, supposedly with experience in said framework but OH DEAR GOD.

Fucktard can't understand requirements and corrections, isn't able to deliver a 20 line script without fucking up. I give him a list with 3 mistakes to fix and only fixes two, crap like that.

Now, hear me out, the mistakes are stuff like:

- Unused variables
- Confusing error messages
- Error messages written in spanglish (mix between Spanish and English, we're located in Latin America)
- Untested features, this is the worst of all.

You may say "but he's a junior", sure. But as I said, he supposedly has experience, more years in IT than me, and fine, you're allowed to fuck up a few times on your first tasks but not make the same mistakes over and over, specially since we've already sat down and addressed these issues in presence of the CTO.

Fuck this guy. I genuinely dislike him as a person also, he is from another latin country and we have some serious cultural differences. For instance, he insists on sucking your ass constantly, being overly well manered (we already saluted with the whole team at the daily stand up, stop saying hello, good day, regards in each of your fucking chat messages or task submissions), and other mannerisms that are hard to translate, but whatever, all of these attitudes are frowned upon here. They're not necessary, we just want to keep it simple, cordial and casual and see you deliver the crap that you're being paid for with a decent level of quality.

On Monday the CTO comes back from vacation, I'm looking forward to that meeting, gonna report his ass, there is evidence everywhere on our issue tracker.