RayFrankenstein

16 ms·

1.
by RayFrankenstein 9mo ago
There was a lot of pressure in the Perl community to write things as succinctly as possible instead of as maintainably and understandably. That’s not realistic for use in a field with a lot of turnover and job hopping.
2.
by RayFrankenstein 11mo ago
The guy is such a web zealot that he refuses to make the sensible engineering tradeoff that favors speed and offline capabilities over platform ubiquity. Most sane people would write a native app for this sort of thing if money was on the l
3.
by RayFrankenstein 11mo ago
So this person has never been a developer?
4.
by RayFrankenstein 11mo ago
Traditional agile practices always sucked and were beyond problematic. Maybe the speed of AI is just making it more apparent.
5.
by RayFrankenstein 1y ago
It's actually pretty amazing that you extracted the very worst, most very destructive practices and ideologies of agile and put it into a package that would allow toxic managements to maximally hurt their developers.
6.
by RayFrankenstein 1y ago
I maintain a compendium of developers' best negative comments about agile https://github.com/rayfrankenstein/AITOW/blob/master/README.... Here's what I've learned from maintaing this compe
7.
by RayFrankenstein 1y ago
I maintain a compendium of 100's of the best developer comments about agile. Check it out and make your own conclusions. https://github.com/rayfrankenstein/AITOW/blob/master/README....
8.
by RayFrankenstein 2y ago
I worked on a mobile app dev team that tried to Ui logic with the backend. With many of the justifications you mentioned being justifications for doing it that way. White labelling, A/B testing, avoiding redeploying, etc. The result wa
9.
Agile Is for Losers (2020)(hypermatic.com)
22 points by RayFrankenstein 2y ago|21 comments
10.
by RayFrankenstein 2y ago
There are no agile trainings, only agile indoctrinations. Not that you can't have a bit of fun with them (at your own risk). 1. Ask if they've worked as a professional software developer? If not, enjoy them squirming as you subtle
11.
by RayFrankenstein 3y ago
Ideally you should use types, but if you have to use any because of some complicated situation where the compiler’s bitching, it’s no big deal. Anyone who tells you otherwise is a shamey OCD a-hole.
12.
by RayFrankenstein 3y ago
Quite a few experienced developers contributed their opinions on why found agile so problem. Check it out https://github.com/rayfrankenstein/AITOW/blob/master/README.... Agile has fundamental structural
13.
by RayFrankenstein 3y ago
Is AI being used to moderate comments now on HN? I ask because I don’t find this comment to be particularly moderation-worthy according to most modern standards of flamebait.
14.
by RayFrankenstein 3y ago
1. Options: give them the answer they’re looking for, even if its bullshit. 2. Stonewall and give them answers so confusing and incongruent they’ll eventually stop asking.
15.
by RayFrankenstein 3y ago
Here’s a compilation of hundreds of social media comments explaining why agile/scrum is so problematic https://github.com/rayfrankenstein/AITOW/blob/master/README....
16.
by RayFrankenstein 3y ago
My problem is not whether I “like” management’s tradeoffs they force me as a developer to make; my problem is that managements typically don’t take accountability for choosing to make them. And then management (and their allies in the close
17.
by RayFrankenstein 3y ago
Another from AITOW “I regularly ask ‘Why are we running a marathon in a thousand sprints?’. Besides tech debt, a concern I have that I don't see brought up is burn out. With Scrum, every action you perform is micromanaged and with a pu
18.
by RayFrankenstein 3y ago
Another from “Agile In Their Own Words” “My experience shows that proper testing and documentation is the first thing that management wants taken out of the story, often with the excuse "We can handle that in a later sprint." But
19.
by RayFrankenstein 3y ago
From “Agile In Their Own Words”, https://github.com/rayfrankenstein/AITOW/blob/master/README.... “One aspect of agile, and of SCRUM in particular, is that the team is expected to 'forecast' whi
20.
by RayFrankenstein 3y ago
Testimony from dozens upon dozens of developers that think that scrum is useless, toxic bullshit: https://github.com/rayfrankenstein/AITOW/blob/master/README....
21.
by RayFrankenstein 3y ago
And here is a list of every rebuttal you could give them: https://github.com/rayfrankenstein/AITOW/blob/master/README....
22.
by RayFrankenstein 3y ago
I fail to see the problem with that
23.
by RayFrankenstein 3y ago
These designs are usually added to show the executives of the company that a branch of the org chart and its Important People can "add value". Conversely, the fastest way to turn around a failing company is to search through compa
24.
by RayFrankenstein 3y ago
I've come to understand that the most important part of any software project is the Critical Twenty, the first 20% of the project's timeline where developers' need to do things like gain a deep understanding from reading docu
25.
by RayFrankenstein 3y ago
Borrowing from sci-fi, I call it the “Agile Expanded Universe”
26.
by RayFrankenstein 3y ago
What developers really think about Agile https://github.com/rayfrankenstein/AITOW/blob/master/README....
27.
by RayFrankenstein 3y ago
(From “Agile In Their Own Words”) “This agile witch hunt has to end, but it never will unless we start politely asking for the things we want. i know for a fact that 90% of engineers dislike agile but many don't even imagine there can
28.
by RayFrankenstein 3y ago
Which is exactly why Agile In Their Own Words exists. Most everything else that’s been written about agile has been pure propaganda that you’re not allowed to question. There needs to be other viewpoints that are critical of agile.
29.
by RayFrankenstein 3y ago
One of the problems with agile is that it demands that every act of developer productivity be couched in a user story, a user-visible unit of change. And the catch-22 is that only things that “deliver value” can be user stories, only things
30.
by RayFrankenstein 3y ago
Agile’s term “customer” is actually very ambiguous about whether it’s trying to define the relationships between developers and employers or developers and users who buy the software.

More ›