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).

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: 😶

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

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.

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

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.