I'm 54 y.o.

I think I'm completely outdated in my skill, as in the last 14 years, I worked on a specific business problem, with an old technology: a JSP application + javascript + postgres.

I do understand software development, agile, web application development, linux server, basic/moderate AWS skills, etc.

Now they laid me off instead of including me in the evolution of version 2 of the software. Maybe covid, company had almost no cash-flow. Well they have now...So basically they fired me to find money to rewrite the application.

I feel without hope at my age.
I'm a generalist.
I can understand fairly well everything you'll throw at me, reactnative, angular, nosql, python, but I have little first-hand experience.

I don't have a lot of management skills, even if I've given frequent presentations to C-roles and board, and I implemented a whole agile methodology in my team.

I don't know what to do.
The amount of technology to study is huge nowadays. When I was younger I could get away with some php and java.

Full-stack developer is a big word for me. Maybe I could handle a full stack web application, but not from scratch.

I feel at my age, I'll compete with 20-something guys with better skills and lower salary requests.
I don't think I can pull a night anymore.

I'm trying to shoot high to management positions with no much success.
I'd like to go on developing, I know that there are 50-something developer out there, but who managed to find a new position at 55? at 60?

As soon as I finish the few money I spared, I'll be on the street, I'l be the "website for food" guy.

My fav way of coding.

Source: NixCraft

Here's a true story about a "fight" between me and my project manager...

I've been working as a Frontend developer for nearly two years, managed to acquire a decent amount of knowledge, in some cases well above the rest of my coworkers, and one day I got into a bit of a disagreement with my project manager.

Basically he wanted me to copy/paste some feature from another project (needless to say, that... "thing" has more bugs than an ant farm), and against his orders I started doing that feature from scratch, to build a solid foundation from the very start.
I had a lengthy deadline to deliver that feature, they were expecting me to take some time to fix some of the bugs as well, but my idea was to make it bug-free from the moment the feature was released. Both my method and the one I should be copying worked the exact same, but mine was superior in every way, had no bugs, was scalable and upgradeable with little effort, there was no reason not to accept it.

We use scrum as our work methodology, so we have daily meetings. In one of those, the project manager asked me how was the progress on that new feature, and I told him I was just polishing up the code and integrating it with the rest of the project, to make sure everything was working properly. I still had a full day left before the deadline set for that feature, and I was expecting to take about half an hour to finish up a couple lines of code and test everything, no issues so far...

But then he exploded, and demanded to know why wasn't I copying the code from the other project, to which I answered "because this way things will work better".
Right after he said that the feature was working on the other project, copying and pasting it should take a few minutes to do and maybe a couple of extra hours to fix any issues that might have appeared...
The problem here is, the other project was made by trainees, I honestly can't navigate through 3 pages without bumping into an average of 2 errors per page, I was placed into this new project because they know I do quality code, and they wanted this project to be properly made, unlike the previous one, so I was baffled when he said that he preferred me to copy code instead of doing "good" code...
My next reply was "just because something has been made and is working that doesn't mean that it has been properly made nor will work as it should, I could save a few hours copying code (except I wouldn't save any, it would take me more time to adapt the code than to do it from scratch) but then I'll be wasting weeks of work because of new bugs that will be reported over time, because trust me, they will appear... "

I told him this in a very calm manner, but everybody in the meeting room paused and started staring at me, not many dare challenge that specific project manager, and I had just done that...
After a few seconds of silence the PM finally said... "look, if you manage to finish your task inside the set deadline I'll forget we ever had this conversation, but I'll leave a note on my book, just in case..."

I finished that task in about 30 mins, as expected, still had 7 hours till deadline, and I completely forgot about that feature until now because it has never given any issues whatsoever, and is now being used for other projects as well.

It was one of my proudest/rage inducing moments in this project, and honestly, I think I have hit my PM with a very big white glove because some weeks after this event the CEO himself came to the whole team to congratulate us on the outstanding work being made so far, in a project that acted against the PM's orders 90% of the time.

Startup: let's improve on our MVP and build an actual website app.

Me: ok.

[go through 2 weeks discovery and planning stage]

Manager1: love working with you. You explain and work in a really professional manner.

[MVP gets built in 2 months, I'm the only dev designer devops throughout]

Manger1: Omg love it! Wait till the other manager sees it. I knew you were right person for the job.

Other users: oo cool. I love features x, y, z.

[two days later shows to Manager2]

Manager2: x doesn't work, feature you is not useful and doesn't work... Hate it. I think we'll move you to another project.

Me: (woah that escalated quickly meme plays in my mind)

Me: [explaining MVP, lean methodology, your internal decision making processes]

...

Manager2: Yeh we want you to not work on any development work (even though those are your skills and extensive knowledge etc) we need you to do admin tasks (that have nothing to do with product or coding etc)

Manager1 and employees: 😲 wtf

Me: I quit

- - -

Now they are struggling in every way possible and don't have enough funds to hire another person close to what they need to help them.

I feel the need to take a different approach to this week's rant. I think someone needs to defend teachers, for a number of reasons. Obviously this is probably out of place on devRant but it is a kind of rant against those who think they know everything and have nothing to learn.

1) Teachers are not industry specialists. They do not spend their lives keeping on top of the latest framework or project management methodology or code management tool. They are educators and that brings its own set of out of hours challenges and training exercises.

2) They have a course to teach and have probably used the same one for quite some time. Years probably. They (should) teach the fundamentals of programming not a particular language or syntax or quirk. Those fundamentals don't really change. Logic, problem solving, precision, structures, etc.

3) They need to provide a course which will cater for different skill levels. There are always class members who are bored because it's too easy and others who struggle in any subject.

4) Teaching is like any profession - there are really, really good ones, OK ones and there are shit ones.

5) They have probably never developed a detailed project or solution in their lives. They don't know the pitfalls and challenges that teams face in this kind of environment. Should they - maybe. But the probably don't.

I think that's all... I'm not a teacher (although I did fancy the idea at a time) but just feel they get a rough ride sometimes (particularly on here).

I joined a "multi-national" company in middle-east where 90% of the developers are Indian. And since it's a "multi-national" company with 50+ developers I thought they already figured it out. Most of them have 5-10 years of experience. They should know at least how to use git properly, deployment should be done via CI/CD. database changes should be run via migration script. Agile methodology, Code Review - Pull Request. Unit testing. Design Patterns, Clean Code Principle. etc etc

I thought I'm gonna learn new things here. I have never been so wrong in all my life...

Technical Manager doesn't even know what Pull Request is. They started developing the software 4 years ago but used Yii v1 instead which was released almost a decade ago. They combined it with a VueJS where in some files contains around 4000 lines of code. Some PHP functions contain 500+ of code. No proper indentions as well. The web console is bloody red with javascript errors. In short, it's the worst code I've seen so far.

No wonder why they keep receiving complaints from their 30+ clients.

Dev: This is the first version of this new app, we’re still experimenting with how it’s going to work but initial headway is looking promising. It cost very little to make, came together very quickly and is already resulting in productivity increases for users. We’re just doing a bit of code cleanup now and we’ll make a move on the next iteration.

Corporate IT: This project is being completely mishandled! In order to successfully build an app you have to determine every single requirement beforehand! It takes millions upon millions of dollars due to the complex system of governance and approval that needs to exist. Massive numbers of stakeholders need to be involved and coordinated to even make so much as a login screen! I bet your project doesn’t even have a documented list of core values.

Dev: Has you ever successfully built an app using that methodology?

Corporate IT: 😡 That’s a loaded question. I went to school to study project management and have over 25 years of experience in the field. If you had the training and experience I do you would know that tech projects are naturally very volatile and there’s nothing you can do about that!

Dev: …

Help.

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

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

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

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

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

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

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

For once I would like to have a scrum master who doesn't try to be a psychologist and just helps us adhere to whatever methodology we are supposed to be following.

We are developers, we know we're dysfunctional, we like it that way and stop telling me I have to wear pants to meetings!!!

Junior: I don't think the methodology you came up with is working.

Me: Why?

Junior: There's an exception when I ran it

Me: ...what exception

Junior: FileNotFoundError

Me: ......have you checked if the path to the file is correct?

Junior: No

(A few moments later)

Junior: Oh I forgot to decompress the zip. Nevermind.

Interviewer: Do you use object-oriented methodology?
Me: (Do I need to elaborate it if I say yes?) Usually I do.
Interviewer: Em. I see.
#End of story.

Worst collaboration experience story?

I was not directly involved, it was a Delphi -> C# conversion of our customer returns application.

The dev manager was out to prove waterfall was the only development methodology that could make convert the monolith app to a lean, multi-tier, enterprise-worthy application.

Starting out with a team of 7 (3 devs, 2 dbas, team mgr, and the dev department mgr), they spent around 3 months designing, meetings, and more meetings. Armed with 50+ page specification Word document (not counting the countless Visio workflow diagrams and Microsoft Project timeline/ghantt charts), the team was ready to start coding.
The database design, workflow, and UI design (using Visio), was well done/thought out, but problems started on day one.
- Team mgr and Dev mgr split up the 3 devs, 1 dev wrote the database access library tier, 1 wrote the service tier, the other dev wrote the UI (I'll add this was the dev's first experience with WPF).
- Per the specification, all the layers wouldn't be integrated until all of them met the standards (unit tested, free from errors from VS's code analyzer, etc)
- By the time the devs where ready to code, the DBAs were already tasked with other projects, so the Returns app was prioritized to "when we get around to it"

Fast forward 6 months later, all the devs were 'done' coding, having very little/no communication with one another, then the integration. The service and database layers assumed different design patterns and different database relationships and the UI layer required functionality neither layers anticipated (ex. multi-users and the service maintaining some sort of state between them).

Those issues took about a month to work out, then the app began beta testing with real end users. App didn't make it 10 minutes before users gave up. Numerous UI logic errors, runtime errors, and overall app stability. Because the UI was so bad, the dev mgr brought in one of the web developers (she was pretty good at UI design). You might guess how useful someone is being dropped in on complex project , months after-the-fact and being told "Fix it!".

Couple of months of UI re-design and many other changes, the app was ready for beta testing.

In the mean time, the company hired a new customer service manager. When he saw the application, he rejected the app because he re-designed the entire returns process to be more efficient. The application UI was written to the exact step-by-step old returns process with little/no deviation.

With a tremendous amount of push-back (TL;DR), the dev mgr promised to change the app, but only after it was deployed into production (using "we can fix it later" excuse).

Still plagued with numerous bugs, the app was finally deployed. In attempts to save face, there was a company-wide party to celebrate the 'death' of the "old Delphi returns app" and the birth of the new. Cake, drinks, certificates of achievements for the devs, etc.

By the end of the project, the devs hated each other. Finger pointing, petty squabbles, out-right "FU!"s across the cube walls, etc. All the team members were re-assigned to other teams to separate them, leaving a single new hire to fix all the issues.

So y'all listen to me.

No Software Development methodology or technique is a silver bullet. None!

Every engineer must acquire the ability to know when and where to use different approaches, appropriately.

Well, you wanna read that again.

For the first time I am feeling like.... I hate my job.

Agile and Scrum can be fucked, but at least there is a work methodology. I was hired by a company being run the old school way.

These guys never heard of git??
- Fuck you. We never used git and neither should you.

Client company does not want to give me push/pull access to their gitlab instance??
- Fuck you, you can use our RDP server for that.

Project planning features be damned, they've got email, Teams and videocalls!

Can I develop in peace? Fuck no, I have to give IT support to the guy who hired me.

Our timeline is defined IN A FUCKING WORD DOCUMENT FOR FUCKS SAKE. I can't connect Issues to milestones in a Word doc

Oh, and the customer is running everything on prem. If there is a need to scale up, FUCK ME. I should have specified 20 machines from the get go or gtfo. We're using 2 machines to run 8 different services that are going to be ingesting and computing data.

They want state of the art on a cheapskate.

And I have nothing else lined up at the moment. Although I am soon to renew the contract... This contract binds me with professional responsibility for a project being ran by people who do not give a single fuck about optimizing the work process.

Client : We want to develop this particular software. While developing it, we will be following Agile methodology.

Developers: Sure.

After developer achieves few features and decides to give 1st Demo of the software to the client.

Client : Wtf is this? This is an incomplete software, there are bugs in it.

Developer : Yes, you point that out to me and I will solve them.

Client: What do you mean point them out for you l, couldn't you do it yourself?

Developer: As a standard method, we often do unit tests, but we are not testers and with a strict deadline to match, we are more on the core implementation then checking again and again for minor bugs.

Client : I thought it would be a full proof software without any bugs in the 1st demo.

Developer : Software development is a process. It's not straightforward, hence you only mentioned at the initial, it's agile.

Client : If that's so, let's make it not agile and make you rot in hell for the next few fays. Now you next time show me a demo with no bugs, great complicated features and we will not mention you our expectations, predict them by yourselves, and most importantly, here's an impractical strict deadline.

A delicious Sprint Planning 😋

It was a hard sprint (SCRUM methodology), but finally we were on our next’s sprint planning meeting. We had a lot of tasks to define and estimate. For the first one, we all estimated the task with 5 points, and for the second one we voted for 3 points. We were coordinated XD so, our boss said “let’s do something, if all of you vote, let’s say, 5, and another votes for a different number, he or she’s gonna buy us a six pack of beer”. Challenge accepted.

Two partners and I have to buy beers for this friday after work 😂 I don’t even mad 😋🍻

Code comments #1: A way to document bad code that wasn't reduced to it's essentials and thus unreadable. Bad.

Code comments #2: A way to explain for non-programmers how the code works. Wrong place.

Code comments #3: Company policy. No one really knows why, but others do that, so we better do it to. The management sucks.

Code comments #4: Because some hip methodology/guru describes how to document code. After a few years, when the methodology has been (unofficially) forgotten, everyone still comments the code the same way. The old management sucked.

Code comments 5#: For insecure programmers who want to convince them self they understand the code they've written. Maybe apply at McDo?

Code comments #6: Some programmers are apparently paid by lines of code. Possibly understandable.

// Comments, anyone?

Asshole-Driven development (ADD) – Any team where the biggest jerk makes all the big decisions is asshole driven development. All wisdom, logic or process goes out the window when Mr. Asshole is in the room, doing whatever idiotic, selfish thing he thinks is best. There may rules and processes, but Mr. A breaks them and people follow anyway.

This is PART 1/2 of a series of rants over the course of a software engineering class years ago.

We were four team members, two had never failed a class, I’ll refer to them as MT and FT, male and female top students, respectively, and an older student with some real world experience who I’ll refer to as SR.

Rant 1: As I was familiar with the agile methodologies I became the Scrum Master and was set with the task of explaining it to the team members, SR showed up late and nobody seemed interested in learning new methodology. At this point I knew we'd have trouble as a team.

Rant 2: FT made up her project proposal without informing anybody, which required a real client/product owner. We only figured it out after her proposal was accepted as the project, so we ended up working with fake requirements.

Rant 3: This one is partly my fault. I researched first and then worked, which meant I was the last to turn up my work. In one activity MT pressures me and I agree to a deadline so everyone can send their work to the teacher in a timely manner. Since I was the last to finish, I was also asked to give the doc some formatting, which I did in a hurry so it wasn't the best.
The next day MT and FT start complaining about me, saying I took too long and that they expect me to do better next time or else. At the same time they were stressed and in a hurry because we had to explain the project outline in front of the class and they didn't study.
Turns out copying and pasting all your work in less than an hour means you don’t learn anything. FT actually asked me for help days before and I sent her a website in English, which she wasn't very good at, so she just ran it through Google Translate and called it a day.
Later FT called me rude for interrupting MT in the presentation, which I did because he started making up stuff about the project.

Rant 4: SR expressed his dislike for school through profanity in variable names and commit messages. This caused MT and FT to dislike him. I thought it was immature but if anything it should’ve been reported to the teacher and move on.

Rant 5: I was stuck trying to get the REST API working for the project Admittedly this was my fault, too, because I was pushing for the usage of things nobody was familiar with for the sake of learning. This coupled with SR’s profanity led to drama and the progress was dropped, starting over from scratch.

At this point I stepped down from the Scrum Master role as nobody seemed to listen anymore.

My boss and I, with a normal morning greeting in slack

Me: morning boss, how are you?

Boss: very good and you?

Me: marvelous. hey boss, do you have a secret entry to your office? I didn't see you coming

Boss: hahaha, front door :| . And I greeted everyone too

Me: :( sorry

Boss: Microsleep 😂

Me: 😎 nope, extreme concentration

Me: it's a new development methodology, born from extreme programming

Boss: 😶

*sigh*

So we have this supervisor that I’ve mentioned before in my previous rant(read if interested). This man has been a pain to my side since I started working here. He does a phenomenally good job at being a douche bag and he has the need to resort to screaming and yelling if you happen to disagree with his methodology in any point of you. He likes to make fun of and be little you as well. Oh and I’ll mention he does it in front of all your co-workers. All bad habits and even less from some one in a supervisor position.

I think I’m a pretty reasonable guy, I try to get my work done only asking for help when absolutely necessary ie idk what’s going on or I’m stuck. This guy has the bad habit of breathing over your shoulder while you’re working......... Anyway I hit a breaking point today and waited til he was in his office to confront him.

I asked to walk in politely and asked if I could close the door it was a personal matter. After I sat down and vented to him explaining that what he’s doing with this egotistical persona of his is wrong and it’s creating an environment that cause everyone to feel like shit thus cause lowered work efficiency. I told him that belittling and offending is a bad tactic and that we are grown ass adults. It shouldn’t be necessary for you to yell or make fun of me, shit if I wanted to eat yelled at I’d go home to my father. He’s allowed this guy is not.

Well cutting it short I finished the convo and he didn’t say much just agreed with some points and stressed others that would be too much to mention. I’m not dumb either I recorded the convo just in case he tries to pull something. But I get the feeling like this is gonna turn out really well or it’s gonna go south.

Just wanted to rant to the rantFam first.

I’m done now.

Next year I will strive to achieve the best test coverage on all our components and design all our new features using best-practice agile methodology with a realtime user involvement.

Reverend on 7 January: Fuck that, we need to ship this shit to production now.

Novice seeking advice, how do you indie/solo dev guys manage your time and productivity to stay clear on what to prioritize and deliver faster ?

I proposed agile training to my company.
I choose a well known coach around here, with good references.

First 3 days were great. After a month he came back for another session and check progress.

This time, he literally fell asleep during the workshop. Several times. He would ask questions, sit down and quietly fall asleep while waiting for our answers.

We were astonished and embarrassed.

He apparently had a very hard working period and could not cope with traveling and working so much. He apologized some day afterwards and didn't charge us for the day.

He never came back. The team didn't take it very well and my reputation was compromised, as well as trust in the methodology I think.

I kept saying that everybody can have a bad day, but it was probably just to defend myself and my fucking stupid idea of changing the world.

A real fucking shame. Still I can't believe when I remember this.

Is it ok if i create a trello board and create cards quickly without following any type of agile methodology because the project is only for me? I cant spend hours of my time writing exact and precise cards following some standard

Id have cards like Todo Doing and Done

Thats it just so i can keep track quickly and focus most of my time on code

Is this ok

SO MAD. Hands are shaking after dealing with this awful API for too long. I just sent this to a contact at JP Morgan Chase.

-------------------
Hello [X],
1. I'm having absolutely no luck logging in to this account to check the Order Abstraction service settings. I was able to log in once earlier this morning, but ever since I've received this frustratingly vague "We are currently unable to complete your request" error message (attached). I even switched IP's via a VPN, and was able to get as far as entering the below Identification Code until I got the same message. Has this account been blocked? Password incorrect? What's the issue?

2. I've been researching the Order Abstraction API for hours as well, attempting to defuddle this gem of an API call response:

error=1&message=Authentication+failure....processing+stopped

NOWHERE in the documentation (last updated 14 months ago) is there any reference to this^^ error or any sort of standardized error-handling description whatsoever - unless you count the detailed error codes outlined for the Hosted Payment responses, which this Order Abstraction service completely ignores. Finally, the HTTP response status code from the Abstraction API is "200 OK", signaling that everything is fine and dandy, which is incorrect. The error message indicates there should be a 400-level status code response, such as 401 Unauthorized, 403 Forbidden or at least 400 Bad Request.

Frankly, I am extremely frustrated and tired of working with poorly documented, poorly designed and poorly maintained developer services which fail to follow basic methodology standardized decades ago. Error messages should be clear and descriptive, including HTTP status codes and a parseable response - preferably JSON or XML.
-----

This whole piece of garbage is junk. If you're big enough to own a bank, you're big enough to provide useful error messages to the developers kind enough to attempt to work with you.

I'm starting to feel super frustrated with my job.
Sometimes I feel like people who work for large tech companies must have it easy. My company is trying to do this digital transformation thing. Modern development practices Scrum, agile, CI/CD etc. So I was put on a team to work on a project with this new methodology. The idea was we would build the front end and interface with the core systems via service calls. Of course it didn't work out that simple and we had to add our own server side stuff but whatever. It's really hard without a point of reference for any of this stuff. We don't have established coding standards, the data we are working with is a mess, incompetent vendors, the infrastructure team supporting the environments can be such arrogant fucks when we need their help to get shit done. The team also doesn't have any members who really know the core systems well. I am the only developer on the team who is an employee of the company the rest are contractors who are in and out. Last week it was literally just me. This is my first job out of school btw I've been here a year now. I guess I just feel frustrated that I have to figure out so much on my own I don't really have many senior devs at the company I can look to. And on the team I've sorta ended up in an unofficial leadership position. Feels like a lot on my shoulders. I feel like if i could have worked for a bigger company I could learn to do a lot of things better. I feel like there's too much on me for the amount of experience I have or am I wrong ?

Disclaimer: I hold no grudges or prejudices toward [CENSORED] company. I love the concept of the business model and the perks they pay their employees. Unfortunately, the company is very petty, and negligence is the core of the management. I got into an interview for the position, of Senior Software Engineer, and the interview wouldn't take place if wasn't for me to follow up with the person in charge countless times a day. The Vice President of Engineering was the most confused person ever encountered. Instead of asking challenging questions that plausibly could explain and portray how well I can manage a team, the methodology of working with various technology, and my problem-solving skills. They asked me questions that possibly indicated they don't even know what they need or questions that can easily get from a Google Search. I was given 40 hours to build a demo application whereby I had to send them a copy of the source code and the binary file. The person who contacted me don't even bother with what I told her that it is not a good practice to place the binary in cloud storage (Google Drive, OneDrive, etc) and I request extra time to complete the demo application. Since I got the requirement to hand them the repository of the codebase, it is common practice to place the binary in the release section in the Git Platform (Jire, Azure DevOps, Github, Gitlab, etc). Which he surprisingly doesn't know what that is. There's the API key I place locally in .env hidden from the codebase (it's not good practice to place credentials in the codebase), I got a request that not only subscript to an API is necessary but I have to place them in the codebase. I succeed to pass the source code on time with the quality of 40 hours, I told him that I could have done it better, clearer and cleaner if I was given more grace of time. (Because they are not the only company asking me to write a demo application prior to the assessment. Extra grace was I needed)

So long story short, I asked him how is it working in a [CENSORED] company during my turn to ask questions. I got told that the "environment is friendly, diverse". But with utmost curiosity, I contacted several former employees (Software Engineer) on LinkedIn, and I got told that the company has high turnover, despises diversity the nepotism is intense. Most of the favours are done based on how well you create an illusion of you working for them and being close to the upper management. I request shreds of evidence from those former employees to substantiate what they told me. Seeing the pieces of evidence of how they manage the projects, their method of communication, and how biased the upper management actually is led me to withdraw from continuing my application. Honestly, I wouldn't want to work for a company where the majority can't communicate.

I really really hope that no one post this,a friend texted it to me and I wanted to share it because made my day.

Idk where it comes, so feel free if know where this came from to post it:

//FUN PART HERE
# Do not refactor, it is a bad practice. YOLO

# Not understanding why or how something works is always good. YOLO

# Do not ever test your code yourself, just ask. YOLO

# No one is going to read your code, at any point don’t comment. YOLO

# Why do it the easy way when you can reinvent the wheel? Future-proofing is for pussies. YOLO

# Do not read the documentation. YOLO

# Do not waste time with gists. YOLO

# Do not write specs. YOLO also matches to YDD (YOLO DRIVEN DEVELOPMENT)

# Do not use naming conventions. YOLO

# Paying for online tutorials is always better than just searching and reading. YOLO

# You always use production as an environment. YOLO

# Don’t describe what you’re trying to do, just ask random questions on how to do it. YOLO

# Don’t indent. YOLO

# Version control systems are for wussies. YOLO

# Developing on a system similar to the deployment system is for wussies! YOLO

# I don’t always test my code, but when I do, I do it in production. YOLO

# Real men deploy with ftp. YOLO

So YOLO Driven Development isn’t your style? Okay, here are a few more hilarious IT methodologies to get on board with.

*The Pigeon Methodology*
Boss flies in, shits all over everything, then flies away.

*ADD (Asshole Driven Development)*
An old favourite, which outlines any team where the biggest jerk makes all the big decisions. Wisdom, process and logic are not the factory default.

*NDAD (No Developers Allowed in Decisions)*
Methodology Developers of all kinds are strictly forbidden when it comes to decisions regarding entire projects, from back end design to deadlines, because middle and top management know exactly what they want, how it should be done, and how long it will take.

*FDD (Fear Driven Development)*
The analysis paralysis that can slow an entire project down, with developments afraid to make mistakes, break the build, or cause bugs. The source of a developer’s anxiety could be attributed to a failure in sharing information, or by implicating that team members are replaceable.

*CYAE (Cover Your Ass Engineering)*
As Scott Berkun so eloquently put it, the driving force behind most individual efforts is making sure that when the shit hits the fan, you are not to blame.

What would be the better approach for loading very big in size or in quantity files in java?
1) Loading data parallel through multiple threads
2) Loading data in series in a single thread
3) any other methodology?

Just asking because loading time is varying both cases.

Newbie Agile Team: "Hi Scrum Coach, we studied and implemented the Scrum methodology, but we are late as before and our software is buggy and shitty as ever, how is that?"

Agile Coach: "Scrum Methodology is easy to learn, but difficult to master!"

Newbie Agile Team (chorus): "Oh coach, Fuck yourself daily, with your coffe thermos, standing up and once per week retrospectively. If you'll come at the next review meeting, we will gangbang your ass in front of the stakeholders"

Just realized one of my partners works with the waterfall methodology. I told him I'm sorry i cant work with him. What do you think?

Any dev who is asked to give “deadlines” then cried about how it’s “waterfall” and you cannot produce business requirement deadlines in agile methodology needs to stop being dependent on terminology and learn that part of programming is proper estimation.

Milestones, business deadlines and agile can go-exist. Anyone who says they don’t, then cries “waterfall” when asked to produce deadlines greater than 4 weeks out, please never work with me

Envy me. The fnew position I am getting spun up on has me assigned to take over the work of a guy who uses no versioning methodology and updates directly to production code. and I have to get it into CM!!!

I'm working in a really really small start up company (I'm the only developer here with the owner being a programming professor in the local uni).
It's my first job after leaving uni and I knew it was a risky decision that I've made but it was my hometown and I could save some extra money by saving on rent and food, also I've always loved a good challenge.
But the challenge isn't working as excepted. It's been a year since I've started here and there was no planning for almost nothing, it's a "do as you think it's best but I'll probably won't like so you have to it again" kind of methodology. Also I've been hire to do an hybrid mobile app and I've ended up doing a full e-commerce website with shitty outdated technology that I've had no experience in using.
So for me I'm more than done. I'm tired of having my suggestions being completely ignored, of the lack of planning and instruction and the fact that I'm being underpaid for what I do.
Fuck it, I'm looking for a new job.

I was brought into my new position as part of an transformation of waterfall to agile methodology.

We are now running 4 while projects and need to restart the remaining 29 projects using agile principles. The business management type people love agile, but somehow the people inside the current waterfall practices doesn't.

They are afraid their silo work will either expand or not exist thus making it hard to transform the company. Also the company have been subjected to the dead sea effect.

Therfore, the project that is currently in the space of transformation is making my blood boil because people just ain't passionate enough about software.

Either you craft software, or, well you sit and suckle other's money. People suckling should please grow up and start venturing beyond there cozy 9 to 5 and transform to be a professional software doer rather than a BA, DEV, IT GUY.

YOU BASTARDS GET A SHITLOAD OF MONEY AND DON'T DESERVE IT FOR THE EFFORT YOU BRING.

It is your software, own it, be proud of it. Read up to make it better. And as always, the people debugging your code can be a violent psychopath

A long struggle to change a nazi enforced scrum methodology that cut our efficency, technical standard and dedication to the product by just working on fragmented features that were added and removed by the wim of the PM.

Job offer in hand as senior dev somewhere else, I stayed, got better eventually. My old boss kept complaining on me for years in performance reviews that I did not respect managements decisions.

Two years of badly led scrum regime left our product in a spagetti mess that is still trying to be untangled.
Til this day, if I hear someone mutter "scrum", I feel a strong need to run far far away.

Copy and paste everywhere is not an acceptable software development methodology. It's a sign that something's very wrong.

I find Scrum Masters useless. I'd rather have a developer replace them. Am I overseeing their value? Could someone enlighten me?

I also think that if a group comprised of smart people, things spontaneously happen without needing a handrail to walk along.

What to do if someone asks for your help with problem X, but then you figure out they originally tried to fix problem A and recursively came up with bad solutions until they got at X at which point the entire codebase overlaps responsibilities, implementations leak, concrete instances are created in controllers ignoring DI and you just can't say ANYTHING nice about it?

Also does not follow a methodology and just does whatever, thinks singletonning a database context is a good option because stuff isn't saved, says they will 'refactor later' even though it should have been done last week and just doesn't seem to get it?

I've told them that what they're doing is plain wrong and they're making it harder for themselves than it needs to be, but they just seem to not get it, even though at this point basic stuff like that shouldn't be an issue.

Posted this in rant since it became kind of a rant instead of a question

Alright, let's talk about Scrum Masters. Honestly, I just can't wrap my head around why they're even a thing. It's like someone decided to invent a job title for a role that's already covered by other folks on the team.

I mean, think about it. Who's usually sorting out the team's issues, making sure everyone's on the same page, and keeping the project on track? That's right, it's the project manager or the lead dev. They're already in the trenches, dealing with the nitty-gritty, so why do we need this extra layer?

And don't even get me started on this "servant-leader" nonsense. It's like they're trying to be the team's buddy, but they've got no real power to make things happen. It's like being a king without a crown. Who's going to respect that?

Plus, having a Scrum Master often just leads to more red tape. Instead of getting stuff done, we're stuck in endless meetings, talking about process this and methodology that. It's like we're more focused on how we work instead of actually working.

The best teams I've seen don't need a Scrum Master to babysit them. They need a real leader, someone who's not afraid to make the tough calls and who can give them the tools they need to kick ass and take names.

So, in a nutshell, I think Scrum Masters are about as useful as a chocolate teapot. It's high time we ditched this outdated role and got back to doing what we do best: building awesome stuff.

I have a lot to say..
In my project theres a design department, since the beginning of the project they didn't want to be part of the scrum methodology..(they used to work waterfall..)
So.. they have a disorder on the user history needs, and they argue for every request that we need to finish the history..
They dont go to the plannings, dailys.. they dont know shiet!
And meanwhile telling u this rant im getting mad as fuck..
so at this point i cant even explain how FUCKING UPSET I AM & WHY THE FUCK people reject the change and decides to work by their own! fuck this!

anyways ill share 2 storys ( i have a lot..)

1. "Raise your hand if you dont know whats a button?"
So we created a standard button to be re used it in other forms..
The designer came late to the planning, and decided to change the button layout (again x4) & it's behavior, so he wanted "the button disabled, but not disabled", since he wasnt able to explain it as well, he got upset.. and said that we didn't know about how a button works & asked the public to raise up the hand who didnt know what is a button.. and we were like :
dude are u fucking serius?.. u cant even explain what the fuck u want, u came late, and know u act like if you teach about ux & design? fucking rockstars..

2. "why do you call me to the planning if you don't need anything from me?"
We ask and required the designer to be in the plannings to avoid the disorder and the delivery delays..
that day we didn't require anything from the designer, so he started complaining that we called him for no reason..
me : dude, d u even realize why is this meeting called planning?

So, we're apparently going to build a sort of social media(with competitions) for our software engineering project. I thought of a productivity app that would follow the GTD methodology (with my own additions), but my team mates thought my idea wasn't big enough for a team of 10. One claimed that he would do it all by himself in a week/month(Don't know what he said). Oh, well. Anyways, I'm going to build that software as a side project with a friend or two. I hope that goes well..

PS. We need a team name. Any suggestions?
I thought of Team Sudo lol.. No one liked it..

I must admit sometimes agile methodology zealots annoy me but I just quit a shop with no process, no source code repository, and no testing. I worked there a month and had no idea such places still exist. I knew it was a bad idea but I needed remote work. I tried to evangelize to them but they blamed me for everything after they fired the project manager.

Soooo lately my boss just introduced the AGILE methodology using Epics, UserStories, Tasks, etc. I enjoyed the approach so much. Scrums, Sprint meetings and the like. And also questioning him why ONLY NOW.

Fr-Agile

Francium Agile Methodology is characterized by lack of proper planning, and constant interruption during the development process as specs are pulled out of product owners asses ad nauseam. Fr-Agile methodology is known to result in an extremely radioactive team environment.

Had a job advert where they legit said a requirement was following the waterfall methodology.

Nope. Nope nope nope nope.

Can we patent an Idea? I have my product A ready for launch. Company B claims that we have patent for that idea. We both trying to solve exact same problem using exact same methodology. How should I proceed? Any legal advisors here?

All u need is C folks seriously fuck the OOP concept you waste more time in a paradigm dilemmas than writing functional code. And that’s a damn fact.

I feel sorry for the mobile developers that are stuck using the OOP methodology

So... I might have to build a survey and analysis tool to be used online nation wide (the final client is the government).
The bad news, it's probably going live in a week.
Even though 90% I wrote and tested in the last 3 years (matrixes,formulas,dB, Interface elements ) from previous runs, I have to handle fronted, databases, math, testing and design.
Over a daily changing methodology and session workflow (by my direct client).
No sleep for the next few days 😭

Waterfall.

I string dislike the waterfall methodology and much prefer agile or scrum. And it's incredibly difficult that upper management only understands waterfall while claiming to know agile.

Meanwhile they want things completed by deadlines that are only possible with an agile approach. So you have a mishmash of upper management running waterfall with impossible deadlines and developers trying to meet those deadlines running in agile.

Anyone else have this problem?

React, it's declarative way of doing things, and the functional programming methodology it prefers.

Realized how much I've moved on from for-loops and class/object instance to maps, filters and immutability/observers when I worked on a Laravel project after so long and found myself forced to do things in the, erm, "PHP" way, despite spending my initial year and a half of programming working exclusively in PHP.

Sure, there's Class Components and imperative techniques in React but I had blissfully settled into using the flexible nature of doing things enabled by both native JS and React, with hooks, Lodash/Ramda and (almost fanatically) pure functions

[Paraphrased quote] "We're implementing an Agile methodology with 12 week sprints."

I hate project managers trying to stay relevant to a agile development methodology. Our PM doesn't care if we are working and providing value to the customer, only about checking off his Project check boxes.

tech lead CANCELS Monday stand-up becuase they cannot attend. and I work and status and update my tasks in or virtual task board. I forget to send a message mentioning I'll be kissing Tuesday standup. Then he sends me emails like the following sent to me, my manager, and my tech lead: "please remember to notify your team if you cannot attend the standup, and to send an agile status to the team. This is something that is required and not optional. We are trying to firm up all stories and tasks and need to hear a status. We are in week 1 of iteration 4.3. Thanks."

I'm coding and delivering value to the customer. Wtf are you doing dude?

I've just found a PHP dev job offer which claims literally:

– Our company philosophy: "Every person is a world unto himself." describes our daily work methodology.

And I think they say it as a positive thing LOOOOOOOL

So i am working on a project based on Agile methodology but client wants to have a daily 4-5 hour code review session like he used to do in waterfall model. What should i do, how to say no diplomatically?

What branching methodology do you use and why? We've been using a trunk based development model, but I'm reviewing others.

Today, I discovered a new software development methodology being used by co-workers. No, no, it's neither agile nor pair programming. It's called disruptive programming:
A methodology where it's ok to make sure your part of coffee works. Fuck the rest and let them go figure.

“A computer language is not just a way of getting a computer to perform operations but rather that it is a novel formal medium for expressing ideas about methodology. Thus, programs must be written for people to read, and only incidentally for machines [including the human] to execute.” (The Structure and Interpretation of a Computer Programs, 1985)

“If you try to make something beautiful, it is often ugly. If you try to make something useful, it is often beautiful.” -Mr. OSCAR WILDE

Our project using Agile methodology, we have every day stand-up meeting(scrum meeting) that normally end around 10 to 15 minutes with 7 ppl.
One day The Project Owner came and join our stand-up meeting that cost us like sprint planning
And The Project Owner did not stop there, he come again next day for the 1 week.
Because of that our product backlogs and Sprint Planning goes haywire.
We failed to delivery what we planned for that project.

Trying to implement DDD into this current project of mine but the whole concept of converting Eloquent objects into plain entities seems to be more work than it is worth.

But the whole methodology of DDD also seems rather complicated.

So, our project is making the transition to the cutting edge Agile methodology (hello, 2005 called).
From what I see, I'm starting to believe that we're also changing our target from delieverin software to deleivering meeting botes and meeting preparation docs.

The customer wants to drop Agile in favor of their in-house development methodology. They just sent an e-mail describing it...
I think my team needs a room decorated with cotton flowers and small huts to get into the right mindset.

PM, we are going to go to an agile methodology for working. (despite PM having never done agile, and most of the team having never done agile) But we will have 4 week sprints, as 2 week sprints are too short. We are going to have daily stand ups, oh but we'll only have then once a week... And we will keep the 3 hour mid week meeting. Oh and we'll keep our existing JIRA, but you also need to use *new* JIRA as well, but that's going to the customer so don't post bugs on it.... (all with a ln important delivery in a few months) The suggestion of getting an adviser (either internal or external) who has experience with agile to help us transition smoothly and provide best practice got shot down. feels like the blind leading the blind...

A project that doesn't follow any kind of development methodology will always be delayed

"We follow the AGILE methodology."

A fancy way to say :
- We mostly work on tight deadlines.
- We will come with last second changes.
- We have little/no overtime payement policies.
- We will ask you to do basically anything even if you said explicitly that you don't know how to do it.

I’m currently working 2 jobs with over 60 hour work weeks in addition to my own SaaS company.

One job is full-time 40 hours, where I am a mid level developer and I just do the waterfall of tickets that is assigned to me. This place is unorganized and has almost no communication within the team.

The second job I am the Senior Dev and project lead. It’s a contract position that I put 20+ hours in on the evenings and weekends. Agile methodology, with a modern tech stack and I promote excellent communication as well as documenting everything.

I’m in a unique position because I’m able to see these differences and compare them side by side. My full-time job doesn’t really know about the second job. I get my work done, and that’s all that matters. This place is a mess. The project lead (CTO) is a helicopter boss that sticks his nose up at any type of formal documentation and practices. No tests are written.. no SIPs or deployment docs.. no stand ups or anything. I must also mention this team has 5 developers and a QA.. my team is only 2 developers and a QA. We get through tickets much faster.. it helps when I go over every single ticket that is created and add requirements and images..

I guess my point is... I’m about to be a full-time contractor because I can’t take this unprofessionalism anymore.

Just because these formalities technical take longer. It does decrease actual time spent developing a project. Spending a couple of hours on tests and requirements can save you days of back and forth in the future. Not to mention... document.. everything.

"20/80" working methodology. It never goes down well. Its usually 20% done, 80% shit

What is your faaavorite Software Development methodology?

Scrum, Kanban, ..

Apple's methodology:

Hmmm this seems like a bug...No worries, we'll call it a feature and no one will ever know!

Big up front design with no requirements, waterfall methodology a distributed team around EU. Falling always behind schedule, software is bad, but everything is going OK

What do you guys think is the best method to teach juniors web dev? What are some things that would make you love a uni class and learn it?

I am teaching web dev and I find it very hard to engage all the students as almost half of them are not interested and I think they see the class too difficult(web basics?!). This is my first class teaching and I want to gather some feedback here and implement it in my class.

So, basically let me know of anything that makes you love and hate abclass because of the teacher's methodology. Thanks a lot

Well I'm back on this stupid project with this stupid Product Owner and I really hate this, it really demotivates me.

I was assigned to this project (data analytics) for like 6 months, working alone with this stupid PO that knows nothing about team management or project management.

The guy had a "methodology" where he established all task to be done daily and would not tell me what we have to do in the entire project but instead would tell me day by day all the tasks to be done in each day. This means that HE was the one making the time estimation which is plain wrong!.

Anyways, I talked to him and told him that I need to have a wide overview of the project in order to be able to make a good time estimation, and it kind of worked.

But the guy is a pain in the ass, calls me every 4 hours to "talk" about the project and texts me every hour to check "how are we doing?".

This project was killing me, I had no motivation to work on it, I hated every minute of it, I didn't like it at all to the point my boss (not him) talked to me and asked me what was wrong with me. I told him: This is not the project for me. He told me: Ok let's try to move you to another project.

After six months of agony, the project was stale (customer approval, paperwork, blah, blah) I was assigned to two other projects that I liked, more software architecture and development, not data analytics.

And last week my boss came back to me with "well, the project was approved so we need you back at it".

WHAT PART OF I'M NOT THE RIGHT GUY FOR THIS PROJECT DIDN'T YOU GET?

Now I'm again with this dude, calling me, texting me, sending me infinite emails, asking for minutely updates...

I really don't want to be working on this project.

in agile methodology, have a daily session of 3 hours code review in which he will understand my code.. 👿

That moment when you realise that your boss is not understanding anything about development and cancel all features... :|

You work in a team, for a team to move forward successfully the team should work in sync. A team always has a goal and a plan to get to it. There are times when the team needs to take a different direction therefore the set path should always be available for change because our environments dictate it.

We all have different styles of working and different opinions on how things should work. Sometimes one is wrong and the other is right, and sometimes both are wrong, or actually sometimes both are right. However, at the end of it all, the next step is a decision for the team, not an individual, and moving forward means doing it together. #KickAssTeam

The end result can not come in at the beginning but only at the end of an implementation and sometimes if you’re lucky, during implementation you can smell the shit before it hits the fan. So as humans, we will make mistakes at times by using the wrong decisions and when this happens, a strong team will pull things in the right direction quickly and together. #KickAssTeam

Having a team of different opinions does not mean not being able to work together. It actually means a strong team! #kickAssTeam However the challenging part means it can be a challenge. This calls for having processes in place that will allow the team members to be heard and for new knowledge to take lead. This space requires discipline in listening and interrogating opinions without attachment to ideas and always knowing that YOUR opinion is a suggestion, not a solution. Until it is taken on by the team. #KickAssTeam We all love our own thinking. However, learning to re-learn or change opinions when faced with new information should become as easy to take in and use.

Now, I am no expert at this however through my years of development I find this strategy to work in a team of developers. It’s a few questions you ask yourself before every commit, When faced with working in a new team and possibly as a suggestion when trying to align other team members with the team.

The point of this article, the questions to self!

Am I following the formatting standard set?

Is what I have written in line with official documentation?

Is what I am committing a technical conversion of the business requirement?

Have I duplicated functionality the framework already offers?

I have introduced a methodology, library, heavily reusable component to the system, have you had a discussion with the team before implementing?

Are your methods and functions truly responsible for 1 thing?

Will someone you will never get to talk to or your future self have documentation of your work?
Either via point number 2, domain-specific, or business requirements documentation.

Are you future thinking too much in your solution?

Will future proof have a great chance of complicating the current use case?

Remember, you can never write perfect code that cures every future problem, but what you can do perfectly is serve the current business problem you are facing and after doing that for decades, you would have had a perfect line of development success.

So, I just (few hours ago)made a new variable that's either brilliant or innately flawed... not sure yet. It's an oddly unique var...

__bs__

So far I only made it in python and windows env (i script like the methodology of css).

I bet you're wondering how I've defined __bs__ and the practicality of it.
__bs__ is derived from a calculated level of bullshit that annoys me to tolerate, maintain, etc. as well as things that tend to throw nonsensical errors, py crap like changing my strings to ints at seemingly random times/events/cosmic alignments/etc or other things that have a history of pulling some bs, for known or unknown reasons.

How/why did this come about now?

Well I was updating some symlinks and scripts(ps1 and bat) cuz my hdd is so close to death I'm wondering if hdd ghosts exist as it's somehow still working (even ostream could tell it should be dead, by the sound alone).

A nonsense bug with powershell allowing itself to start/run custom ps1scripts with the originating command coming from a specific batch script, which worked fine before and nothing directly connected to it has changed.

I got annoyed so took an ironic break from it to work on python crap. Python has an innately high level of bs so i did need to add some extra calculations when defining if a py script or function is actually __bs__ or just py.

The current flavour of py bs was the datetime* module... making all of my scripts using datetime have matching import statements to avoid more bs.

I've kept a log of general bs per project/use case. It's more like a warning list... like when ive spent hours debugging something by it's traceback, meticulous... to eventually find out it had absolutely nothing to do with the exception listed. Also logged aliases i created, things that break or go boom if used in certain ways, packages that ive edited, etc.

The issue with my previous logging is that it's a log... id need to read it before doing anything, no matter how quick/simple it should be, or im bound to get annoyed with... bs.

So far i have it set to alert if __bs__ is above a certain int when i open something to edit. I can also check __bs__ fot what's causing the bs. I plan to turn it into a warning and recording system for how much bs i deal with and have historical data of personal performance vs bs tolerance. There's a few other applications i think ill want to use it for, assume it's not bs itself.

*in case you prefer sanity and haven't dealt with py and datetime enough, here's the jist:
If you were to search any major forum like StackOverflow for datetime use in py, youd find things like datetime.datetime.now() and datetime.now() both used, to get the same returned value. You'll also find tons of posts for help and trying to report 'bugs', way more than average. This is because the datetime package has a name conflict... with itself. It may have been a bug several years ago, but it beeb explicitly defined as intentional since.

* Automated Technical and Fundamental Expert Advisor trading in MT4 with Python dealing with RSS News Feed on the Financial Calendar
* Food decision/recommender/randomizer app
* Food decision/recommender/randomizer bot
* Personal Companion set up on Raspberry Pi with Jasper AI, buy BrickPi and Lego Mindstorm to make it a friendly moving robot
* Cardboard fort for my kid
* A 3D game that involves hacking with drama storyline (inspired from Mr. Robot) and publish it on Steam
* A SaaS app like Tinder that matches would-be Project Managers with Devs to push Devs to finish side projects that we have and push Project Managers to use whatever PM techniques and methodology (Six Sigma perhaps)

And so much more... Ughh.

What software methodology do you work on your pet projects?.. I'm a newbie and I'd like to get some rough ideas..

scrum my ass! the whole company(especially the marketing) must be aware and agree with this methodology and not only the devs.

1 - Correct me if I’m wrong, but in true Agile, a product owner ought to be able to interact directly with the dev team, and vice versa, in the card/conversation/confirmation process of creating, estimating, and executing the user stories, correct?

2 - If Company “A” contracts with Consultant “A” to have software developed, and then Consultant “A” then contracts with Company “B” who then contracts with Consultant “B” to do the development, who would you define as the Product Owner?

3 - If Company “B” is barring Consultant “B” from talking with Company “A” and Consultant “B”, is Agile even possible?

Does rapid application development methodology leads to more technical debt compare to other ones? With a factor like deadlines, a small number of team etc? 🤔

So I'm target multiple platforms with one of my c++ projects and on one of the platforms I the window manager is quite different, and one of the libraries can't be used. Thats fine for my needs, I'm just wondering what the typical way to allow for these differences is. Basically currently I've created 2 "main" files that have preprocessor code to only use he one that's right for the platform by having ifdefs at the beginning of each, I've kinda followed that methodology for the other files that are totally platform specific also. Is there a better way to go about this? Currently using msvc for windows compilation and a gcc-esqu compiler for one of the other platforms, where the compile command is built by a home made build tool.