I don't know what line of IT work I like

Did you recently graduate? If this is your 1st job then it may be boring but it is probably good for experience and then later on you can go and apply for another job which you'd like more as they'd be more willing to accept you.

Yes, I recently graduated but it's my third job - a very boring one at that. Yes, it's good for experience and yes, while I'm doing this job, I'm studying other libraries on the side and perfecting my web design and web dev skills so that I can land a more fun job.

Have you considered a career as a Microsoft Dynamics Consultant?

Yeah in work, when you're a dev, you don't have much power or a say into what task you're given or sometimes how you do that task. Its all about story points in agile sprints and how quickly you can ship a feature or product.

Unfortunately I know of companies who work like that, but it's usually a contradiction. Companies who work like this really aren't "agile" - they just tell themselves this, either because they don't understand their own problems or they don't really care and want to pretend to developers that they know how to deliver software, but it's often an ongoing saga of endlessly repeated disasters which results in fewer features being shipped and people wasting much of their time on tasks that don't really achieve anything.

Companies who really know how to deliver software (they do exist!) are the ones who fully empower their development team to be involved in the entire process, and put their concerns at the centre of decision making, encouring them to work collaboratively with the rest of the business (especially BAs and QAs), rather than sticking them in boxes and telling them to churn out features all day, following mandated processes with no real involvement in the bigger picture.

The irony is that cherry-picking various concepts from scrum/kanban/etc without actually putting the focus on the people involved in building the software ends up being extremely inefficient, slow, costly and unreliable in terms of sticking to software delivery goals, because it essentially means that the business hasn't grasped what agile really means, ignores the real problems, and never really addresses the things which actually go wrong.

Actually, companies who really do follow 'agile' don't do things like this, they put people first, and they fix problems, and they're usually a lot better to work for because they usually get things done, and people involved at all stages tend to be more engaged and happier as a result. Unfortunately, many companies follow "false agile" and end up instigating more heavyweight processes, checks and balances, documentation, and other anti-agile policies in an attempt to fix the problems, But the reality is that any environment which essentially treats development as just a step in the whole delivery process probably isn't going to be very good at delivering things.

Yea, I would agree with most of what you said. However some bits are abit too pessimistic? Where are you getting all of this (mostly correct) insight from?

I don't know what line of IT I like but I'm still discovering it.

Here's my current problem:

I'm not sure if many can follow my train of thought but here's the thing I hate about modern software development for your average mid-sized company:

- business code, business rules, enforced corporate rules, complicated software patterns and brain-racking business algorithms. Pure numbers, pure logic, etc.
- You have to use the libraries the company wants
- The company even makes fun webdesign boring. You can't just start and code some fun pages. Noooo, you have to adhere to some fad like TypeScript, SPA, SEO, deal with maintenance headaches of using tools like Bower, Grunt, Gulp,.. bah. Just let me start with the fun stuff already.
Just the word business makes me feel sick. I don't like words like clients. All this corporate, forced mumbo jumbo. Back in the 90's web development was more fun. Needless to say, I hate back-end development, or even better: I hate forced, business-driven software development.

I'm not the only one who thinks this way. Like me, my classmate who graduated with me wasn't very good at coding either and he chose to pursue a career in Testing instead and it seems to have worked out for him because he's a much happier person now than he was when he used to work in a previously boring job where he was tasked to maintain boring, rigid database structures for the food sector.

Don't get me wrong, I like structured and clean code but, for example, at my job as a back-end Software Engineer I don't have freedom to code as I want. I know this is how the business world works but I'd rather work in an environment where I'm not barked at for not adhering to company-wide coding standards.

What I want is: I want a fun place like Google, where there are tons of oldschool or fresh, bright, and fun young people. I'm not an ageist but being trapped in a company full of people who are either close to retirement or near their 40's sucks the life out of me even more so than the boring job does by itself.

It works in funny ways. When I worked in Systems Administration, I was eager to touch anything that involved providing a quick code solution. Now that I'm working in Software Development, I yearn Systems Administration.
I think there is a fine line there; I'm starting to see that what I love is scripting rather than programming and I also love webdesign and UX. Just don't give me a boring back-end job where I have to program boring business models for boring sectors such as the food industry or whatever.

I find true joy in having a problem at home, say, fetching a stream link from a streaming website using JS + nodeJS or Python, or even putting a neat frontend onto it like a .NET or Java GUI, so that I can do it the GUI way. It's fun to test my own stuff this way for some reason, probably partially because I'm not restricted to boring things or boring rules.

Can anyone relate to this?