* Figure out how to write AI for games. A simple example would be, how to write a bot that finds shortest path out of labyrinth.

* Check out graphics programming

* Try to see if low-level programming is for you: kernel level, GPU, OS

* Check out infosec industry, there should be a lot of fun there: malware analysis, penetration testing, etc

* Machine Learning: tons of coolest stuff. predicting, classifying, reinforcement learning, neural networks. Check out Kaggle machine learning competitions.

* Checkout competitive programming sites. My personal favorite is hackerrank.com, but other popular ones are topcoder.com, codechef.com, codeforces.com. Try doing challenges for a couple of weeks you may find that you learnt as much as you previously learned in a year. Also through it you may get interested in particular algorithms and fields.

* Distributed programming, system engineering. How to build systems at scale? How to process tons of data in parallel.

If you don't seek for the new challenging things to do that could improve you, then you will find boredom and burn out in any field.

There's nothing unexciting or less complicated or challenging about producing good CRUD [sic] applications.

I don't understand the industry cynicism towards producing good quality "bread and butter" software for any vertical market.

It takes years of experience to learn good (relational) data modeling.

It takes years of dedicated attention to assemble tried, tested and efficient user interface designs that your user community loves to use on a daily basis. User interface design (and yes, we are talking about your "boring" invoice capture screens here) may seem easy at first glance to be dismissed as unexciting, but almost every real world example is a challenge that requires creative thinking. Many are implemented badly.

It takes hard knocks experience to add gems of strategies to your repertoire of "boring" reporting solutions. Producing industrial volumes "TPS reports" may sound boring, but architecting reliable and efficient reporting solutions is hardly easy.

Another challenge of the "1 inch deep and 1 mile wide" mental specter associated with "CRUD" apps is managing the challenge of excatly that - the 1 mile wide sprawl. Each CRUD app may be simple and boring on its own, but how do you manage several of them on one site such that each one not only operates efficiently with its own specialisation but also as an integrated whole with others? These are not simple or by any means boring.

I love CRUD apps. I love seeing different CRUD apps in specialised domains and how similar concepts of the CRUD world manage to solve specialised needs of a particular niche.

Fascinating.

:-)

So while getting "the damn thing up" may be the burning expectation in everyone who isn't making the wall, the wall maker knows the consequences of poor work and it is his responsibility to educate folks who depend on said wall.

A billion times this! In retrospect, it's kind of funny that at my previous engagement, I was doing things which were kind of unusual to me and yet I was feeling bored and depressed. Now I'm back squarely in the CRUD world and learning so much. It's one thing to write applications that perform these tasks, it's a whole other ballgame to make those applications performant, scalable, and a delight to interact with.

But how does this tie in with the manager who says 'it's just an invoice screen, why are you taking so long' probably based on the mentality that $ revenue is proportional to # features.

Obviously the problem here is the manager, not the fact that you want to write and build quality work. Especially if they run on flawed assumptions such as "the mentality that $ revenue is proportional to # features".

You can't build quality under shitty management like that.

There's markets and jobs for both types: some desire cheap & shitty, others are willing to pay premium for solid, beautiful & well-designed.

Also, I've noticed many end users are not confident to comment on what they believe is an inefficient interface. So, problems with user interfaces are not spoken openly unless the interface completely blocks the user from completing his/her task. It takes some amount of permission-giving from the developer's side to get valuable feedback that would otherwise not be spoken about.

The exception to this is in situations where the market is being disrupted. For example when the iPhone 3g came out it just made any other hard-to-use smart phone look like shit. And thus the competition was forced to catch up.

However in enterprisey applications we are a long way off that. The awesome invoice screen may add value to the customer, but not much if none of that will be captured by the provider of the software.

Unless a certain class of invoice screen is on the list of must-have things the buyers must have, because it is a particular pain point. In which case you will be told by the pointy haired boss to make it awesome, it won't be your choice as the developer.

Damn I sound cynical!

Your point about users is spot on, and we have all been such users. I mean you have used MS Word ... right? And often at work we have to use such applications. We just push on through. Users that are not programmers may not even know to question it, they assume that is the way it is unless they have used a competing product.

Along the way, you might find {activities, collaborators, products, ideas} that get you really excited. And since it's not "pure software" there will almost certainly be lots of opportunities to have a major impact! Software is eating the world, and almost every "non-pure software" activity is hurting for good programmer help.

That's great! Many of us have done the other way: approaching programming via robots. If you are tired on programming, do something that moves AFK: create a robot. You can start from small. There are hundreds of people sharing their insights so you can learn fast and do your own. Try here: letsmakerobots.com

Francisco

After some time, these challenging stuff have the same problem, being mundane. Specially constraint of work environment and people you have to deal with. Plus some of the "coolest stuff" just blows up with overfitting and seems to be a mere hype to me.

The wonderful thing about our line of work, especially these days, is that it's so easy to find projects, learn about them and participate. It just takes time and perseverance :).

Tools are just that - they are tools. Granted, there are many of them, new and shining, coming in all packages, but that gets tiresome after you've spent a substantial period of time with them. They are all essentially the same and sooner or later you lose interest in them.

What never gets boring is using tools to create things that affect people's lives. And I gather from your message that you've missed that joy.

My advice is simple. Think of some thing that would be helpful to (non-technical) end users. Come up with some kind of service that would solve even a small problem for them. Then see your eyes light up as people are adopting your offering and giving you their thanks.

In short, your work must have a meaning. You should know that somehow what you do improves the world we live in, even if in a small and seemingly insignificant way. For as long as you're just finishing tasks prepared by somebody else for somebody else's meaningless projects, you're not going to be happy. As with all creative professions, in programming too you have to take matter in your own hands.

You've just realized (subconsciously) that your work has been meaningless. You basically need to find your path. What you could do:

- Forget about the tools, just pick up something you're comfortable with and create something useful for people

- Change jobs until you find a project you can personally identify with and where you'll see you work affecting the outside world in a tangible way

- Change profession or role to the one where your need for meaning will be satisfied

That's hard I know. I wish it weren't but it's just the way things are in life.

It can also be something of an intra-life crisis. For some reason 34 hit me really hard. I think part of it was that suddenly I knew that there was some things that I had considered "something I'll do some day" were probably off that list, permanently. Like a friend of mine who realized he wasn't going to ever be one of the world's top jazz musicians. (for me it was being an astronaut) And the realization that this is "all" there is, you live, you experience life, and you die. There is no "win" there is only great times and not so great times. All of that came down pretty hard on me in my 30's.

My coping mechanism is finding something new to learn, but that certainly doesn't work for everyone.

Some other ideas:

- Spend your free time (and take some extra time off) to do something new non-computer related: gardening, mountainbiking, climbing, etc. Sometimes, computers are just work (until you have more inspiration), which is ok - it pays the bills, find the challenge somewhere else.

- Try some vipassana meditation classes. It can be really insightful to see how the mind works.

- Take a year off, travel the world (relax a little before a real burn out hits you).

- (If applicable) Start a family :). We have a 1.5 year-old daughter, it's great to just watch her play, going for a walk in mountains with her, etc.

If not Virgin Galactic there will be another company.

[1] Not exactly epic experiments though, I recall that one of the sillier ones was tie two fans together at the base, with their blades facing opposite directions, and see how fast it would spin.

I totally agree with you. Technology for the sake of playing with technology gets stale after a while.

The software industry loves re-inventing things and attaching new labels. You are absolutely correct that regardless of what language/paradigm/methodology you use eventually every program results in machine level instructions being executed. In some cases less efficiently than in other cases. It's not about the program, it's about the problem being solved.

Only you can decide, based upon the other comments and preferably after competent medical advice, whether your situation is a case or burn-out, depression, mid-life crisis, etc.

Assuming that it is none of the above, then you might want to consider finding a "real world problem" and using your knowledge and expertise to create a solution for it. If you can't find any worthwhile problems (yet) then go travelling! It will open your eyes to a massive, colourful, complex REAL world out there with its myriad problems. Sooner or later you'll find something you care about enough to want to solve.

Champion the cause of code that's legible - and that doesn't mean covering it in syntactic sugar. Legible code makes it damn obvious what it does and how it does it. Sometime find the "power take off" for a tractor ... that's what you're trying to do.

You can also champion the cause of not fixing that which is broken. There is also fun to be had demonstrating the technical debt is real debt and it does need to be paid back.

Much fun introducing peer review, too.

Get yourself, your team or whatever to sit next to your damn customer. Have them look at what you're doing at least once a day so they can say "oh, no, not like that" before it turns into a $100k fuckup.

So, yeah, you've just got through to the next level. It's not the software that's the challenge, it's the people.

Well said. The customer is the final and only arbiter on our disagreements about tech tool choice, style and architecture. In front of the customer, all our internal arguments look and sound like those of immature, spoilt and unfocused professionals.

Add to that that many IT professionals dislike getting advice/input from non-techs and you see why we have so many broken systems out there.

So I'm reading maths and physics now. The joy in my life is actually from taking things to pieces and seeing how they work and there is plenty of that there.

For more of being with you, my company drank the microservices kool aid. Rather than concentrate on building a quality product we've got buzzword soaked boiled shit that doesn't work properly. There's nothing wrong with microservices in principle but they lack the talent and experience to pull it off. So there I am, a doomsayer, a figurehead on a ship of fools.

Edit: Just to add, I work for liars and a personality cult and that is the root cause. Why don't I leave? Money is amazing and that gives me the freedom I need.

I don't mind when a company I join has some awful code - it sucks to work with at first, but it leaves me never bored since I can make my mark improving it and learn while I am at it. I work to schedule fixes to go along with feature development & try not to worry beyond that. There are many things to do in life, most not involving programming. I rather run with friends, travel & visit places with friends, research & code whatever I want without work pressure, play video games, and just overall have the freedom of choice.

I hope the OP hasn't fallen into this trap.

I wanted the income and less hours and demanded it. They said no, so I automated most of my responsibilities and do a 25-30 hour week anyway. I work from home and most of my job is thinking and that's non-deterministic.

You only live once (I shudder saying that but it's true).

Don't fall in love with a tool, fall in love with using the tool to make the world a better place. If you are not making the world better, then you are missing the whole point.

I've just been back at a desk for 4 years, but am again burnt out so now I quit again, and I'm driving around Africa for 2 years starting in a couple of months.

Get out and live, I say!

[1] theroadchoseme.com

I honestly felt like I was spending money to live, rather than to die slowly by going to work.

I spent roughly $1200 a month on the trip [1], and prior to leaving, simply to go to work every day in Calgary I was spending that much monthly. So it really was a great feeling to be spending no more money, but to be really alive every day.

[1] Full breakdown - http://theroadchoseme.com/the-price-of-adventure

Reason I mention this -- RE save my arse when I reached your level. Easily replaced the coding income, even though I was consulting in my last few years for $120 to $400 per hour.

I have friends who could not get hired in their 40s. At that time, I had not had a regular job in software for 10 years. I'm now 20 years past my final full time job and just making tons of money in Real Estate. Unlike coding tools, the tools you develop to purchase and manage properties does not get rotten like vegetables at Safeway.

Let's face it. We're some of the smartest folks on the planet. Do you Really think any of us can find intellectual stimulation after many years of doing the same thing? Very few of us can.

Do something different. RE is different and will replace your income.

> I have friends who could not get hired in their 40s.

In the software development field, this is just plain BS. Of course, your friends "who could not get hired in their 40s" may not be in software development. My apologies if interpreting your statement led me to an invalid conclusion.

What you get:

* Family who is waiting for you at home

* Happy weekends

* Rest, visiting places with them and take a rest

and lots of other things, also visit your parents, make them happy, remember about old days and be with them

P.S: I am not native speaker, probably made lots of mistakes and my text sounds like robotic, sorry

http://cliki.net/Getting+Started http://www.gigamonkeys.com/book/ http://mitpress.mit.edu/sicp/full-text/book/book.html

And no, it's not yet another language, it's that feeling you have had all your life. That feeling that something was wrong with the world. You don't know what it is but it's there, like a splinter in your mind, driving you mad, driving you to me.

A couple of years ago I've read about Lisp, and I started picking on it. At first I didn't get whats the point, already knowing Java and C. But months later, I got a course in which we used Haskell. And then functional programming started to make more sense.

Recently I got interested in Lambda Calculus, which is in the same branch of functional programming. And for me its amazing, seeing this different languages. And also making contrast with imperative or OO programming. Cause they are different way of expressing, each with its own advantages/disadvantages.

And there's also prolog, which I plan to pick up next...

So my point is, I personally like to learn about other languages. I have colleague friends who told me, "But why Haskell, what is it for?, I can do it in Python" "You can't do real-world applications with that", things like that. And for me, it's about learning, it's not only "what is popular" or "what will get you a job". It goes beyond that.

Somewhere along the way I started to regain some of my joy in technology (mostly I realized how much magic I have at my disposal compared to most people who can't program, can't build/deploy/administer servers, etc.), and have begun several new projects and begun to refocus on my primary project/business in a manner I haven't been able to do for a while. I moved into a regular house a year ago, but decided I didn't like it, so two days ago I bought an old Avion travel trailer (one of the shiny silver classic kind) and will be moving the rest of my stuff into it tomorrow.

I'll be hitting the road again...but, will do so in a way that enables me to be connected to tech more deeply, rather than almost completely disconnected. I'll spend some time in Silicon Valley, will catch several relevant Open Source conferences, etc.

I'm not telling you to buy an RV and travel from Alaska to southern Mexico for four years. But, it worked for me. Maybe a major change really is what you need. If you've been reasonably successful with your tech work, you probably have some flexibility in what you do, at least for a little while. Make use of it. I wound up quite broke in the process of all this, so maybe don't go as far off the reservation as I did; that may be part of my impetus for getting back into tech with such gusto...money comes so much more easily for tech work than any other work I've ever done (maybe partially because I'm so much better at it than any other work I've ever done).

This said, you are right on most points. Most people want to contribute in changing this world, make it a better place, etc. You apparently lost the meaning of it. There is alot of noise, new things, but what for ?

My feeling is that if there are people who like creating new things, we also need people calling back to simplicity. And I also think that simplicity trumps all in the end. Your perception of the ambient noise and how the things can be made simpler is a gift. You could find a meaning for your contribution to software/programming in this.

Software, computer science, can be your ticket into whatever industry you want, whatever interests you, because it all needs software.

So think about what's interesting to you in the world. Aircraft? Aerospace? Trains? Medicine? Medical devices? Business? Movie making? Publishing? Oppressive scheduling algorithms managing on call jobs in the legal slavery known as retail? Shipping logistics? Law enforcement? Surveillance? Human rights? Gambling?

Man, the world is infinite for all intents and purposes, and you get to participate in any part of it you want. Raise your head up from your tools a bit and look around.

You need to realize that what you think is not the source of your feelings, even though it seems like it.

It's actually the other way around. What you feel dictates what you think about the stuff you have contact with in life.

If you are sad, you start thinking hopeless thoughts about what you do, about who you interact with. Those thought seem objective and you are led to believe that they are source of your feeling because they deepen it.

But that's not the case. The source of all this downward spiral is the feelings.

To get out you need to do things that are counter-intuitive to you. Stop reading. Don't drink alcohol. Cut off the things you were doing to comfort yourself. They are not working. Force yourself to find new ones. Meet new people that are passionate about the things you have no idea about, listen to them, go outside into the woods and be bored. Run. Take many hour walks preferably around some trees. Basically do all the physical stuff that was found to reduce depression. If you have a partner, interact with her, listen, agree, do things together, don't worry you are bored and faking it, just perform well. When you make her feel better she will make you feel better a little bit.

Realizing helps, that actual content of your thoughts is virtual because it's induced by the way you feel. If you felt better you would think completely different thoughts about same things.

I don't mean this as a put-down at all. Any time I hear so ething like that it usually means the person saying it has been wearing blinders for a long time and has no clue what else is out there.

How about this: Go figure out how to make a machine really think. You could devote a lifetime to that alone. Then, if you succeed, figure out how to use it to help doctors and researchers diagnose patients and/or find cures for diseases.

One thing that really re-ignited my love for technology (not that I lost it) was to become a mentor for our local FIRST FRC team. Experiencing the discovery, passion and excitement of technology through the eyes of a bunch of smart kids eager to learn is really neat.

In any case, I think that you'd have a lot in common with David Heinemeier Hansson. You can see in this video https://www.youtube.com/watch?v=lBfVxBj61z0 and a lot of his blogs that he approaches things in a much more realistic down to earth manner than many other engineers out there. I think that if that's what you want, then it's all a matter of finding the right company that thinks the same way about using technology to solve real problems.

https://www.youtube.com/watch?v=UZGS_IOPZpk at 25:18 - "People always ask, thats always the next question. Will that scale if you have a 100 people? I don't give a fuck. Because we don't have a 100 people". GOLD.

[1] https://vimeo.com/74338272

[2] http://www.amazon.de/Start-Small-Stay-Developers-Launching/d...

The software industry is very trendy and it's amazing how people can be smart enough to program but don't care about simplicity, it's almost as if being smart-enough leads to boredom which leads to technical churn. Which is why there's so little technical innovation.

The worst kind are those who think technical innovation moves at a fast pace because of their startup's efforts, rather than the glacial pace it does in reality.

There were two things that helped me clear my head a bit - going to the gym and focusing on my well-being (a.k.a. actually going to a gym 3-4 times a week) and learning something outside of computers (in my case, learning the Japanese language). I think just focusing for a bit on something more than computers can help you take a step back and gain some of that lost energy back, at least it did for me.

Life is bigger than your job or your immediate interests. Take a break. Travel. Challenge yourself. Break out of the circle that you don't like and find something else, even if it's just for a short while. That's what I usually do. At the very least you'll find something else to rant about, and maybe eventually realize that things could be much worse.

I'm sitting in the kitchen writing this staring out the window at a nice juicy tomato with my name on it. I'm having it for lunch in my sandwich.

You do have to get used to failure. For example, it's July an my butternut plants are only 2 inches tall an have no chance of fruiting ever.

Thing is, it's pretty easy to code for a machine. It's REALLY hard to program in a way that other developers can understand you. And, like in literature, using less words to describe something is more often better for the reader.

"Too much jargon, falsely claimed software engineering practices and overly zealous object oriented mentality"

I used to hate all the jargon too but then I realizes it gives programmers a vocabulary to discuss things. When everyone understands the jargon, it makes discussing complex solutions a lot easier. OO can definitely be overused, but honestly 99% of the problems I face are people just writing unmaintainable, procedural code. You're right though, OO can often be less simple (harder to read all at once) but that's the trade off we devs need to balance when writing code.

I don't want to sound condescending but is it possible you are making excuses for learning hard things. Maybe it's the people you work with who are pushing it down your throat the wrong way. Maybe you already know these hard things but just haven't had to use it so you're giving up on the ideas. Or maybe I'm still in the cynical phase of my life.

I feel this statement is way too subjective and has been used very often in the industry in a negative way. Just because one does not understand the depth of the problem or style doesn't necessarily mean the style is bad or the solution is bad. I first realized this when I picked up AOCP.

> OO can definitely be overused, but honestly 99% of the problems I face are people just writing unmaintainable, procedural code.

I've seen unmaintainable OO code and maintainable procedural code.

> OO can often be less simple (harder to read all at once) but that's the trade off we devs need to balance when writing code.

And it's often vague when rules of maintainability pops up somewhere and people try to pick that up. Suddenly, it feels like there is no need of "Science" in CS.

> I don't want to sound condescending but is it possible you are making excuses for learning hard things. Maybe it's the people you work with who are pushing it down your throat the wrong way.

May be it is the people but then you have to deal with people in the industry. Not too sure about what you mean by "hard things". The hardest problem I've faced at work was the interview question (in a Fortune 500).

There are also very different paradigms which I find renew my interest. erlang, rlang, golang... you may have to dig to find what keeps you interested.

It sounds like you need something new, something refreshing. Maybe take a break from your existing approaches?

Learn what you want to, work on what you want to. Tackle the difficult problems. We still have very difficult problems in this industry. I suspect you are not challenging yourself enough and that's why you are getting bored.

Take a break. Learn something new, and apply the cross technology knowledge you acquire to new fresh projects. Always keep an open mind, and by all means avoid pointless topics that try to establish the best language, the best IDE and so on.

Fred Brooks, managed the development of IBM's System/360 and the OS/360 in sixties. He also thought deeply about the false claims in the field many years ago.

"No Silver Bullet — Essence and Accidents of Software Engineering" 1986:

https://en.wikipedia.org/wiki/No_Silver_Bullet

For one 2014 take of that, see: Kenneth M. Anderson, 2014. No Silver Bullet. CSCI 5828: Foundations of Software Engineering. Lecture 02 — 08/28/2014:

http://www.cs.colorado.edu/~kena/classes/5828/s12/lectures/0...

There will always be folks eager to be employed as cogs or who try to attain "thought leader" status. That's not really a judgment on those people, since maybe their personality or situation makes it a good fit. But if it's bothering you that you can't go farther from within this lens, find a slightly different one.

I rarely "have time" to do it ... but somehow I always have time to work in circles for weeks or months and not get much done.

A common answer here is "learn something new" and that works for me at first. When "learn something new" isn't enough, I bring out the big guns and go camping. I haven't isolated what about camping does it for me. (I believe Danny Hillis, the founder of Thinking Machines wrote that he would never have finished his dissertation if he hadn't written the first draft at Disney World. Not my kind of thing but I guess it worked for him.)

Good luck!

I found scientific programming: i.e. using Machine Learning and related disciplines to solve hard AI problems. I can guarantee you might get frustrated by lack of success and hardship of challenges but never ever bored.

In case you are interested, this is my blog post when I got inspired by this: http://byterot.blogspot.co.uk/2015/01/future-of-programming-...

He sais that a great job has to offer you great creativity, impact, and control over what you do and how you do it. IMHO this is why so many people are mesmerised by startups. Anyhow, if you miss one or more of these three traits in your current job than you have to find an other one which fits better to you.

Read the book! I hope it will help you as much as it helped me!

[1] https://sivers.org [2] https://sivers.org/book/SoGood

When working for such a startup; the primary focus will be solving your customer's problems. You should work one on one with your first couple of customers. Doing so will be very challenging and if things go well very rewarding both intellectually and fiscally.

Issues of programming languages, editors, infrastructure frameworks will be secondary. But as the company grows, the technical challenges of scaling, reliability, managing teams, feature growth, etc. with will need to be met.

What`s worked well for myself is starting a small niche tech business. We`re small and focused on resolving customer problems. Not bickering over class hierarchy, design rules or other crap thats irrelevant to building products that customers really enjoy.

WHY are you building software? Start with answering that question. Then, do a bit of soul-searching; figure out what truly feels meaningful for you. That's something no one can answer but you. Then go and do it.

If you can't come up with an immediate answer, then start trying different things.

Building a bridge isn't enough. Connecting two communities over an otherwise impassable chasm is.

I was working for an org that turned out to be all about the technology and not enough about solving real known problems.

I mean, if you were on a desert island, would you even want a computer? What would you do with it?

"BOAT" = "Break Out Another Thousand"

enuf said:-)

I stopped thinking of software technology in terms of technologies, but rather tried to think it as a means to help other people. I might be bored by technologies in its own sake, but I'm never bored with the idea of helping others.

I think the good thing is, you don't need to be defined by this. There are a lot of people out there who prize solid planning and skill above gee wiz buzzwords. Find some of these people and work with them. Or if not, start your own gig and grow it.

https://www.youtube.com/watch?v=jN9L7TpMxeA

It bored me. I slowly studied programming and left the civil field for software. I now make as much designing for the web as I did designing bridges.

Life is not a predefined trajectory. It is chaos. Roll where your heart leads ya.

Recognizing "the churn" so often present in our industry is a major milestone in maturation as a person delivering solutions to problems via creating software. The rush many initially experience when exposed to the fact that their thoughts can be reified as programs which dutifully encode their wishes is quite intoxicating. Key here is "initially."

Progression from "I can make a computer do what I want" to "I can make my favourite environment do what other environments do" is a short leap indeed. Herein begins "the churn." Specifically, I mean that problems previously solved in other environments present themselves as an opportunity to be transcoded into (insert environment here). It is far easier to dissect an existing solution and produce an equivalent in another language than it is to tackle something new.

With this background established, let's discuss some of the specific points you have broached.

> I used to love software/programming but it's getting boring now.

A lot of responses have said you might be burnt out. I do not belive this is the case based on what you have written and the title of this thread. Instead, perhaps the fact you are "bored with life and software industry" is because the passion you have for what you love to do has been muted (more on that in just a moment and not the same as burnout).

> It seems so clear to me that so much futile effort is being put into building yet another language, yet another editor, yet another UI rework, yet another infrastructure rework. And for what, just because people would have something to show for.

This is experiencing enlightenment. When this sort of epiphany happens, seeing efforts addressing the same things over and over again becomes obvious (as you state). And once our eyes are open, we cannot close them again. Given a situation where a person has experienced this type of growth, yet may not feel they are in a position to progress with it, some combination of boredom/frustration/dejection/futility are sure to follow.

> Does it get any better ?

Yes. And you are at the precipice of it being so.

It gets better by accepting that those junior in the field experience the aforementioned progression and will duplicate projects often for the ease of being able to simply transcode. And that's OK, as they are in a period of discovery which is entirely new to them.

It gets better by recognizing that still others will reinvent the wheel just because that is all they can do. Their growth has stopped for whatever reason. And that's sad, but their choice.

It gets better by realizing that you have reached the point where you can discern duplicate efforts and choose what of those offerings are best for your way of thinking and/or working.

Finally, it gets better by allowing yourself to choose your own path, trusting your awareness/experience, with what you feel is best for how you can optimally do what you love to do, and eschewing what others espouse since they simply are not you.

1. what hurt you badly in the last 15 years

2. which things have already been done but have been reinvented an repackaged differently.

I've seen all these before in other incarnations.