Programming thread

  • 🏰 The Fediverse is up. If you know, you know.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
I have to admit I have several of his books on my shelf. I've never read them, which I've told is potentially a good thing.
I think I've read one of them a long while ago, Clean Code maybe. He seemed to be the king of stretching out a simple concept to an absurd length. That and some of his advice just sounds like a contractor advising other contractors, rather than someone who sticks around long-term in a business.

I've found he's given a bit of good general advice about code quality. He also supported the Agile Manifesto, which at least in it's original stated form, was a good. Just Agile as it's practiced has become a money making scam to fuck up project management since then. To be fair he might be one of the causes of that.
 
All you need to know about Robert Martin is that (a) he has no successful software projects that he's worked on and can point to as accomplishments, which puts him significantly lower than Ed Yourdon on my "software methodology scam guru" tier list, and (b) he gave himself the disarmingly folksy nickname of "Uncle Bob", which is certifiable used car salesman behavior.
 
I think I've read one of them a long while ago, Clean Code maybe. He seemed to be the king of stretching out a simple concept to an absurd length. That and some of his advice just sounds like a contractor advising other contractors, rather than someone who sticks around long-term in a business.
I've watched some of his old apperances at developer meetups, I think I watched some of his stuff at Ruby West IIRC.

Some of the ideas were interesting and I've incorporated into my own work. But a lot of this stuff is difficult when you are dealing "Mortgage Developers" that seem to expect to collect a paycheck forever because they learned how to bang shit together in VB or Visual Fox Pro 25 years ago.
I've found he's given a bit of good general advice about code quality. He also supported the Agile Manifesto, which at least in it's original stated form, was a good.
On code quality. I've seen some of the tl;dr; versions of the advice and there is good rule of thumb to keep in mind.

On the Agile stuff, I just never seen a business operate that way and when I see people talk about it online / YouTube that are serious, I've never seen a business operate that way.
Just Agile as it's practiced has become a money making scam to fuck up project management since then. To be fair he might be one of the causes of that.
It has made my dev life miserable. I can carry a whole project by myself, if left alone and given clear requirements and time constraints. So many women with far too much makeup making do fucking poker deck shit, meetings and all sorts of shite that stops me from getting work done.

At my last contract, I made a point of starting at 6-7am so I could get some work done as this was too early in the morning for these fucks. I ended up finishing at 1-2pm.
 
Thank you all to everyone who told me I was on the right track a while ago about my web-socket powered front end project. I got a basic implementation working and I am happy with the result. There is some delay I can't seem to find (more than just normal networking delay) so I think something is going on in the browser side of things, but its real-time enough to be useful for my purposes. Now I can work on the "fun" side of the project now that most of the backend is working right, but all this project did was highlight why I don't like front end in the first place.
 
On the Agile stuff, I just never seen a business operate that way and when I see people talk about it online / YouTube that are serious, I've never seen a business operate that way.
If I recall correctly, the original agile manifesto basically advised people to do what worked for them, release software regularly so that requirements can be refined by reality, and value people over processes.

Everything else called Agile is tacked on to get less technically minded people stuff to do.
It has made my dev life miserable. I can carry a whole project by myself, if left alone and given clear requirements and time constraints. So many women with far too much makeup making do fucking poker deck shit, meetings and all sorts of shite that stops me from getting work done.
I am fortunate that I don't have a boss who obsesses over the inane busy work. All he really asks for is a plan, and to be kept updated as things go. He's happy for the plan to change as we go. The worst thing I currently have to do is juggle ticket updates and try to manage a checked out colleague.

I have experienced that crap though. I had a line manager about 10 years ago who basically obsessed over us doing planning poker, story points, meetingings about meetings etc. I am bitter about him more so because he ignored my simple demand to have a grade or title change to go along with a pretty good pay raise I got. He left and became an "Agile Coach". Presumably that means he carries people to the airport.
 
If I recall correctly, the original agile manifesto basically advised people to do what worked for them, release software regularly so that requirements can be refined by reality, and value people over processes.
Yes that is what I are referrring to. Much like many other means it doesn't matter much what the original manifesto was. It is what is commonly understood today. Agile today means lots of time wasting meetings, lots of process that make working miserable and empowers useless people.

I am of the belief that most software projects are often only completed by "Heroic Development". As a former hero, I refuse to to this these days and do the bare minimum as I've never been promoted or had a increase in pay that is worth the hours of my life wasted.
 
Yes that is what I are referrring to. Much like many other means it doesn't matter much what the original manifesto was. It is what is commonly understood today. Agile today means lots of time wasting meetings, lots of process that make working miserable and empowers useless people.

I am of the belief that most software projects are often only completed by "Heroic Development". As a former hero, I refuse to to this these days and do the bare minimum as I've never been promoted or had a increase in pay that is worth the hours of my life wasted.
I miss when I believed in what I was doing enough to be a hero, but honestly after you leave your first dev job you realize that there really are very few projects that are worth being passionate about.
You and your teammates pour your heart and soul into a big thing that people end up using for a little while and a year later outside forces have you working somewhere else and all that stuff you did is dust in the wind.

If your kitchen has more than like 10 cooks in it dont even bother, Just cut the veggies at an acceptable rate or they’ll raise expectations and give you more next time.
 
You and your teammates pour your heart and soul into a big thing that people end up using for a little while and a year later outside forces have you working somewhere else and all that stuff you did is dust in the wind.
I wrote a pure JS charting library for one company. I also wrote a backend to pull all the charts out for this section of the site, with proper DI so I could use stub data easily. It's already cross-browser and cross-device. It had pixel-perfect rendering. I wrote a bunch of documentation for it. They threw it away after 2 years and replaced it with something that worked worse.

I ran another product for them as a contractor. Delivered the product on time (the only time it happened in the company). I was having issues finding work due to a general collapse in demand for contractors. Interviewed for a perm job, and the feedback from my interview was that they didn't understand what I had done at the company, ignoring the fact that my work was running on their servers at the time.
 
Back
Top Bottom