Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "developer career"
-
!rant
After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:
1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.
2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)
3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.
4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.
5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.
6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.
7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.
8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.
9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)
10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...
These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!222 -
Biggest hurdle? Probably other people telling me no.
- My parents wouldn't let me go to college to study CS because 'this computer thing is just a fad and you won't be able to make a living off it'. Instead they pulled me out of school early and made me go study automotive so I could be a mechanic like my dad.
- At 22, my boss at my first tech company job heard I was taking Java classes in the evenings. Told me to stop wasting my money because I'd never be a programmer.
- Got a job at a game development company as a document writer. I could code by then. When I was done with my work I'd look for bugs and send the solutions to the programmers so they could submit them. Tech lead found out and flipped out. Said I wasn't allowed to look at the code because I 'hadn't been hired as a programmer'.
Today I'm a senior developer and pretty happy with my career.
When people tell you that you can't do something, that should be all the motivation you need to work your ass off to prove them wrong.15 -
Worst dev I've interviewed?
"Archie" ran his own consulting business for almost 20 years. Prior to his interview, Archie sent HR (to send to us) his company's website, where he had samples of code for us to review (which was not bad, this guy did know his stuff).
What I found odd was Archie was the lone wolf at his company, but everything I found about him (the about page, his bio, etc), Archie was referred to as 'Mr. Archie Brown'.
Ex. 'Mr. Archie Brown began his humble career and 'Mr. Archie Brown is active in his church and volunteers his time in many charities ...'
Odd to refer to yourself in the third person on your own site, but OK, I like putting hot sauce on my mac & cheese (no judgement here).
Then the interview..standard stuff, then..
Me: "Given your experience, this is an entry level developer position. Do you feel the work would be challenging enough for you?"
Archie: "Yes, Mr. Archie Brown would have no problem starting at bottom. You see ..."
Almost any time he would reference himself, instead of 'me' or 'I', he would say 'Mr. Archie Brown'. As the interview continued, the ego and self-importance grew and grew.
My interview partner wanted to be done by using the escape clause, "PaperTrail, I'm good, do you have any questions?"
Yes, yes I do. I was having too much fun listening to this guy ramble on about himself. I made the interview go the full hour with the majority of time 'Archie' telling us how great he is.
The icing on the cake was my partner caught his gold cuff-links and tie-pin where his initials and how he kept raising his hands and playing with his tie to show us (which I totally missed, then was like "oh yea, that was weird")
After the interview, talking with HR:
HR-Jake: "How did it go?"
John: "Terrible. One of the worst. We would have been done in 10 minutes if PaperTrail didn't keep asking questions."
Me: "Are you kidding!? I had the best time ever. I wish I could have stayed longer."
HR-Jake: "Really? This guy was so full of himself I wasn't sure to even schedule with you guys. With his experience, I thought it deserved at least a round with you two. You think we should give him a chance?"
Me: "Hell no. Never in a million years, no. I never in my whole life met anyone with such a big ego. I mean, he kept referring to himself in the third person. Who does that?"
HR-Jake: "Whew!...yea, he did that in the phone interview too. It was a red flag for us as well."
Couple of weeks later I ran into HR-Jake in the break room.
HR-Jake: "Remember Mr. Archie Brown?"
Me: "To my dying day, I will never forget Mr. Archie Brown."
HR-Jake: "I called him later that day to tell him the good news and he accused me of being a racist. If we didn't give him the job, he was getting a lawyer and sue us for discrimination."
Me: "What the frack!"
HR-Jake: "Yep, and guess what? Got a letter from his lawyer today. I don't think a case will come in front of a judge, but if you have any notes from the interview, I'll need them."
Me: "What are we going to do?"
HR-Jake: "Play the waiting game between lawyers. We're pretty sure he'll run out of money before we do."
After about 6 months, and a theft conviction (that story made the local paper), Mr. Archie Brooks dropped his case (or his lawyers did).23 -
I'm at my seat during the regular morning routine of checking emails, planning the things I need to complete/study when my phone rings.
HR: Good Morning, can you come over to the conference room please ?
Me: Sure
I enter the conference room and on the other side of the table, I see a group of 3 HR Managers (not a very nice feeling), especially when it was 10 months into my first job as a Trainee Software Developer.
HR: The company hasn't been performing as expected. For this reason, we've been told to cut down our staff. We're sorry but we have to let you go. You've been doing a great job all along. Thank you.
Me: ---- (seriously ?!)
The security-in-chief 'escorts' me out of the premises and I hand over the badge. I'm not allowed to return to my desk.
This happened about 16 years ago. But it stuck with me throughout my programming career.
A couple of Lessons Learnt which may help some of the developers today :
- You're not as important as you think, no matter what you do and how well you do it.
- Working hard is one thing, working smart is another. You'll understand the difference when your appraisals comes around each year.
- Focus on your work but always keep an eye on your company's health.
- Be patient with your Manager; if you're having a rough time, its likely he/she is suffering more.
- Programming solo is great fun. However it takes other skills that are not so interesting, to earn a living.
- You may think the Clients sounds stupid, talks silly and demands the stars; ever wonder what they think about you.
- When faced with a tough problem, try to 'fix' the Client first, then look for a solution.
- If you hate making code changes, don't curse the Client or your Manager - we coders collectively created a world of infinite possibilities. No point blaming them.
- Sharing your ideas matter.
- Software Development is a really long chain of ever-growing links that you may grok rather late in your career. But its still worth all the effort if you enjoy it.
I like to think of programming as a pursuit that combines mathematical precision and artistic randomness to create some pretty amazing stuff.
Thanks for reading.14 -
The university system is fucked.
I've been working in this industry for a few years now, but have been self taught for much longer. I'm only just starting college and I'm already angry.
What does a college degree really mean anymore? From some of the posts I've seen on devRant, it certainly doesn't ensure professional conduct, work ethic, or quality (shout out to the brave souls who deal with the lack of these daily). Companies should hire based on talent, not on a degree. Universities should focus more on real world applications or at least offer such programs for students interested in entering the workforce rather than research positions. A sizable chunk of universities' income (in the U.S. at least) comes from research and corporate sponsorships, and educating students is secondary to that. Nowadays education is treated as a business instead of a tool to create value in the world. That's what I signed up for, anyway - gaining the knowledge to create value in the world. And yet I along with many others feel so restricted, so bogged down with requirements, fees, shitty professors, and shitty university resources. There is so much knowledge out there that can be put to instant practical use - I am constantly shocked at the things left out of my college curriculum (lack of automated tests, version control, inadequate or inaccurate coverage of design patterns and philosophies) - things that are ABSOLUTELY essential to be successful in this career path.
It's wonderful that we eventually find the resources we need, or the motivation to develop essential skills, but it's sad that so many students in university lack proper direction through no fault of their own.
Fuck you, universities, for being so inflexible and consistently failing to serve your basic purpose - one of if not the most important purpose on this earth.
Fuck you, corporations, for hiring and paying based on degree. Fuck you, management, for being so ignorant about the industry you work in.
Fuck you, clients, who treat intelligent people like dirt, make unreasonable demands, pull some really shady shit, and perpetuate a damaging stereotype.
And fuck you to the developer who wrote my company's antipattern-filled, stringy-as-all hell codebase without comments. Just. Fuck you.17 -
This happened when I was on third semester of the career at university. I had my first boyfriend, the "Python" guy. He has that nickname because he used Python as his main programming language and nobody on the classroom used it.
In a few words, he was a... horrible human being. He talked down to me almost all the time, saying to me that my country was sh*t (he is from United States, and for a reason he never wanted to told me, he cannot go back to his country), that my university was sh*t and he said "you're will be lucky if you rot programming in a chair".
As you might wondering, yes, unfortunately it was a toxic relationship. Once he said he wanted to kill the teacher because he though that he hacked his laptop D:
He claimed that he was going to teach me python and security stuff, bla bla bla, but nothing. I learned python by my own.
I almost lost my faith in dev future because I though that the only ones that could have a real future in programming where people without ethics and only if they have a friend or a relative on a company.
The saddest part was that I dated him because I love smart boys, but he was just an idiot that, furthermore, wanted to change me (he pressured me to have tattoos, dye my hair and have sex, things that, of course, I didn't do).
I found courage to break up with him. I waited until the semester ends (in order not to lose my programming final projects) and, the day after the last day of class, I broke up with him.
I recovered my faith on programming when, next semester, one of the teachers invited me to give a python programming workshop :D and I gave two python workshops, and two of mobile development.
Now I'm working as a junior .NET developer. Thank God I broke up with him before the relationship became even worse. "Python" wanted to marry me after a year! O_O11 -
My first rant here, don't know how to start, but fuck these self proclaimed senior developers who can't even get their concepts right about basic things and don't believe in reading docs.
Fuck you for asking if sequelize has a method to return details of the logged in user of your app, it's a fucking ORM you dumbfuck. You are a "full stack" developer for fuck's sake.
Fuck you for making those "minor changes" which breaks build and then blame it on any random plugin or lib used, or my commits.
Fuck you for expecting me to review your code on Sundays because you couldn't finish it on time.
I don't like java, at all, but even I get that without it we wouldn't be where we are right now and can't reach where we aspire to reach. But you can't keep chanting "Java is dead, Java is dead" every chance you get. No, it's NOT dead. Nor is going to, anytime soon.
And for god's sake, please stop choosing one library/plugin over another just on the basis of stars on repo, it's not the only (or valid) criteria. Look if you actually even need it. Think.
And please learn how to google first, and also stop using "the" before every the noun, the adjective and the verb. It's the fucking the annoying to read.
And yes, there are different linting presets out there, and just because a piece of code in a plugin/library/boilerplate is not following your specific, and may I say horrible standard, doesn't mean it's a "bad code". It's written by people who have created/worked-on these libraries as side projects on which your entire career is based upon.
And I haven't even talked about the code you write or your domain knowledge or the way you treat other people. So get off your high horse and behave like a developer, a real one.8 -
Attended one of the best meetups ever. To give you an idea how awesome it was..
Speaker took the first ~20 minutes introducing himself.
His intro card deck kept referring to himself in the third person (he is the only employee in consulting 'company'). Ex. "Mr. Smith began his humble career .."
The powerpoint presentation began with him clicking each page, not executing the slideshow (ex. pressing F5).
Finally someone asked "Can you make slide bigger?"
S:"You can't read that?..um..sure...I guess .."
Starts fumbling around the zoom ...
Dev: "No, can you start the slideshow?"
S: "I don't know what you mean...there...I zoomed it, is that better? Now I can't see my notes..just sec.."
<fumbles again with the zoom>
Dev: "No, not zoom, start the slide show, press F5"
S: "Oh...you want me to F5 it...OK..."
<he *clicks* the slide show button>
Finally getting into code, trying to get out of powerpoint ...
S: "How do I get out of this fullscreen?.."
Dev: "Hit escape"
S:"No..um.."
<keeps trying to click on 'something'>
S:"I see visual studio, but its not on the big screen... "
<keeps click on 'something', no one is sure whats going on>
Dev: "Hit Escape to stop the slideshow"
<finally hits escape, then able to put Visual Studio on the big screen>
S: "Ahh...there, I figured it out."
Speaker had no end of making wild/random statements like:
".Net Core is the future of Microsoft, if you're using .Net 4.5...forget it, its not even supported anymore."
"When I was at Microsoft Build, I asked them why not put all the required .Net assemblies in one directory. Looks like with .Net Core, they listened to me" (he was serious)
"I don't use SQL Server Mgmt Studio. Its free and it sucks. I use <insert a very expensive SSMS clone>, its great, you guys should check it out", then proceeds to struggle to open a query window to write some SQL.
"When you use .Net Core and EntityFramework, you have to write your own stored procedures. If a developer can't write stored procedures, he shouldn't be in this business."
I was on the edge of my seat, hungry for the next crazy bat-shit thing to come out of his mouth. He did not disappoint. BEST MEETUP EVER!9 -
My team are the best coworkers I've had. Admittedly I'm only 4 years into my professional career, but my team makes me stay with my current job.
My team do a lot of silly things to keep everyone in a good mood, and stress free. This week we've had a game where in a quote moment you just yell the name of a primitive type (like BOOL). Why? No idea, but we're enjoying it.
We also have a chicken hat that we named Barry. He sits with people on their desk to do code reviews and such. When people leave they get their own Barry to take with them to their new job. We introduce people to him as a regular member of the team.
Sometimes work sucks. Being a developer can be hard, and can be stressful. Working with this team makes it worth it. -
So there's a recent rant, about making a website work for IE.
I get it, you don't want to make it work for IE because you don't use IE.
But get this: you're not doing the site FOR YOU. You're doing it for the intended user, which is a lot of users that use all kinds of shit. If you don't want to do that, get the fuck out of web development, or from development overall. It's not for you.
I remember when I started my career, I had to make a web app that was intended to be used by, say, 100 people. As a developer I had the best tools for that - cool new 19" monitors, good GPU able to spit out a humongous resolution, and I designed that portal to look great. You know what my superior did then? He took away my 19" monitor and gave me a 14" monitor instead, saying that I became a spoiled brat that totally ignored the customer. I was angry at that, but immediately realized that he was completely right.
It doesn't matter! that it works on your machine. Who the fuck cares about your machine?
Does the software work for the intended user? If not, then you're a shitty developer.22 -
I had been a "hobby" programmer for well over a decade, with my primary career being in repair or a "technician". I had taught myself dozens of languages because it was fun, but never really accomplished much.
I was laid off from my job as a technician and I found myself listless and without purpose. I started doing development again on random things to pass the time and I ended up volunteering as a developer for a game I had played for years.
At the same time I had an uncle who encouraged me to consider software as a career. These two things gave me the confidence to apply for a local software job I saw on Indeed.
They called me pretty quickly, and I was brutally honest. "No, I don't have a degree. I'm self-taught. I have no professional experience really."
I got a proficiency exam anyway and I took it - apparently doing well enough on it that the CTO called me a week later. We had a long talk and I finally asked him why he called me.
He told me that while a degree means something, the passion to learn this job means more to him. It was a month before I was offered the position, and I graciously accepted it.
We had a call about my compensation before starting. It was rather low, but we both agreed that my skill level was quite an unknown.
A year later and my pay was bumped up a sizable amount. My skills are defined now and growing rapidly as new challenges are sent my way. I went from a naive hobbyist to a professional in a short period of time.
I realized that I was always a professional. I had a desire to learn and a desire to do things the right way. I may not have known what to call things. I didn't know some of the design patterns I had used over the years were standards that had names and meaning.
I basically work two jobs now. My full-time job and also on the game that helped propel my career forward and gave me the confidence to reach for it.
As for my hobby? I turned to electronics and the maker community. It's a nice marriage with my programming skill set, and I never knew how rewarding a blinking LED would be. :)4 -
Impostor Syndrome at it's finest.
Any experienced developer knows writing good programs has very little to do with syntax and a whole lot to do with where you put it. If this guy actually did any work over his career he probably knows a ton about application architecture and design patterns without even realizing it.
source: https://quora.com/I-have-been-worki...2 -
I was in college studying stuff I couldn't care less about and had a job that was consuming me. A couple of colleagues and I then decided to open our own company. Four years of sleepless nights later, all colleagues left. I had lost touch with family and friends, had lost a girlfriend and had been left with all the company's debt to pay. Going back to my old career seemed like the only option, but I couldn't let me sabotage myself again. I sat my butt in front of my sister's computer and downloaded every coding class I could get my hands on. Getting used to sleep deprivation helped. Eventually I built my first app and landed my first freelance job. All hat in hand, I told this company I didn't have much experience and they told me they'd hire a senior developer as well. It was on a Sunday morning, at 4am, with the deadline breathing down our necks, that the senior developer had jumped ship and the company asked me if I could take over the project. That moment I realised it's all about being competent. That moment I knew I could do this.5
-
Met a Project Manager (at a friend's party) who had transitioned to a PM role from a developer role (most probably he wrote shitty code)
Smartass PM to me (after I told I code for living) : I really pity poor programmers and I feel sorry for them, the work they do, the effort they put in l, it's just now worth it
Me : yes you are right if we don't code PM are just not worth it, I understand it's a skill to talk about deadlines and features and what not, but the Pre-requisite is that some one would code it first. Also coding is not that anyone can do, I do it because I enjoy it, I m just not meant for superficial talks and I love building things, that's y I do it..
Smartass PM : (dumbstuck)
After half an hr of bullshit conversation...smartass PM has realized it by now that in Silicon Valley (where we live) it's much cooler to be a developer than being a PM (he has recently moved from east coast)...
PM to me : I just live on stack-overflow
Me thinking : Really !!
People should not compare their career paths, every one has their interest and personality -
I'm leaving my job.
That had already been decided when I learned that the only other front end guy at the company put in his two weeks notice. I immediately decided that I was morally obligated to put in my 4 months notice to give the company enough time to find a replacement (because, contrary to the beliefs of some programmers, front end plays a critical role in web dev).
With only 2 weeks left, I was put on his project to do some "simple design work".
Jesus christ in heaven alive and dead...
I've never in my career seen CSS with such an intense level of specificity -- nobody on that team should have ever let that code get so out of control.
I've spent the past week cursing, walking out of the room, whispering "I can't believe you've done this", ranting to non-developer friends.
Here's an example: the application has a panel used all over the place with a header and a body. Every Single View has it's own duplicated panel, each with its own unique class names and CSS. And that's just one element.
Every view has hundreds of lines of duplicated CSS. Every button, link, list, all with unique styles.
To any junior developer reading this, please hear me: Write one block of CSS for any element that will be reused. DO NOT duplicate your code when it can be used over and over.
/rant4 -
few years back,I wanted to be become supercar designer or weapon designer.
Due low grade in 12th.I got admission in computer science instead of mechanical.
c was introduced in 1st sem.
Score well in first year.
college offer me to change my field cs -> mechanical
4 year later (now)
2 drop's
1) due to health
2) financial issues
happy to be full stack developer.
still like cars and weapons but choosed cs as my real career.16 -
Early in my database developer career, I started a new job at a mortgage company. I was poking around the code, just getting familiar with things.
One script identified properties in certain states/territories for special handling:
AND STATECD IN (‘PR’, ‘HI’, ‘AL’)
I thought “Puerto Rico, Hawaii, and ALABAMA?? One of these things is not like the other…”
Yeah, that was supposed to be Alaska (AK)… But they’ve been special-handling properties in Alabama for years. -
For the first time in my career as a developer I remembered the tarball command line options without looking them up5
-
Today is my 1st week studying laravel via laracast. I had fun playing with php artisan 😂
Btw I'm an Android developer, and
I'm planning to shift career because my company can't get any mobile projects 😥17 -
Favorite/most hated language? (I love a good flame war)
Why did you quit your previous job / Moment you've considered quitting your current job?
Why do you think Linux is so much better than OSX? (Ahh yes I feed on apple flavored hipster tears)
What side project are you currently working on?
If you had the best teams and unlimited funds, to be used only on a serious project using both Blockchain, IoT and AI, what would you create?
If you forgot how to code, what other career would you pursue?
What is your "I was so busy wondering if I could, that I forgot whether I should" concept/idea/project?
How many chicken eggs would fit inside the moon if it was hollow? (I like retarded interview questions)
If you started a startup, what unique perk would you offer your developer employees?
Do you under- or overengineer?
Most unnecessary feature you ever had to create?
Most necessary feature your boss/client denied to approve?15 -
I'm so close to giving up. Yesterday, I travelled 4 hours in one direction for a job interview for a graduate position as a web developer. As I arrived at the interview, I was welcomed by a senior dev and one of the HR people.
I sit down and they start explaining how everything will commence(standard procedure stuff) and afterwards hand me the technical test. At this time I am super calm cause I did my homework, checked out their products, their websites and knew right away what I was going to work on. As I turn the page, I see at the top with huge fucking capital letters "JAVA OOP test".
I take a minute and look back at them, like wtf is happening. Turns out that they are looking for a java dev. They picked me for the role because I had literally 1 fucking sentence in my CV and where I have said that I studied java in one semester of uni. FYI my entire portfolio, cv and cover letter are focused on JS, html, css both for client and server side.
As the fucking HR guy stood there and asked me "is there something wrong", I felt broken inside. For the first time in my fucking life I felt like I was done and couldn't continue anymore. I felt like this is some bitch-slap from karma about something but I still can't figure out what. I just walked out of there being unable to realize what happened.
I just feel like I should end my developer career before it has even started, just go do business analysis or something. Why the fuck would someone put a job description entirely talking about Angular, Less/SASS, bootstrap and jQuery and then say that is a Java dev OOP role. Who the fuck allows those people to take good salaries yet still deliver the up most shittiest quality service.
Before the interview, I checked out their websites which are simply horrendous with the comparability of a fucking baked potato. Idk really what to do, I don't mean to sound as a whiny little b.... but as I walked out of their office, I felt broken inside. Sorry for the long rant.8 -
!rant
I took the job! I finally turned my hobby into a career! Super excited to start November 1st as a Junior Full Stack Developer!4 -
(Best read while listening to AEnima by Tool, loudly)
Dear Current Workplace,
Fuck you, for the reasons enumerated below.
Fuck your enterprise grey blue offices, the stifling warm air of a hundreds of bodies and sub par "development laptops".
Fuck your shitty carbonated water machines which were a cost saving measure over decent drinkable water.
Fuck your fake "flexi time", "you can do home office whenever you want" bullshit. You're still inviting me to mandatory meetings at 09:00 regularly.
Fuck your shitty, in house, third part IT provider sister company. They're the worst of all worlds. If it was in company, we'd get to give out to them, if it was an external company we'd fire them. And yes, when I quit I will quote the dumpster fire that is our corporate VPN as a major factor.
Fuck your cheery, bland, enterprise communication. Words coming under the corporate letterhead seem to lose all association with meaning. Agile, communication, open are things you write and profess to respect, but it seems your totally lack understanding of their meaning.
Fuck your client driven development. Sometime you actually have to fix the foundations before you can actually add new features. And fuck you management who keep on asking "why are there so many bugs and why is it always taking longer to deliver new releases". Because of you, you fucknuts, Because you can't say "NO" to the customer. Because you never listen to your own experienced developers.
Fuck your bullshit "code quality is important to us" line. If it's so important, then let us fix the heap of shit you're selling so that it works like a quasi functional program.
Fuck you development environment which has 250 projects in a single VS solution. Which takes 5mins plus to compile on a quad core i7 with 32 gb of ram.
Fuck this bullshit ball of mud "architecture". I spend most of my time trying to figure out where the logic should go and the rest of the time writing converters between different components. All because 7 years ago some idiot "architect" made a decision that they didn't have to live with.
Actually, fuck that guy in particular. Yeah, that guy who was the responsible architect for the project for 4 years and not once opened the solution to look a the code.
Fuck the manual testing of every business process. Manual setup of the entities takes 10mins plus and then when you run, boom either no message or some bullshit error code.
Fuck the antiquated technology choices which cause loads of bugs and slow down development. Fuck you for forcing me to do manual tests of another developers code at 20:00 on a Friday night because we can't get our act together to do this automatically.
Fuck you for making sure it's very clear I'm never going to be anything but a code monkey in this structure. Managers are brought in from outside.
Fuck you for being surprised that it's hard to hire competent developers in this second rate, overpriced town. It's hard to hire anywhere but this bland shithole would have anyone with half a clue running away at top speed.
Fuck you for valuing long hours and loyalty over actual performance. That one guy who everyone hated and was totally incompetent couldn't even get himself fired. He had to quit.
Fuck you for your mediocrity.
Fuck you for being the only employer for my skill-set in the region; paying just well enough that changing jobs locally doesn't make sense, but badly enough that it's difficult to move.
Fuck you for being the stable "safe" option so that any move is "risky".
Fuck your mediocrity.
Fuck you for being something I think about when I'm not at work. Not only is it shit from 9 to 5 you manage to suck the joy out of everything else in my life as well?
Fuck you for making me feel like a worse developer every day I work here. Fuck you for making every day feel like a personal and professional failure. Fuck you for making me seriously leave a career I love for something, anything else.
Fuck you for making the most I can hope for when I get up in the morning is to just make it until the night.6 -
For some reason the office I work for is paying for a designer to become a front end developer and she gets to take the classes one work time. Any time I want to further my career or pay I have to pay out of pocket and it can't interfere with work. Additionally I have to deal with her asking me every other day why I use Sublime over something else.
Basically I use Sublime because I spent too much time researching new things to try and learn yet another editor. If you wanna use brackets, cool, if you wanna use atom, cool, if you wanna use notepad, cool. I don't give a flying fuck what editor you use, you're writing CSS, I'm writing PHP, if you can count to 4 spaces, and not look at my code, I'm not going to scream at you.
She comes in each day and sits at her desk watching video after video on beginner HTML and CSS asking me mundane questions breaking my concentration at least once an hour.
I know we all started somewhere but Google was my best friend and should be yours as well.7 -
I've lost my gf (she said she wouldn't want to be with a programmer, I said 'sure, bye') and found a much better and more fun career path than I had before.
Otherwise my life stayed pretty much intact, except for the fckn compile time errors and occasional 'fix my electronic device' or 'hack this social media account for me' requests. In retrospect it was more than worth it, would switch to be a professional developer anytime again.11 -
Job title: "Junior Application Developer"
Rest of job description: "4 years experience...Career level: Experienced hire/Professional"
Meaning: "Looking for a senior level programmer willing to work for a junior salary."
I hate job hunting.2 -
this is how I destroyed my career in IT and how I'm headed to a bleak future.
I've spent the last 10 years working at a small company developing a web platform. I was the first developer, I covered many roles.
I worked like crazy, often overtime. I hired junior dev, people left and came. We were a small team.
I was able to keep the boat afloat for many years, solving all the technical problems we had. I was adding value to the company, sure, but not to mine professional career.
There was a lot of pressure from young developers, from CEO, from investors. Latent disagreement between the COO and the CEO. I was in between.
Somehow, the trust I built in 10 years, helping people and working hard, was lost.
There was a merge, development was outsourced, the small team I hired was kept for maintenance and I was fired, without obvious explanations.Well, I was the oldest and the most expensive.
Now I'm 53, almost one year unemployed.
I'm a developer at heart, but obsolete. The thing we were doing,
were very naif. I tried to introduce many modern and more sophisticated software concepts. But basically it was still pure java with some jquery. No framework. No persistency layer, no api, no frontend framework. It just worked.
I moved everything to AWS in attempt to use more modern stack, and improving our deployment workflow.
Yes, but I'm no devop. While I know about CD/CI, I didn't set up one.
I know a lot of architectural concepts, but I'm not a solution architect.
I tried to explain to the team agile. But I'm not a scrum master.
I introduced backlog management, story mapping, etc. But I'm not a product manager.
And before that? I led a team once, for one year, part of a bigger project. I can create roadmap, presentations, planning, reports.
But I'm not a project manager.
I worked a lot freelancing.
Now I'll be useless at freelancing. Yes I understand Angular, react, Spring etc, I'm studying a lot. But 0 years of experience.
As a developer, I'm basically a junior developer.
I can't easily "downgrade" my career. I wish. I'll take a smaller salary. I'll be happy as junior dev, I've a lot to learn.
But they'll think I'm overqualified, that I'll leave, so they won't hire me even for senior dev. Or that I won't fit in a 25 y.o. team.
My leadership is more by "example", servant leader or something like that. I build trust when I work with somebody, not during a job interview.
On top of that, due to having worked in many foreign countries, and freelancing, my "pension plan" I won't be able to collect anything. I've just some money saved for one year or so.
I'm 53, unemployed. In few years time, if I don't find anything, it will be even harder to be employed.
I think I'm fucked25 -
Dropped out after 4 months at Uni when I realised that I will learn absolutely nothing useful for my future career. We were either learning HTML/CSS or coding calculators in C# . At this point I was already writing my own PHP CMSs with huge databases for real life clients. I guess I can only blame my course level and maybe I could go someplace else but it probably wouldn't be so much different.
A month after I dropped out I got my first job as a junior Drupal developer. That was 7 years ago, now I'm a FrontEnd dev in a really great environment and throughout the years no one looked at my grades or even asked for them.
Experience and passion as as valuable if not more as your education.5 -
TLDR: SAP sucks. Don't ever work with it. Run away from it. Delete it from your memory. If your company works with it, quit. It's the best you can do.
A couple of weeks ago the group rant was "Story of your best/worst career choice" and I talked about the contract I signed. Even tho that is still true and I still feel like that, I think I got a new worst choice:
WORKING WITH SAP.
When I got this job I knew it would be SAP, but I didn't know what SAP was. I just thought "it's programming, how bad can it be?" OH BOII.
If only I would have done some FUCKING RESEARCH I would know this would be a mistake!!
And I knew I didn't want to work with this, I knew I wanted to be a web developer, but I STILL ACCEPTED THE JOB OH MAN WHAT WAS I THINKING I'M SO MAD.
Were I live we all have the same mentality when looking for the first job, which is to just accept anything you can get, because it's your first job, you need to work and to get experience, even if it's a bad job or if you know you won't like it. When my intership was ending, I told my parents I didn't want to stay there because they treat their employes like shit, and the salary is terrible. They told me to still accept it if they offered because I still need a job (this one was web tho) and experience.
So, of course, since I was looking for my first job, was told this my entire live, always thought like that and they were the first to contact me, I accepted it.
BIGGEST FUCKING MISTAKE!! DON'T THINK LIKE THIS!! AND STOP TELLING KIDS THIS!! IT'S NOT A GOOD MENTALITY!!!
ALSO DON'T WORK WITH SAP! EVER!24 -
Works as backend developer for 2 years now; Almost fails simple university algorithm course.
I'm contemplating my whole life and career choice right about now.2 -
In the Ruhr area (Germany) we have some very old, very strange words with strange meanings. One of those words is ‚Prutscher‘.
A Prutscher refers to a person who does things but never gets a good result, due to lack of knowledge or simple carelessness. Most of the time, Prutschers are people who are interested in certain subjects and often work in the related jobs, but who lack the motivation to properly train themselves, learn what there is to learn and to always keep up with their technologies .
Here are a few examples I've stumbled upon so far in my career:
- Developers in their 60's who read a book about PHP 25 years ago and decided to become a software developer. Since then haven't read anything about it. Who then now build huge spaghetti monoliths for large companies, in which they prefix every function, every variable and constant with their initials and, of course, use Hungarian notation.
- People who read half a fucking tutorial about <insert any fancy js framework here> and start blogging/tweeting about it
- Senior web developers who need to be told what the fuck CORS is and who can't even recognize CORS related errors in their browser console.
- People who have done nothing else for 18 years than building websites for companies on Wordpress 1.x and writing few lines of PHP and Javascript from time to time. Those who are now applying as a frontend dev due to the difficult economic situation and are surprised that they are not accepted due to a lack of experience.
- Developers who are the only ones working on Windows in the team and ask their Linux colleagues for help when Windows starts bitchin.
- People who have been coding for 30 years, have worked with ~42 languages and don't know the difference between compiled and interpreted languages in the job interview.
- Chief developers at a large newsletter-publisher who think it's a good idea to build your own CMS (due to a lack of good existing ones, of course).
- Developers who have been writing PHP applications for multinational corporations for 25 years and cannot explain how PHP is executed. They don't even know what the fucking OPcache is, let alone fpm. FML
- People who call themselves professional developers but never ever heard of DRY, KISS, boy-scout rule, 12-Factor App, SOLID, Clean Code, Design Patterns, ...
- Senior developers wondering why the bash script won't run on their fucking Windows machine.
- Developers who consider Typescript to be a hindrance and see no value in it.
- Developers using ftp for deployments in 2022
- Senior Javascript Developer applying for a job and for whom Integer is a primitive data type in JS.
- Developers who prefer to code without frameworks and libraries because they are only an unnecessary burden/overhead and you can quickly code everything up yourself.
- Developers who think configuring their server(s) manually is a good idea.
You fucking Prutscher. What you have already cost me in terms of work and nerves. I can't even put it into words how deeply I despise you. I have more respect for the chewing gum that has been stuck in my damn trash can for the past 3 years than I do for you guys. You are the disgrace of our profession. I will haunt you in your dreams and prefix every fucking synapse of your brain with MY initials.
As a well-known german band once sang in a very fitting song: I wouldn't even piss on you if you were on fire.
If you recognized yourself in one of the examples here: FUCK YOU!29 -
!rant, advice, !mine
Q: I'm [xx] years old [xyz] professional. Would that be a good idea if I try to change my career to software development right now?
A: Age is mostly doesn't matter. You can learn programming at any age. And, software is everywhere. Every background knowledge will be useful. Your prior knowledge will not be wasted.
But, should you change career?
- YES, if you deeply interested in programming.
- NO, if it's only because you feel there are better opportunities.
It's true that there may be better opportunities. But, without deep interest in the subject, you may struggle to become good software developer. Without being a good developer, your opportunities will be limited and you are likely to regret the decision.
Software development is easier for those who passionate but very difficult for those who doesn't....4 -
!dev (Please, don't take this very seriously, I'm kind of burnt out)
I'm not having a good time.
I can't even write a post to properly explain how I feel.
I feel disappointed by life and by myself in many levels. Life is disappointing. I am disappointing too.
I'm having issues to focus, can't even write a couple of lines of code.
Time to listen to some emo lofi and write about how much I hate myself.
I wished I didn't feel these feelings.
I wished I didn't regret so many things I did or didn't do.
I wished I could fucking understand everything I read, but I don't, everything I read is gibberish, every paragraph makes me feel like I'm drifting in a storm.
I wished I was happy with my career, with my job. I wished I had a true friend.
I wished I could finish one goddamn fucking project for once.
I wished there was something that made me unique, but I don't think there's any.
I just feel like an ant, and that I don't really matter.
I don't feel like I'm someone at all, I feel like I'm experiencing a dream, and a rather boring one.
Programming used to be challenging and fun for me, but it has become this dull and stressful ordeal.
The internet has shown me that I don't matter really. I remember being a little kid and believing that the internet would not discriminate you, that right from the comfort of your house you could connect to people and be cared for, and collaborate in something.
But every year that passes I see that I was wrong. I have tried to put in time into people, I have asked people how they're doing, I have cared for their projects. But there's no reciprocation.
The internet itself has become a thing where the big fish only matters. The top 1k users will get 99% of the attention.
Fuck nurture, rule competition.
What's the point of creating a github project that you think it's cool? No one will give two shits about it, it won't make a goddamn difference whether you push it or not.
You know what fucking matters? If you're an apple or google developer and have thousands of followers.
Bla, bla, bla, I'm depressed...9 -
I'm kind of disgruntled that I've only worked with one ninja level developer in my career (small market) and he was an insane dick. Despite my hatred, I treated him kindly and respected him. I wanted to learn from him but he didn't want to teach.
Ninja devs, don't be that guy.6 -
As a developer, I constantly feel like I'm lagging behind.
Long rant incoming.
Whenever I join a new company or team, I always feel like I'm the worst developer there. No matter how much studying I do, it never seems to be enough.
Feeling inadequate is nothing new for me, I've been struggling with a severe inferiority complex for most of my life. But starting a career as a developer launched that shit into overdrive.
About 10 years ago, I started my college education as a developer. At first things were fine, I felt equal to my peers. It lasted about a day or two, until I saw a guy working on a website in notepad. Nothing too special of course, but back then as a guy whose scripting experience did not go much farther than modifying some .ini files, it blew my mind. It went downhill from there.
What followed were several stressful, yet strangely enjoyable, years in college where I constantly felt like I was lagging behind, even though my grades were acceptable. On top of college stress, I had a number of setbacks, including the fallout of divorcing parents, childhood pets, family and friends dying, little to no money coming in and my mother being in a coma for a few weeks. She's fine now, thankfully.
Through hard work, a bit of luck, and a girlfriend who helped me to study, I managed to graduate college in 2012 and found a starter job as an Asp.Net developer.
My knowledge on the topic was limited, but it was a good learning experience, I had a good mentor and some great colleagues. To teach myself, I launched a programming tutorial channel. All in all, life was good. I had a steady income, a relationship that was already going for a few years, some good friends and I was learning a lot.
Then, 3 months in, I got diagnosed with cancer.
This ruined pretty much everything I had built up so far. I spend the next 6 months in a hospital, going through very rough chemo.
When I got back to working again, my previous Asp.Net position had been (understandably) given to another colleague. While I was grateful to the company that I could come back after such a long absence, the only position available was that of a junior database manager. Not something I studied for and not something I wanted to do each day neither.
Because I was grateful for the company's support, I kept working there for another 12 - 18 months. It didn't go well. The number of times I was able to do C# jobs can be counted on both hands, while new hires got the assignments, I regularly begged my PM for.
On top of that, the stress and anxiety that going through cancer brings comes AFTER the treatment. During the treatment, the only important things were surviving and spending my potentially last days as best as I could. Those months working was spent mostly living in fear and having to come to terms with the fact that my own body tried to kill me. It caused me severe anger issues which in time cost me my relationship and some friendships.
Keeping up to date was hard in these times. I was not honing my developer skills and studying was not something I'd regularly do. 'Why spend all this time working if tomorrow the cancer might come back?'
After much soul-searching, I quit that job and pursued a career in consultancy. At first things went well. There was not a lot to do so I could do a lot of self-study. A month went by like that. Then another. Then about 4 months into the new job, still no work was there to be done. My motivation quickly dwindled.
To recuperate the costs, the company had me do shit jobs which had little to nothing to do with coding like creating labels or writing blogs. Zero coding experience required. Although I was getting a lot of self-study done, my amount of field experience remained pretty much zip.
My prayers asking for work must have been heard because suddenly the sales department started finding clients for me. Unfortunately, as salespeople do, they looked only at my theoretical years of experience, most of which were spent in a hospital or not doing .Net related tasks.
Ka-ching. Here's a developer with four years of experience. Have fun.
Those jobs never went well. My lack of experience was always an issue, no matter how many times I told the salespeople not to exaggerate my experience. In the end, I ended up resigning there too.
After all the issues a consultancy job brings, I went out to find a job I actually wanted to do. I found a .Net job in an area little traffic. I even warned them during my intake that my experience was limited, and I did my very best every day that I worked here.
It didn't help. I still feel like the worst developer on the team, even superseded by someone who took photography in college. Now on Monday, they want me to come in earlier for a talk.
Should I just quit being a developer? I really want to make this work, but it seems like every turn I take, every choice I make, stuff just won't improve. Any suggestions on how I can get out of this psychological hell?6 -
I spent over a decade of my life working with Ada. I've spent almost the same amount of time working with C# and VisualBasic. And I've spent almost six years now with F#. I consider all of these great languages for various reasons, each with their respective problems. As these are mostly mature languages some of the problems were only knowable in hindsight. But Ada was always sort of my baby. I don't really mind extra typing, as at least what I do, reading happens much more than writing, and tab completion has most things only being 3-4 key presses irl. But I'm no zealot, and have been fully aware of deficiencies in the language, just like any language would have. I've had similar feelings of all languages I've worked with, and the .NET/C#/VB/F# guys are excellent with taking suggestions and feedback.
This is not the case with Ada, and this will be my story, since I've no longer decided anonymity is necessary.
First few years learning the language I did what anyone does: you write shit that already exists just to learn. Kept refining it over time, sometimes needing to do entire rewrites. Eventually a few of these wound up being good. Not novel, just good stuff that already existed. Outperforming the leading Ada company in benchmarks kind of good. At the time I was really gung-ho about the language. Would have loved to make Ada development a career. Eventually build up enough of this, as well as a working, but very bad performing compiler, and decide to try to apply for a job at this company. I wasn't worried about the quality of the compiler, as anyone who's seriously worked with Ada knows, the language is remarkably complex with some bizarre rules in dark corners, so a compiler which passes the standards test indicates a very intimate knowledge of the language few can attest to.
I get told they didn't think I would be a good fit for the job, and that they didn't think I should be doing development.
A few months of rapid cycling between hatred and self loathing passes, and then a suicide attempt. I've got past problems which contributed more so than the actual job denial.
So I get better and start working even harder on my shit. Get the performance of my stuff up even better. Don't bother even trying to fix up the compiler, and start researching about text parsing. Do tons of small programs to test things, and wind up learning a lot. I'm starting to notice a lot of languages really surpassing Ada in _quality of life_, with things package managers and repositories for those, as well as social media presence and exhaustive tutorials from the community.
At the time I didn't really get programming language specific package managers (I do now), but I still brought this up to the community. Don't do that. They don't like new ideas. Odd for a language which at the time was so innovative. But social media presence did eventually happen with a Twitter account that is most definitely run by a specific Ada company masquerading as a general Ada advocate. It did occasionally draw interest to neat things from the community, so that's cool.
Since I've been using both VisualStudio and an IDE this Ada company provides, I saw a very jarring quality difference over the years. I'm not gonna say VS is perfect, it's not. But this piece of shit made VS look like a polished streamlined bug free race car designed by expert UX people. It. Was. Bad. Very little features, with little added over the years. Fast forwarding several years, I can find about ten bugs in five minutes each update, and I can't find bugs in the video games I play, so I'm no bug finder. It's just that bad. This from a company providing software for "highly reliable systems"...
So I decide to take a crack at writing an editor extension for VS Code, which I had never even used. It actually went well, and as of this writing it has over 24k downloads, and I've received some great comments from some people over on Twitter about how detailed the highlighting is. Plenty of bespoke advertising the entire time in development, of course.
Never a single word from the community about me.
Around this time I had also started a YouTube channel to provide educational content about the language, since there's very little, except large textbooks which aren't right for everyone. Now keep in mind I had written a compiler which at least was passing the language standards test, so I definitely know the language very well. This is a standard the programmers at these companies will admit very few people understand. YouTube channel met with hate from the community, and overwhelming thanks from newcomers. Never a shout out from the "community" Twitter account. The hate went as far as things like how nothing I say should be listened to because I'm a degenerate Irishman, to things like how the world would have been a better place if I was successful in killing myself (I don't talk much about my mental illness, but it shows up).
I'm strictly a .NET developer now. All code ported.5 -
What do you wanna become? / What are you?
1. PHP Developer
2. Python Developer
3. Node.Js Developer
4. JavaScript Developer
5. Java Developer
6. Android Developer
7. Other (please mention in comment)64 -
Just want to share that in August I'll be starting my career as a developer, something which I'm super nervous and excited about.
I just finished my bachelor degree, and will be starting mid-August. I've been moderately interested in the concept of programming since I was 14, but I initially didn't think I had what it took to make it my profession ("Programmers need to be good at math and that sort of stuff, right?") So I studied electronics and started at the same place where I finished my apprenticeship, working IT support. Eventually, I found myself not fully pleased with how things had turned out and quit my job to get a bachelor degree. And now, having graduated a few days ago, I'm very excited to see what my future as a developer will bring. I'm stoked and nervous at the same time, and I just wanted to share this with someone.
During my time as a student, I've been so lucky as to have discovered the world of JavaScript/Node.js/React in addition to all the standard Java-centric curriculum they taught at school, and I think that's an area I hope to explore more in the coming future.4 -
If you ever feel like you won't achieve anything in your developer career just remember that Suicide Squad won an Oscar.1
-
Why management people thinks that a career path for any senior developer is to be a "leader" and be good in business side. Its like saying "hey you are a good programmer, let me take away that work you love to do and do stupid human resource management instead"5
-
They probably should have made me sign a NDA, but I never did.
I was a wee little front-end devloper for a really small dev shop. The lead devloper, who was also the only back-end developer decided to quit. The company was in the middle of a huge project with Rolls-Royce aerospace. I managed to learn ColdFusion and release the application in only a few months. It was basically a giant warranty management application for jet engines. This is one app I wish I can go back and redo because if I had the expierence then that I do now... I feel like it would be so much better. That application allowed me to advance in my career, and 5 years later, I'm working for one of the largest development companies. -
Being me. Fresh out of UNI with a three year bachelor in CS, no work experience. Starts in a big tech company with a lot promise of exciting project etc. Starts in 3 projects with one lead dev and two senior devs.
First month begins. I start by setting up my local environment and read documentations, which is fairly irrelevant and old. One of the senior devs quits.
Second month begins. Lead dev quits as well and the other senior dev having sick leave for the rest of the month. Basically I'm on my own, but thankfully not responsible for the projects.
Third month begins. The other senior dev is still sick. Nobody to help. Now I'm forced to talk to customer with a lacking knowledge of projects. Nobody knows what is going on. Hopefully my other senior dev will come back.
Fourth month begins. My senior have quit as well. I've been assigned as responsible of all three projects now. FML.
Fifth month begins. I begged my manager for help. Got a junior dev to help me with one of the projects. He and I still have no clue what we should do.
What a shitty start to a career as a developer.
Anybody having a similar experience?5 -
The best mentors I had were the people at the company where I started working.
I was doing my master thesis, bored like hell writing about someone else's idea. I decided to drop out and do a 10 week apprenticeship at this company. They had been my mentors in a university project and thought it would be nice to see what I could learn from them. I wasn't wrong.
During that time they taught me Ruby, JavaScript, Angular, Node and Git. They taught me about coding standards and how to write better, more maintainable code. They inspired me to keep learning and also to share my knowledge. In the end I didn't stay there, but they helped me get my first real job.
If it weren't for those 10 weeks my career would have been a lot different. I wouldn't be the developer I am today without them and I'm forever grateful.1 -
Coding has given me the ability to turn my favorite hobby into a career. This in turn gave me the chance to take jobs in three countries so far (US, Germany, UK). So, I can explore the world with lovely wife while doing something I'm really passionate about and constantly learning. It also allows me to relate more to my dad, a software engineer of about 30 years who got me started when I was a kid.
In short, coding changed everything for me.
PS: I met my wife in intro to CS, though she's not a developer. -
"Writing good code is a charity". ( - saves time, effort, mental-health, & career of next developer).5
-
This happened when I finished highschool.
I was looking for a programming related career at university, and I had two options: Computer systems engineering or Software engineering. I commented this to my mom.
Me: Mom, this university offers Software engineering. The thing is that the campus is 1 hour from the city and it’s a new career, so I don’t know if it’s a good idea or not.
Mom: Why Software engineering? Don’t you want to be a developer?
Me: Yes, that’s why I was thinking of taking Software engineering
...
Mom: Is not “Software” what is inside the computer? (Inside the chasis on desktop computers)
I started laughing so hard 😂 and, of course, I ran away4 -
Well in America, developer is the current "hot" career if you wanna make bank and rightly so, you can make a great salary. However the "business types" politicize the position since it's trendy right now and do all sorts of undesirable things like looking for "10x" or "rockstar" devs, etc. It's really just an excuse to have you on call 24/7. Some jobs, you go home, but you never really clock out of work. Well, if you even make it home; you could end up always travelling for your work.
But at least it's a romanticized and well paid position, unlike system admin, who may work the same hours but will never have the "cool" job.6 -
One of my colleagues held a very short, literally 5 minutes, interview today. The candidate was looking for an android developer position.
Me: Done already?😕
C: Yep. Had enough.
Me: How come?
C: I asked him if he has any apps on the store? No. Any public git? No. Any apk? No.
C: Ok what experience do you have?
Dude: I worked on a app similar to imdb 4 years ago. I made a page for it.
C: *Page* *triggered* *internal screaming* 😂
C: Ok and since then?
Dude: Nothing.
C; Ok, we'll call you.
Best ot luck in your android dev career mate. Never gonna hear from us.
How can you come to an interview and be so unprepared. Was he delosutional or something?😕2 -
My developer career has ended before I even start. After failing to get a job, I have started a business men services company. Maybe in the future, I will include software development to the business. So no more rants from my side at least for one year.
Fuck you all fucking retarded companies who wants junior developers with the same experience of senior developers.6 -
So I joined this financial institution back in Nov. Selling themselves as looking for a developer to code micro-services for a Spring based project and deploying on Cloud. I packed my stuff, drove and moved to the big city 3500 km away. New start in life I thought!
Turns out that micro-services code is an old outdated 20 year old JBoss code, that was ported over to Spring 10 years ago, then let to rot and fester into a giant undocumented Spaghetti code. Microservices? Forget about that. And whats worse? This code is responsible for processing thousands of transactions every month and is currently deployed in PROD. Now its your responsibility and now you have to get new features complied on the damn thing. Whats even worse? They made 4 replicas of that project with different functionalities and now you're responsible for all. Ma'am, this project needs serious refactoring, if not a total redesign/build. Nope! Not doing this! Now go work at it.
It took me 2-3 months just to wrap my mind around this thing and implement some form of working unit tests. I have to work on all that code base by myself and deliver all by myself! naturally, I was delayed in my delivery but I finally managed to deliver.
Time for relief I thought! I wont be looking at this for a while. So they assign me the next project: Automate environment sync between PROD and QA server that is manually done so far. Easy beans right? And surely enough, the automation process is simple and straightforward...except it isnt! Why? Because I am not allowed access to the user Ids and 3rd party software used in the sync process. Database and Data WareHouse data manipulation part is same story too. I ask for access and I get denied over and over again. I try to think of workarounds and I managed to do two using jenkins pipeline and local scripts. But those processes that need 3rd party software access? I cannot do anything! How am I supposed to automate job schedule import on autosys when I DONT HAVE ACCESS!! But noo! I must think of plan B! There is no plan B! Rather than thinking of workarounds, how about getting your access privileges right and get it right the first time!!
They pay relatively well but damn, you will lose your sanity as a programmer.
God, oh god, please bless me with a better job soon so I can escape this programming hell hole.
I will never work in finance again. I don't recommend it, unless you're on the tail end of your career and you want something stable & don't give a damn about proper software engineering principles anymore.3 -
Aspiring Android developer here transitioning to a new career in programming. Stumbled across this great community! Sup guys! OK now back to some Saturday afternoon coding ✌9
-
Well, I suppose there's no rules against talking about a non-tech company situation.
Before I made it into my career as a developer, I wrote code as a self-learned hobby programmer. I had a job though, which was selling chips. No, not ICs... potato chips. Funny enough, I made a killing doing it.
Anyway, this isn't about me. It's about the guy who quit shortly after I showed up. You see, we all had company trucks and most of us parked them at the warehouse and commuted in our own vehicles. We'd load the trucks up with product and lock them up in the yard for the next day.
It used to be that there was an option to take the truck home, but after this gentleman, that was reserved for special instances.
That would be due to the fact that the guy played "hide the chip truck" and called up to quit his job, forcing my former boss to hunt around an entire city to find the damn thing.
I've found it isn't so different in software, except when people quit, it's more like "hide the actual deployed branch you didn't commit". -
I really like my current job.
I work as an analyst developer looking after and sorting out people's old tech debt.
Once that's stable I get pretty free reign to do what I want.
It allows me to stretch from dev into graphic design, security, architecture and training on a very regular basis.
It allows me to keep an eye on tech trends, research and develop ideas using the latest shiny things.
Oh and if I say I need a thing, I can usually get it purchased.
All of the above comes with the "as long as it's for the benefit of the company" disclaimer, but when your direct managers see an IDE and think "okay he's working" the lines get a little blurry.
They keep asking me about my career goals and if I want to manage or move around. Fuck that noise, all of that noise.
Do wut I wawnt.6 -
Early in my career I saw a specific lead developer being a jerk. I saw it as confidence then. Looking back I realize they were scared and were trying to cover up the fact that they didn’t know what they were doing. Time really does give clarity sometimes.1
-
Why is it what so many developers think that they are the sole genius surrounded by idiots and completely lack in interpersonal skills or the ability to see other people's arguments as valid? Honestly, with some people it's like working with an emotionally stunted teenager. I literally spoke to someone yesterday who thinks it's impossible to come to a compromise or agreement about anything unless there is a third party to arbitrate and mindlessly insists on his own way in literally every disagreement, even after admitting his logic is faulty. It's like watching a spotty 17 year old argue about politics online I swear it.5
-
I grew up on a farm in western KS. My parents bought PCs when I was in grade school. First was a trs80 , then an Epson Equity 1+, where I built a spare key for it, and built levels in willy for my brother to beat. Then a 486 and pentium which I broke often. I ended up working at the same store in college for extra cash. While I'm an adverage developer, I do on and make decent $$. I still help them out with keeping their PCs running, for moms sewing, and dads Linux box. I figure I owe them for their investment in me. They gave me the tools to figure out what I want to do with my career and my life.2
-
Story time!
I moved from React Dev to fullstack like halve a year ago. Three months ago I became project lead and now I will start to become a team lead.
Holy shit I'm growing fast2 -
Any other 30+ year old developer that didn't start the dev career too long ago and gets completely depressed when surfing on Quora? Reading 100 about "developer career being over after 30" when mine started at 29 isn't too good a motivation23
-
I was junior developer. My friend recommended me for JavaScript Senior developer in the company he was working. He had settle the interview without asking me. I knew a little of javascript, but I was not ready for this interview at all and I knew that.
So I went to the interview. The questions were very difficult and complex for me, I answered two question of ~15. I was very upset, I was sweаty and blushed ... one of the most uncomfortable moments in my career.
After the questions, the interviewer decided to give me a MacBook to do an exercise with JavaScript to see me in action. The exercise was easy, but MacBook ... Damn it, I saw a MacBook for the second time in my life. I knew the solution of the task, but I was very slow in implementation because of Mac..
After 15 minutes of slow coding and sweating, the interviewer said "OK, just finish it at home and send the code to my email...".
When I got home, I made the perfect solution for 30 minutes and I sent it to him. The only answer was "ok, tnx" and that guy didn't call me anymore.
This is kind of rejection I think ;)3 -
Boss wants me to become lead developer on a huge project; I still consider myself Junior and feel like there is still more for me to learn before I can even accept something like this. The company is amazing and I would love to step into this role but I fear that I will only disappoint.
What would you do? If I should take it; could you recommend resources that would help me level up?8 -
I rarely tell this story because it's hard to believe and would show me in a bad light if people don't believe its details. I know there have been foolish moves from my part, and more stuff should have been agreed to in writing, and I did step into a legal grey area. However I am pleased with what I did and how it all turned out, and this is as close to the truth as possible without needing to explain too many details.
I was once a team lead in an outsourcing company. We had a flexible payment plan depending on results. That helped me motivate myself and my team. Things worked great.
But then the boss started acting like shit:
1. Flexible payment means minimum, right?
2. Promises are made to be broken, as long as your employees have hope and work overtime for a whole month just to finish an important project before schedule, right?
3. Who needs a good, comfortable, SAFE work environment when you can save 30$ on not buying a new crappy chair in place of the old broken crappy chair, if it can be maintained standing by just a bit of duct tape and careful balancing on it? It's not like that developer who earns 30$ per hour has anything else to think about than balancing on a broken chair, right?
I'm a very calm person at work. I never ever raised my voice at anyone for 10 years of my career. Except this situation. I pulled the boss out of the office so his secretary wouldn't hear what I had to say. I threw this everything into his face.
A guy from sales got out of the office to go to the bathroom, and when he heard me, he carefully snuck back into the office (I didn't see him. He told me this over a beer after he left).
Of course I quit on the spot, convinced most of my team members to leave (wasn't hard, I just had to offer a secure plan, which I did), and helped my team members to get good positions elsewhere, and assisted others in starting their own business, by stealing customers from this company (the asshole did not foresee this when he prepared the labour contracts), after he accused me of plagiarism (that I stole code from somewhere else) and used that excuse to not pay me what we agreed upon.
I didn't want litigation. I just used karma, while remaining in the legal realm.
Within a month after this, more than half of his company was gone, and he was left with only a fraction of the revenue he was making before, since the only ones left were people that did not produce value (sales that had nothing to sell, accounting that had nothing to account, etc.), and just one person maintaining one remaining contract that was bringing barely enough money to sustain half of these people.
Now I want to congratulate you for actually finishing reading this :)1 -
So the other day I randomly checked out a few job postings on some recruiting agency’s website. Didn’t even sign up or anything.
The very next day I get a call from them. The person on the phone tells me they noticed I had visited their website and was wondering if I was interested in applying to any of the offers. Even as a developer I was totally taken aback as to how they managed to track me down based on a single visit.
I believe I ended up on their website by clicking on a link on LinkedIn. I’m assuming it’s via LinkedIn that the managed to get my info (phone etc.). All in all I’m not extremely surprised. But to me it’s downright creepy and it makes me feel like I’m being stalked. Also it makes recruiters look totally desperate and I’m not sure I would want to entrust them with the responsibility of handling my career4 -
So after months of self study my company finally appoints me as a junior developer with a major client as the intermediate dev on the project resigned. My tech lead assures me that junior devs only fix bugs and do other minor changes. One week in and in our first sprint planning session the client decides to priorities a Major update to the app. Now I have 2 weeks to deliver what will either make or break my immediate career. And I have no idea how to implement any of the changes. Stack overflow you're my only hope (and many hrs of YouTube tutorials)3
-
When I was in college OOP was emerging. A lot of the professors were against teaching it as the core. Some younger professors were adamant about it, and also Java fanatics. So after the bell rang, they'd sometimes teach people that wanted to learn it. I stayed after and the professor said that object oriented programming treated things like reality.
My first thought to this was hold up, modeling reality is hard and complicated, why would you want to add that to your programming that's utter madness.
Then he started with a ball example and how some balls in reality are blue, and they can have a bounce action we can express with a method.
My first thought was that this seems a very niche example. It has very little to do with any problems I have yet solved and I felt thinking about it this way would complicate my programs rather than make them simpler.
I looked around the at remnants of my classmates and saw several sitting forward, their eyes lit up and I felt like I was in a cult meeting where the head is trying to make everyone enamored of their personality. Except he wasn't selling himself, he was selling an idea.
I patiently waited it out, wanting there to be something of value in the after the bell lesson. Something I could use to better my own programming ability. It never came.
This same professor would tell us all to read and buy gang of four it would change our lives. It was an expensive hard cover book with a ribbon attached for a bookmark. It was made to look important. I didn't have much money in college but I gave it a shot I bought the book. I remember wrinkling my nose often, reading at it. Feeling like I was still being sold something. But where was the proof. It was all an argument from authority and I didn't think the argument was very good.
I left college thinking the whole thing was silly and would surely go away with time. And then it grew, and grew. It started to be impossible to avoid it. So I'd just use it when I had to and that became more and more often.
I began to doubt myself. Perhaps I was wrong, surely all these people using and loving this paradigm could not be wrong. I took on a 3 year project to dive deep into OOP later in my career. I was already intimately aware of OOP having to have done so much of it. But I caught up on all the latest ideas and practiced them for a the first year. I thought if OOP is so good I should be able to be more productive in years 2 and 3.
It was the most miserable I had ever been as a programmer. Everything took forever to do. There was boilerplate code everywhere. You didn't so much solve problems as stuff abstract ideas that had nothing to do with the problem everywhere and THEN code the actual part of the code that does a task. Even though I was working with an interpreted language they had added a need to compile, for dependency injection. What's next taking the benefit of dynamic typing and forcing typing into it? Oh I see they managed to do that too. At this point why not just use C or C++. It's going to do everything you wanted if you add compiling and typing and do it way faster at run time.
I talked to the client extensively about everything. We both agreed the project was untenable. We moved everything over another 3 years. His business is doing better than ever before now by several metrics. And I can be productive again. My self doubt was over. OOP is a complicated mess that drags down the software industry, little better than snake oil and full of empty promises. Unfortunately it is all some people know.
Now there is a functional movement, a data oriented movement, and things are looking a little brighter. However, no one seems to care for procedural. Functional and procedural are not that different. Functional just tries to put more constraints on the developer. Data oriented is also a lot more sensible, and again pretty close to procedural a lot of the time. It's just odd to me this need to separate from procedural at all. Procedural was very honest. If you're a bad programmer you make bad code. If you're a good programmer you make good code. It seems a lot of this was meant to enforce bad programmers to make good code. I'll tell you what I think though. I think that has never worked. It's just hidden it away in some abstraction and made identifying it harder. Much like the code methodologies themselves do to the code.
Now I'm left with a choice, keep my own business going to work on what I love, shift gears and do what I hate for more money, or pivot careers entirely. I decided after all this to go into data science because what you all are doing to the software industry sickens me. And that's my story. It's one that makes a lot of people defensive or even passive aggressive, to those people I say, try more things. At least then you can be less defensive about your opinion.45 -
The emphasis on "team" to the exclusion of the individual (thanks in no small part to Scrum) is destroying the software developer career. It's a pendulum. There are always team/company goals AND personal goals. However, these days, the rhetoric is ALL about the team: everybody on a team has the same title, get rid of people who don't conform to some "collaborative", "open space", "colocated" ideal, etc. OKRs are entirely about giving everybody the exact same goals. I remember sitting down with managers throughout my career to talk about where I want to be in a year. What skills I wanted to explore. There were no guarantees, but the generally accepted idea was that nurturing the employee helped retain the employee. Now, there is only the idea that every developer should have the same "T-shaped" skillset, that all team members are the same, that all teams are interchangeable, that all developers are nameless cogs. It is demoralizing. If I were to give any advice to those looking to enter the industry as a developer right now, it would be "Don't". Because you will be told that being a "hero" is a bad thing. In what other industry does management tell its producers that they don't want people to go "above and beyond", and that if they do, they won't get credit for it because the credit always belongs to everybody.7
-
I work in a consulting firm.
I started right after graduation. I entered with candy glasses. Thinking is all well and ready to climb the ladder.
I entered as a junior developer.
On my first project, i am constantly belittled by my team lead. To the extent i suffer from ptsd.
On my second project, i am the only dev. I am amaze i manage to handle all the development job by myself for a year. Still i get nasty comments from my boss. Despite i am able to deliver on time.
On my third project. i left due to office politics.
Currently i am in my fourth project. The code is complete mess. The development environment is crappy. It doesn't reflect change right away.
My passion has dried up.
I'm seriously giving thoughts, should i switch career path.12 -
If the Kenya ICT bill will be passed into law, it will soon be illegal to write any code as a developer or engineer or practice any ICT career without a license ($460 per year) or without a college degree 😢8
-
It is said that the number of programmers doubles every five years with fresh CS, CE, and EE grads. Assuming that's true, then at any one time over half the developer community are novices in the early stages of their career.
My entire life's been spent in software and I've been in it now for about 15 years and I've seen a lot of people make alot of things and I've seen a lot of people fail at alot of things. My observation is that the doers are the major thinkers, the people that really create the things that change this industry are both the thinker doer in one person. It's very easy to take credit for the thinking the doing is more concrete. It's very easy for somebody say "oh, I thought of this three years ago" but usually when you dig a little deeper you find that the people that really did it. Were also the people that really worked through the hard intellectual problems.
Many people falsely believe that a great idea constitutes 90% of the work. However, there is a significant amount of craftsmanship required to bridge the gap between a great idea and a great product. As you evolve that great idea it changes and grows it never comes out like it starts because you learn a lot more as you get into the subtleties of it and you also find there's tremendous amount of trade-offs that you have to make.
There are certain things you can't make electrons do, certain things you can't make plastic or glass, certain things you can't make factories or robots do. and as you get into all these things, Designing a product involves juggling 5,000 different concepts, fitting them together like puzzle pieces, and exploring new ways to combine them. Every day brings new challenges and opportunities to push the boundaries of what's possible, and it's this ongoing process that is the key to successful product development. That process is the "magic"3 -
So I have a question.
How do you freelancers keep motivated? I'm a web developer and that's all I do. However i made a mistake of dedicating myself a little too much.
I moved to a new country and started with all these new projects that started becoming successful however when I started making friends in Uni and out , those friends were less of friends and I treated them more like workmates who I can share projects with and work on new orojects. Because of this, my career overtook me to the extent that that was all I ever worked on. Literally.
It was only recently that I realized that I have been missing out too much. I miss having a life and being with friends. recently I lost my creativity and productivity. Gave up on an insanely huge project because I have not been able to work on it. Lost a job because Im not productive. My life has started falling apart and I don't know how to keep it controlled. I feel I can't bother my friends because we're not totally close and most are only friends on campus.
I don't know what to do where to start or how to be productive again.9 -
Honestly... I'm my own biggest influence. I had a career shift from law enforcement to developer. I hated my job, my life, where I was at and where I was going. I never want to be in that position again so I got myself to a point where I have more freedom and opportunities.
-
The biggest hurdle I overcame on my dev career was coming back to a full time job after a few years spent on a "hippie phase" combining work as an artisan, content developer and editor, and just a few freelance dev jobs. It was all a struggle to start again thinking of myself as "junior again" surrounded by people ten or fifteen years younger than me. But I kept myself over the tidal web and here I am, a Senior again.
-
A connection was looking for a developer in the city my brother-in-law recently moved to (for my sister's career), so I connected them. They exchanged a couple of emails, and he has an on-site interview tomorrow!
He and I are both .Net developers, and I'm older/more experienced, so I offered to rearrange my schedule to help him with some interview prep tonight.
He said no, that he's pretty confident about things, that he'll do some studying and research on his own.
Good for him and his confidence, but I'm kinda salty that he didn't take me up on my offer. I'm pretty damn clever. How dare someone reject my offer for assistance?? I hope the interview goes well of course but if it doesn't I'm very much going to feel some silent "I told you so!"6 -
Two states of a developer every day:
• Fuck this job. I hate everyone and everything. My code sucks. It's not working. Why did I choose this career?! I am so miserable.
• It works! I'm a programmer god. Oh my goodness I'm smarter than everybody.4 -
Because I didn't start coding until 21 I constantly feel behind, but the pure satisfaction from finally getting something to work or to see a project grow iteratively over time keeps the gears turning. The bad part is I feel like I am constantly stressed because of my feelings of always being inadequate. The thing is I didn't only have to learn how to code but I basically had to start from scratch tech wise. i had a decent acer laptop in high school and basically just web browsed and gamed with it. So needless to say most of my life has been away from a computer. Now I feel at a constant rush to compensate for my ignorance. I have slowly become more introverted because I feel like if I don't work on my skill set everyday I stray further away from making myself marketable; this has caused me to become more irritable and to close myself inside more. I want to make a career doing this and I also have the added pressure of not having a degree, so projects and skills are even more mandatory. I truly love programming to the fullest extend, but not having local friends to express code with and to bounce concepts and ideas off of is torture. But I try to keep my head up and make progress out of the day- if the will is there- so I can land my first job as a developer and actually make a living doing something that brings me a little piece of meaning. So overall there is a tradeoff of having added pressure, stress, anxiety and sometimes depression to build a craft that still has ages to go to reach a stage of maturity.10
-
Next week I'm starting a new job and I kinda wanted to give you guys an insight into my dev career over the last four years. Hopefully it can give some people some insight into how a career can grow unexpectedly.
While I was finishing up my studies (AI) I decided to talk to one of these recruiters and see what kind of jobs I could get as soon as I would be done. The recruiter immediately found this job with a Java consultancy company that also had a training aspect on the side (four hours of training a week).
In this job I learned a lot about many things. I learned about Spring framework, clean code, cloud deployment, build pipelines, Microservices, message brokers and lots more.
As this was a consultancy company, I was placed at different companies. During my time here I worked on two different projects.
The first was a Microservices project about road traffic data. The company was a mess, and I learned a lot about company politics. I think I never saw anything I built really released in my 16 months there.
I also had to drive 200km every day for this job, which just killed me. And after far too long I was finally moved to the second company, which was much closer.
The second company was a fintech startup funded by a bank. Everything was so much better than the traffic company. There was a very structured release schedule, with a pretty okay scrum implementation. Every team had their own development environment on aws which worked amazingly. I had a lot of fun at this job, with many cool colleagues. And all the smart people around me taught me even more about everything related to working in software engineering.
I quit my job at the consultancy company, and with that at the fintech place, because I got an opportunity I couldn't refuse. My brother was working for Jordan Belfort, the Wolf of Wallstreet, and he said they needed a developer to build a learning platform. So I packed my bags and flew to LA.
The office was just a villa on the beach, next to Jordan's house. The company was quite small and there were actually no real developers. There was a guy who claimed to be the cto of the company, but he actually only knew how to do WordPress and no one had named him cto, which was very interesting.
So I sat down with Jordan and we talked about the platform he wanted to build. I explained how the things he wanted would eventually not be able with WordPress and we needed to really start building software and become a software development company. He agreed and I was set to designing a first iteration of the platform.
Before I knew it I was building the platform part by part, adding features everywhere, setting up analytics, setting up payment flows, monitoring, connecting to Salesforce, setting up build pipelines and setting up the whole aws environment. I had to do everything from frontend to the backest of backends. Luckily I could grow my team a tiny bit after a while, until we were with four. But the other three were still very junior, so I also got the task of training them next to developing.
Still I learned a lot and there's so much more to tell about my time at this company, but let's move forward a bit.
Eventually I had to go back to the Netherlands because of reasons. I still worked a bit for them from over here, but the fun of it was gone without my colleagues around me, so I quit last September.
I noticed I was all burned out, had worked far too much, so I decided to take a few months off and figure out what I wanted to do with my life. I even wondered whether I wanted to stay in programming.
Fast forward to last few weeks. I figured out I actually did want to work in software still, but now I would focus on getting the right working circumstances. No more driving 3 hours every day, no more working 12 hours every day. Just work close to home and find a company with the right values.
So I started sending out resumes and I gave one recruiter the chance to arrange some interviews too. I spoke to 7 companies in the span of one week. And they were all very interested. Eventually I narrowed it down to 2 companies and asked them for offers. And the company that actually had my preference offered me significantly more than I asked for, which settled the deal.
So tomorrow I'm officially signing with them, and starting next week I'll be developing in Kotlin, diving into functional programming and running our code in serverless environments. I'm very excited! -
Started new job almost two moths ago..
For almost 3 years I was developing custom themes, plugins, and widget for WordPress using PHP, jQuery/AJAX, and MySQL.
The new company that hired me brought me on as a backend developer to help rebuild their custom PHP Framework, and other web based software/products as their moving toward Google Cloud Platform.
When I started, MVC and OOP was new to me... took a couple weeks to get the hang of things, and understand their system.
Just when I was getting comfortable, I had a task assigned to me that was all NodeJS...
Had a 30 check-in the week I started the Node task, and was feeling pretty beat down because it was all new to me and I wasn’t making a lot of progress, and still not comfortable with Promises yet, and some other ES6 features but finding my way around slowly but surely.
Manager reassured me that I wasn’t going to be fired and it wasn’t unique to myself. Very encouraging to hear, but I’m my own worst critic so it’s frustrating not being able to make progress like I would with PHP projects.
Fast forward to this week, I started to review another task for a feed and found it’s all Ruby! Another language I have no familiarity with... and started to question if I’ll every get the hang of all these languages and be a solid team member...
Not only do I have to get a grasp on NodeJS and Ruby now, but then I’ll also have to get familiar with GCP and whatever else comes along with it...
Oh and I’m using Linux now instead of Windows/ OSX... so there’s that too.. plus the other command line tools the company built, and uses..
I was comfortable developing in PHP and know I needed to take a step and accept this job to move my career forward but it seems like I’m always behind the 8 ball...
Some days I wonder if it was worth staying a Wordpress developer and just focused on learning ReactJS and stay more Front-end than Backend..
I enjoy working with talented people but I don’t like being the low man on the totem pole knowing I don’t have the experience yet.
Does it feel like this for all devs?!?!13 -
Hired by large prestigious company to do web development. Understanding at the outset, I was not a web developer, just wanted my foot in the door with the company. 2 days after orientation, I am placed on a $20 million contract expansion with 3 other developers. All new to this contract. So: new language, new technologies, new team, no leadership, no mentorship. 2 months later after a month of asking for help, I'm asked why I'm not delivering solid code by the project exec and moved to the testing team. Testing team lead introduces me to people on the contract and answers questions or tells me vaguely where to loom. Spend last 4 months building a professional fuck you by making myself a yes man to everyone and their mother. Left the contract and have been getting regular hours with them since (including developing for them). New contract loves me and despite the project execs attempt to torpedo me, I have an excellent reputation and am positioned for career advancement already.
I couldn't give him the finger, but I made him regret lettimg me go. Original team lead has since been released for unrelated HR complaint. -
!Rant; Week40
Honestly, before starting my post secondary education in Computer science I had wanted to become an architect.
Since I was maybe.... 10 years old all the way till the semester before graduating from highschool I was sold on becoming an architect.
I love design; Interior design, art, unique use of colors, architecture. I love systems that looked good and worked as well as they appeared.
Over the winter break of my grade 12 year a friend said to me, "Why don't you become a UI/UX developer? You love technology, software and design, why not go into a career where you practice on all three?".
I was surprised to hear that. It had honestly never really occurred to me since I had always told myself I would become an architect.
I guess that leaves me to where I am now. Still a student, but loving my time learning the details behind software development. I do not regret choosing Development over becoming an Architect.2 -
Need Advice + Rant
I am an Android Developer, pursuing an Internship, which i thought would be good for my career. But I am being assigned the task to build search feature for the App using Elastic Search. I intially was halpy to work on Search since it had to be Algolia. I am hating the work now because I am getting so stuck with Elastic and there have been other factors which also have decreased my productivity, but I am being quite inefficient. Now the deadlines are coming closer and if I dont give output I will be laid off. I am thinking about quitting myself because now I feel extremely demoralized and demotivated to work because we first decided to work on Algolia and it was all ready before we thought of shifting to heroku and now on AWS. What do the experienced once suggest? It's not that its impossible to do, now i just have to write queries in Java, again I am stuck and not really looking forward to since I was given the deadline today, for 2 days later.
The only issue is, I may have to return the new phone (OnePlus 3T) which I bought planning to later return the money to someone through my stipend.23 -
> be me
> studying 1.5 years liberal arts stuff and general education class at community college
> transfer to a 4 year university.
> realize I need a major
> Realize I also I wanted to 9ne day have a family.
> realize family would need money
> "struggling actor" not a great choice
> pray about what I should be doing
> get distinct impression that instead of attending the session on majors at the college of fine and performance arts to go to session with the college of Science and engineering.
> hear pitch for computer science.
> signup for introduction to programming taught with c++.
> A couple semesters down the line take 3 classes all at once Discrete Math 1, Linear Algebra, and database design and administration.
> around week 6 realize that all 3 classes revolved around sets and set logic and set math.
> realize rdbs's are "applied" set math and that Each class a little more "applied" than the former.
> Be genius at SQL and set math
> havereally smart database teacher mentored me
> get introduced to the recruiter at the career fair.
> get interviews
> get flown out for 2md interview
> get internship
> do work, and get project back under budget
> a job offer
> finish senior year
> start as a "real" developer supporting business data and analytics.
> ???
> profit.3 -
*confession*
I'm one of *those* developers that sold their soul to Microsoft technology stack early in their career, and then bought in into even more narrow specialization, SharePoint dev (Could easily have been Dynamics or similar) ...
...And almost don't regret it. The only concern is becoming obsolete in time, but I suppose life of a developer is always learning, so all should be fine.
Major kudos to all non-MS developers, I enjoy reading about your lives here.5