I took that same vow years ago!

But I still break that vow every morning I go into work and renew it as I leave for the day.

@castor-rg Yes, I use OneNote to informally document the original purpose of a project, why no TRD nor spec was written, why management changed their mind, shortcuts taken to accommodate redesign, all emails related to project, and any configuration setup I had to go through to set up my dev environment.

I originally wanted a Wiki for each project, but Project Management saw no value in "documenting executables", so OneNote it is.

Are all meetings from the same company, or multiple companies throughout your career?

Good for you for trying to convey a very real issue to your PM. An issue which is often underestimated by non-devs.

At the risk of sounding incompetent, what is a "live bucket" and why does it contain generated files?

Is this similar to a production web server having all files accessible when a user goes to a root URL?

Yes!! This should lower the barrier to entry for using .Net Core!

This is so true it hurts, sometimes I think our office should just have a private Twitter network.

That is one of my fears. Multiple drawn out interviews only to be rejected at the end due to salary constraints, even after HR/Department director already agreed to a minimum.

When performing interviews, I try to keep coding challenges less than an hour and a half (for both the candidate's and my patience).

Good luck next time!

Wait till you have to maintain a legacy code base where someone created their own DateTime library that must talk to backend vendors that use industry standard time_t or DateTime objects.

If you think managing time across time zones and various languages is bad, wait until you cannot even trust a seemingly regular time keeper algorithm.

Holy hell.

@Vaibhav7909

Not necessarily, a lot of people have tiers.
A quick search shows some students charging $50. And some devs charging $250 for enterprise level solutions.

https://fiverr.com/bilalhassanqadr/...

https://www.fiverr.com

The site works more in favor of the client instead of the developer due many competitors are overseas devs willing to work for cheap.

Having a portable solution to get my coworkers and my dev environment auto-configured to just work without any of the pain in the ass set up.

Examples:

- IDE
- IDE plugins
- environment variables,
- class paths
- JDK
- Correct versions of Python
- Net framework
- runtime libraries
- .git ignores
- the first git init being at the correct folder depth-level
- Appropriate active directory permissions to not have to fight the tools
- At least two browsers.
- SQL server instance properly created
- etc

VMware snapshots and Docker are good enough for some scenarios, but emulated environments have limitations. For example domain credentials decay from time to time and you will have to establish trust with the domain controller again.

Another example is that those don't help me when I have to teach SCM how to build releases on their non-emulated production servers, which often entails me having to remember one-time checkboxes and other options I did months ago at the start of the project.

I've learned two important things as a dev when it comes to money.

1. You are never paid what you are worth. You are paid what you negotiate. You need to be honest with yourself from the beginning with what is the least amount of money you would be willing to accept a position for without guarantee of bonuses or raises. This way, you are financially happy and anything else is just a welcome surprise. Asking for more money after negotiations and getting your foot in the door can seem tacky to management.

2. The only real way to get a pay bump, is to leave or to be willing to leave. Unless there was a significant role change involved with a promotion or change in responsibilities (such a senior engineer quitting and you having to additionally take on that role), management isn't going to do you any favors. When you give your notice, the manager may let you go immediately to avoid proprietary theft, may assign you to write documentation for knowledge transfer, or counter you with $$.

Looks like it would be a literal pain in the ass.

Anyone who chooses to become a dev because of the craft and not the money. Those that care more than just the immediate "how", but to truly desire to understand the workings of a system or framework.

Typical Problem Googled:
"How do I marshal an unmanaged C++ DLL into my C# application."

The person above just cares about solving the immediate problem. Which is completely acceptable.

Developer wanting to understand:
"Why are C++ and C# dlls considered to be different? Since DLLs don't have a main, are they loaded into their own memory space or share memory space with the process using it? If I remove a used DLL, will applications crash immediately on startup? Or will everything work until the function in the missing DLL is called? Does it make a difference if it's C# or C++ dlls? What is the delayed DLL loading feature vs the default loading behavior? Why are DLLs placed in a GAC?"

Sorry for block of text (char limit). But the latter people are my heroes the inquisitive devs.

I got halfway through creating one, when I realized.

"Nobody but me is going to read this shit."

..

"I don't even think I'm going to read this shit."

..

numUnfinishedProjects++;

@Berkmann18 they were probably not hacked at least 99 times

... or they do, and management begins to understand the implications of accruing technical debt, such as cutting your sprint or not giving you enough sprint time to finish adding real authentication because:

"The web app already does all the features we want it to do with your latest update. Why are you going to spend another week on it if it isn't going to do anything different?"

And then your "dramatic" explanation of client/server side validation falls on deaf ears: cleaning up debug code, adding try/catches, sanitizing input, or explaining how a user manipulating the DOM, URL, or query string could circumvent or crash everything.

Unfortunately, management tends to not care until they are forced to care. That is how my employer's QA department came to exist.

My technical manager told me not use lambda or LINQ expressions because it's hard to read during the code review.

I tried to explain the optimized benefits of lazy loading, and improved readability due to declarative-like syntax and reduced if-statement clutter... but that went about as well as I'm sure most devranter's would expect or personally experienced.

You know, like when trying to explain the technical advantages of an approach to a manager who has already made up their mind about a subject matter they don't understand before the conversation even started.

@BikerMouse Then you are about to be very motivated by linker errors, preprocessor errors, pointer errors, memory size allocation, null terminators, functions that return void but mutate your data, and functions being organized by files instead of classes.

I only use it for developing offline iOS apps as I am a Windows dev at work.

I've considered making OSX applications from time to time, but I always find reasons not too. Either the UI desktop application is better served in Windows to make my colleagues and my day-to-day job easier, or I can make a web application that serves both platforms.

In the end, it is about use cases and the number of potential users.