Continuation from :
https://devrant.io/rants/835693/...

Hi everybody! I am sorry that as a first time poster I am building 2 long stories, but I really like the idea of connecting with other people here!

Well, as I was mentioning before, I got a job in Android development and had a blast with it. Me and the developer clicked and would spend our time discussing PHP, the move to other stacks (I was making him love the idea of Django or Spring Java) games, bands and cool stuff like that. This dude was my hero, his own stack was developed in a similar MVC fashion that he had implemented from scratch before for many projects. It was through him that I learned how to use my own code (rather than frameworks and other libraries) to build what I wanted. I seriously thought that I had it made with a position that respected me and placed me in the lead mobile development position of the company. Then it happened. He had taken 2 weeks of unauthorized leave, which was ok since he was best friends with the owner of the company, those 2 along another asshole started it so they could do whatever they wanted. And I could not make much progress without him being there since there were things that he needed to do, that I was not allowed, for me to continue. When he came back I was quickly rushed to the owner of the company's office to discuss my lack of progress. The lead developer was livid, as if he knew that he had fucked up. He blamed the whole thing on me (literally told the owner that it was my fault before I was summoned) and that we lost 2 weeks of business time because I did not had the initiative to make progress on my own. I felt absolutely horrible, someone that I had trusted and befriended doing something like that, I really felt like shit. I had mad respect and love for this guy. It got heated, I showed the owner the text messages in which I showed him my pleas to led me finish the parts that were needed while he was away. Funny enough, he acted betrayed. After that it was 3 months of barely talking to one another except for work related stuff. He got cold and would barely let me touch the internal code that he was developing. It was painful. The owner kept complaining about progress and demanded that I do a document scanner for the company, which was to be attached to their mobile application. Not only that but it had to be done with OpenCV. Now, CV is great, but it is its own area, it takes a while to be able to develop something nice with it that is efficient and not a shitstorm.
I had two weeks.
Finished in one. After burning my brain and ensuring that the c++ code was not giving issues and the project was steady I turned it in...to their dismay. And I say so because I felt that they gave me such a huge project with the intention of firing me if it was not done. After that it was constant shit from the owner and the lead developer. I was asked then to port the code to the IOS version. I had some knowledge of it already so I started working on it. Progress was fast since the initial idea was already there and I really love working on Apple devices. And when I was 70% done the owner decided to cut me loose. At first he cited things such as lack of funding and him being unable to pay my salary. I was fine with that even though I knew it was not true. So at the time I just nodded and thanked the company for my time there. Before I left, he decided to blame it on me, stating that if they were not producing money that it was perhaps my fault. I lost my shit, and started using my military voice to explain to him how a software company is normally ran. Then I stormed out.
It was known to me, that the lead developer had actually argued against me being laid off. And that he was upset about it, we made amends, but the fact remains that I was laid off because the owner did not think of me as an asset, regardless of how many times I worked alongside the lead developer or how valuable I was actually to the company, their infrastructure did get better while we worked together, so I just assumed that he never actually did any mention of my value.

I lasted 2 months without a job, feeling horribly shitty because my wife had to work harder to ensure our stability whilst I was without any sort of salary. At this time I had already my degree, so all I had to do was look better. In the meantime I decided to study more about other technologies. I learn React, and got way better at JS and Node that I thought I could and was finally able to get another job as a full stack developer for another company.
I have been here since 2 months. It has been weird, we do classic ASP, which is completely pointless at this time, but meh. At this time though, I just don't really have the same motivation. Its really hard for me to trust the people that I work with and would like to connect with more developers.

@Flux

I read https://devrant.com/rants/1845851/...

I was going to comment until I realized it was a post from 300 days ago.

Just want to say ask you how it went or give a post mortem. Also Congratulations. I hope you brought a long run way when you started almost a year ago.

Remember starting is 80% of finishing, and carrying through is the other 20%.

Success looks easy when all you see are the success stories. Steve jobs wasn't the most famous marketer, he was the most famous salesman, and what he sold was a dream.

Marketing is a buzzword, and a lot of companies try to use marketing as a replacement for sales people, but nothing really beats a good sales person or team. Thats the secret to marketing: forgo it as much as possible and work on sales and relationships instead. Awareness is nice, but money and sales are better.

This coming from a guy who had six businesses by the time he was twenty six and helped his family to start two other successful businesses.

Apparently I'm good at helping other people make money just not good at helping myself do it.

What I've learned is if you can get 1 customer you can get 10 and if you can get 10 you can get 100. And then keep going.

Good luck.

In reply to this:
https://devrant.com/rants/260590/...

As a senior dev for over 13 years, I will break you point by point in the most realistic way, so you don't get in troubles for following internet boring paternal advices.

1) False. Being go-ahead, pro active and prone to learn is a good thing in most places.
This doesn't mean being an entitled asshole, but standing for yourself (don't get put down and used to do shit for others, or it will become the routine) and show good learning and exploration skills will definitely put you under a good light.
2)False. 2 things to check:
a) if the guy over you is an entitled asshole who thinkg you're going to steal his job and will try to sabotage you or not answer acting annoyed, or if it's a cool guy.
Choose wisely your questions and put them all togheter. Don't be that guy that fires questions in crumbles, one every 2 minutes.
Put them togheter and try to work out the obvious and what can be done through google or chatgpt by yourself. Then collect the hard ones for the experienced guy and ask them all at once. He's been put over you to help you.

3) Idiotic. NO.
Working code = good code. It's always been like this.
If you follow this idiotic advice you will annoy everyone.
The thing about renaming variables and crap it's called a standard. Most company will have a document with one if there is a need to follow it.
What remains are common programming conventions that everyone mostly follows.

Else you'll end up getting crazy at all the rules and small conventions and will start to do messy hot spaghetti code filled with syntactic sugar that no one likes, included yourself.

4)LMAO.
This mostly never happens (seniors send to juniors) in real life.
But it happens on the other side (junior code gets reviewed).
He must either be a crap programmer or stopped learning years ago(?)

5) This is absolutely true.
Programming is not a forgiving job if you're not honest.
Covering up mess in programming is mostly impossible, expecially when git and all that stuff with your name on it came out.
Be honest, admit your faults, ask if not sure.
Code is code, if it's wrong it won't work magically and sooner or later it will fire back.

6)Somewhat true, but it all depends on the deadline you're given and the complexity of the logic to be implemented.
If very complex you have to divide an conquer (usually)

7)LMAO, this one might be true for multi billionaire companies with thousand of employees.
Normal companies rarely do that because it's a waste of time. They pass knowledge by word or with concise documentation that later gets explained by seniors or TL's to the devs.
Try following this and as a junior:
1) you will have written shit docs and wasted time
2) you will come up to the devs at the deadline with half of the code done and them saying wtf who told you to do that

8) See? What an oxymoron ahahah
Look at point 3 of this guy than re-read this.
This alone should prove you that I'm right for everything else.

9) Half true.
Watch your ass. You need to understand what you're going to put yourself into.
If it's some unknown deep sea shit, with no documentations whatsoever you will end up with a sore ass and pulling your hair finding crumbles of code that make that unknown thing work.
Believe me and not him.
I have been there. To say one, I've been doing some high level project for using powerful RFID reading antennas for doing large warehouse inventory with high speed (instead of counting manually or scanning pieces, the put rfid tags inside the boxes and pass a scanner between shelves, reading all the inventory).
I had to deal with all the RFID protocol, the math behind radio waves (yes, knowing it will let you configure them more efficently and avoid conflicts), know a whole new SDK from them I've never used again (useless knowledge = time wasted and no resume worthy material for your next job) and so on.
It was a grueling, hair pulling, horrible experience that brought me nothing in return execpt the skill of accepting and embracing the pain of such experiences.

And I can go on with other stories. Horror Stories.
If it's something that is doable but it's complex, hard or just interesting, go for it. Expecially if the tech involved is something marketable.

10) Yes, and you can't stop learning, expecially now that AI will start to cover more and more of our work.

https://thriveglobal.com/stories/...

What's your business life like? Do you work at home (while being employed) or do you do you seperate private and business-related physically?

Top 5 Reasons for Not Discussing Weird Topics in Your Graduate Admission Essay

Knowing the top five reasons for not discussing weird topics in your graduate admission essay is very important. There is really no strict requirement about what kind of topic you use, as long as you can discuss it effectively. However, choosing weird topics may not really work for you, especially if it’s a very controversial or sensitive one. The following are the top five reasons why you should avoid discussing weird topics in your essay.

Reason #1: Weird topics are weird.

First off, weird topics are exactly that, weird. The last thing you want to do is weird out your graduate school admission panel, which is almost a sure way of getting yourself that polite rejection letter that every applicant dreads of receiving.

One of the main important points to remember is to think of your audience when writing your graduate admission essay. This audience will be composed of tenured professors, and probably younger teachers closer to your own age. Although it is a good idea not to tailor your essay according to what you think they want to hear, it’s best to stick to a topic that will make the panel want to get to know you more. You can do this by putting yourself in the admission officer’s shoes and trying to feel what your reaction would be with a particular topic you have in mind. Being creative is good, but to any audience, weird is weird, and most audiences will not know how to react to a weird admission essay.

Reason #2: Weird topics may reflect your personality in a bad way.

Weird topics make you look weird, or worse. You may think that a weird topic is the same as a creative topic, something that most experts on admissions officers urge applicants to use. With a weird topic, you can easily make the jump from being creative to just plain strange or worse, someone with an emotional or personality problem. Weird topics, when discussed ineffectively, are bad topics, and can be anything from the death of a pet, recent religious epiphanies, and even parent bashing. These topics are the last topics that can paint you in a good light so avoid these and other similar topics.

Reason #3: Weird topics may not represent the real you.

Weird topics will not paint the real you, unless you are naturally weird. If you really think that being a little bit off will pay off, then by all means do so. But if you want to appear as normal and as emotionally healthy as possible, save the strange stories for Halloween night.

Reason #4: Weird topics may seem too informal.

Weird topics can get too informal. You can be informal but you need to look normal as well in order to avoid appearing irreverent. Some may disagree with this, but often the only way to get on your admission panel’s good side is to tread on the middle ground arefully, and not be too stiff and prudish but not be too loose either.

Reason #5: Weird topics may confuse the readers.

While most schools allow their applicants free reign when it comes to writing an admissions essay, you can do your self a lot of good by treading on the middle ground. Avoid weird or strange topics if you can. A weird topic will put your readers in a place where they may not understand you. And in a process where getting to know you as a person is the main objective, this move will definitely have an effect on whether you get accepted or not. Knowing what to write in a graduate school admission essay is fairly easy, especially if the school provides you with a set of questions, known as prompts as your guide. As long as you already have the other requirements such as the right grade point average, recommendation letters, program of study and the like, you can start working on your essay. But if your still not sure whether it good idea to write essay by yourself. You can find tons of great quality writing services such as https://uk-essays.com/research-pape.... At such a websites you’ll easily find help from from people who already have considerable experience in writing a wide variety of essays. They will gladly help in any issue that makes you difficult.