Fuck sake, so my bank has been migrating/rolling out new IT system and app/site have been broken for about a week (others noted evidence of devs debugging in production)

Assuming I don't lose my money as some mischievous assholes will inevitably exploit the fuck up, and rob the bank, I will be moving my funds to a different bank...

In mean time I'm trying to prepare for uni, and they're making a ton of semi-random changes in addition to rolling out a site with course details and info along those line, and good fucking god is it bad.

Is is slow as fuck? Check. Does it use never-seen-before naming for standard things? Check! Is the UI pulled from late 90's? YOOU BETCHA! Are the pages bloated with unnecessary content? Fuck yeah! Do I get SQL exceptions when I finally locate my course? Of course I do. Does clicking "back" take me back to the landing page instead of previous page, when I'm several steps deep? .....

I could keep going, but don't feel like ranting and feel more like punching someone in the throat.repeatedly.

I think that two criterias are important:

- don't block my productivity
- author should have his userbase in mind

1) Some simple anti examples:

- Windows popping up a big fat blue screen screaming for updates. Like... Go suck some donkey balls you stupid shit that's totally irritating you arsehole.
- Graphical tools having no UI concept. E.g. Adobes PDF reader - which was minimalized in it's UI and it became just unbearable pain. When the concept is to castrate the user in it's abilities and call the concept intuitive, it's not a concept it's shit. Other examples are e.g. GEdit - which was severely massacred in Gnome 3 if I remember correctly (never touched Gnome ever again. I was really put off because their concept just alienated me)
- Having an UI concept but no consistency. Eg. looking at a lot of large web apps, especially Atlassian software.
Too many times I had e.g. a simple HTML form. In menu 1 you could use enter. In menu 2 Enter does not work. in another menu Enter works, but it doesn't submit the form it instead submits the whole page... Which can end in clusterfuck.
Yaaayyyy.
- Keyboard usage not possible at all.
It becomes a sad majority.... Pressing tab, not switching between form fields. Looking for keyboard shortcuts, not finding any. Yes, it's a graphical interface. But the charm of 16 bit interfaces (YES. I'm praising DOS interfaces) was that once you memorized the necessary keyboard strokes... You were faster than lightning. Ever seen e.g. a good pharmacist, receptionist or warehouse clerk... most of the software is completely based on short keyboard strokes, eg. for a receptionist at a doctor for the ICD code / pharmaceutical search et cetera.
- don't poop rainbows. I mean it.
I love colors. When they make sense. but when I use some software, e.g. netdata, I think an epilepsy warning would be fair. Too. Many. Neon. Colors. -.-

2) It should be obvious... But it's become a burden.

E.g. when asked for a release as there were some fixes... Don't point to the install from master script. Maybe you like it rolling release style - but don't enforce it please. It's hard to use SHA256 hash as a version number and shortening the hash might be a bad idea.

Don't start experiments. If it works - don't throw everything over board without good reasons. E.g. my previous example of GEdit: Turning a valuable text editor into a minimalistic unusable piece of crap and calling it a genius idea for the sake of simplicity... Nope. You murdered a successful product.
Gnome 3 felt like a complete experiment and judging from the last years of changes in the news it was an rather unsuccessful one... As they gave up quite a few of their ideas.

When doing design stuff or other big changes make it a community event or at least put a poll up on the github page. Even If it's an small user base, listen to them instead of just randomly fucking them over.
--
One of my favorite projects is a texteditor called Kate from KDE.

It has a ton of features, could even be seen as a small IDE. The reason I love it because one of the original authors still cares for his creation and ... It never failed me. I use Kate since over 20 years now I think... Oo

Another example is the git cli. It's simple and yet powerful. git add -i is e.g. a thing I really really really love. (memorize the keyboard shortcuts and you'll chunk up large commits faster than flash.

Curl. Yes. The (http) download tool. It's author still cares. It's another tool I use since 20 years. And it has given me a deep insight of how HTTP worked, new protocols and again. It never failed me. It is such a fucking versatile thing. TLS debugging / performance measurements / what the frigging fuck is going on here. Take curl. Find it out.

My worst enemies....

Git based clients. I just hate them. Mostly because they fill the niche of explaining things (good) but completely nuke the learning of git (very bad). You can do any git action without understanding what you do and even worse... They encourage bad workflows.
I've seen great devs completely fucking up git and crying because they had really no fucking clue what git actually does. The UI lead them on the worst and darkest path imaginable. :(

Atlassian products. On the one hand... They're not total shit. But the mass of bugs and the complete lack of interest of Atlassian towards their customers and the cloud movement.... Ouch. Just ouch.

I had to deal with a lot of completely borked up instances and could trace it back to a bug tracking entry / atlassian, 2 - 3 years old with the comment: vote for this, we'll work on a Bugfix. Go fuck yourself you pisswads.

Microsoft Office / Windows. Oh boy.
I could fill entire days of monologues.
It's bad, hmkay?

XEN.
This is not bad.
This is more like kill it before it lays eggs.
The deeper I got into XEN, the more I wanted to lay in a bathtub full of acid to scrub of the feelings of shame... How could anyone call this good?!?????

Users running Linux on laptops with Intel processors should avoid Linux Kernel 5.19.12 due to an error that might physically harm the display. Fortunately, kernel 5.19.13 has already fixed the issue. Versions 6.0 and 6.1 have also begun rolling out with many significant changes.

Just needing somewhere to let some steam off

Tl;dr: perfectly fine commandline system is replaced by bad ui system because it has a ui.

For a while now we have had a development k8s cluster for the dev team. Using helm as composing framework everything worked perfectly via the console. Being able to quickly test new code to existing apps, and even deploy new (and even third party apps) on a simar-to-production system was a breeze.

Introducing Rancher

We are now required to commit every helm configuration change to a git repository and merge to master (master is used on dev and prod) before even being able to test the the configuration change, as the package is not created until after the merge is completed.

Rolling out new tags now also requires a VCS change as you have to point to the docker image version within a file.

As we now have this awesome new system, the ops didn't see a reason to give us access to kubectl. So the dev team is stuck with a ui, but this should give the dev team more flexibility and independence, and more people from the team can roll releases.

Back to reality: since the new system we have hogged more time from ops than we have done in a while, everyone needs to learn a new unintuitive tool, and the funny thing, only a few people can actually accept VCS changes as it impacts dev and prod. So the entire reason this was done, so it is reachable to more people, is out the window.

How do you guys keep up with new concepts and tech? Or what is your preferred source for this activity?

Conferences(in person or youtube)
ACM journals/SIGs
Research papers
Blogs/hackernews or the like
Books
Something else
?

So I've been working with a Ruby DSL my colleague wrote for our rails app that builds app flows represented by data using migrations, which are consumed and rendered by the frontend. So data-driven UI.

It's very solid in prod, so we're running with it, but it can be hard to work with because everything is built using migrations - for example, the one signup flow we have spans across 7 migrations that add/change/remove components in the flow, change decision logic, etc.

I'm building a particularly complex one and can't decide which development method is better. I can either

1. write the flow in one huge migration, then change as needed - keep rolling back, resetting and testing until it works, or

2. increment changes and additions in multiple migrations across multiple pull requests, such that the final product spans across about 10-12 smaller migrations

Which one?

Both are super icky to me but I'm leaning toward 1. At least all of the shit would be in one place and would make sense without needing to switch between 10-12 files to see where shit is being defined, changed, etc. because it reads chronologically.

Greene Horizons: Empowering Change Through Motivation and Motivational Interviewing

At Greene Horizons, located at 320 Raritan Ave #202b, Highland Park, NJ, we are committed to helping individuals overcome obstacles and achieve their goals through the power of motivation and motivational interviewing. Whether you're dealing with personal challenges, striving for positive change, or seeking support in your journey toward a healthier life, we provide the guidance and tools to help you unlock your potential.

The Role of Motivation in Personal Growth
Motivation is the driving force that fuels change and helps us pursue our goals. Whether it's overcoming personal barriers, achieving better mental health, or making positive lifestyle changes, motivation is key to success. At Greene Horizons, we believe that everyone has the ability to make meaningful changes in their life. Our goal is to help you tap into your inner drive and find the motivation to create lasting transformations.

Whether you're dealing with procrastination, a lack of confidence, or difficulty following through with goals, we offer the support and encouragement you need to stay motivated. Our therapists work closely with you to identify what drives you and help you harness that energy to make sustainable, positive changes in your life. Motivation is not only about setting goals but also about understanding the emotional and psychological factors that influence your ability to achieve them.

Motivational Interviewing: A Collaborative Approach to Change
Motivational interviewing is a client-centered, evidence-based therapeutic approach that focuses on helping individuals find the motivation to make positive changes. Rather than being confrontational or directive, motivational interviewing encourages self-reflection and enhances an individual’s intrinsic motivation to change.

At Greene Horizons, we use motivational interviewing to help clients explore their ambivalence toward change, resolve internal conflicts, and ultimately commit to their goals. This approach is especially effective for individuals dealing with addictions, mental health challenges, and those who may feel stuck or uncertain about making changes in their lives.

The key principles of motivational interviewing include:

Expressing empathy: We listen without judgment, acknowledging the challenges you face.
Developing discrepancy: We help you see the difference between where you are and where you want to be, increasing awareness of the need for change.
Rolling with resistance: Instead of confronting resistance, we work with it, helping you explore any fears or doubts about change.
Supporting self-efficacy: We empower you to believe in your ability to succeed and make positive changes in your life.
Our skilled therapists are trained in motivational interviewing and can guide you through this powerful process to help you find clarity, build motivation, and take actionable steps toward your goals.

Why Choose Greene Horizons for Motivation and Motivational Interviewing in NJ?
At Greene Horizons, we are passionate about helping individuals tap into their full potential. Whether you're facing challenges in your personal life, career, or mental health, our team of experienced therapists is here to provide the support you need to stay motivated and achieve your desired outcomes.

We understand that every individual’s journey is unique, which is why we offer personalized care tailored to your specific needs. Our approach is compassionate, client-centered, and grounded in evidence-based practices, such as motivational interviewing, to help you achieve long-term success.

Take the First Step Toward Change Today
If you're ready to unlock your potential, find your motivation, and make lasting changes in your life, Greene Horizons is here to help. Our motivational interviewing services are designed to empower you to make decisions that align with your values and goals, and to move forward with confidence and clarity.

Contact us today at +16408889665 to schedule an appointment or learn more about how we can support you in your journey toward a brighter future. Our office is located at 320 Raritan Ave #202b, Highland Park, NJ 08904, and we are here to help you achieve the positive change you’ve been seeking.