# Rant Published articles for Rant. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Things I love and hate about the state of software companies in 2024 DevFeed: [Things I love and hate about the state of software companies in 2024]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-03-16T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Agile](), [Software](), [Self-organizing Team](), [systems]() Tags: [agile](), [better](), [business-developer-experience-employee-happiness-high-purpose-environments-remote-work-self-ref](), [deployment](), [framework](), [leadership](), [management](), [process](), [productivity](), [proxy](), [rant](), [work](), [writing]() ### AI overview An opinionated critique of software companies in 2024, focusing on hierarchy, management practices, productivity measurement, return-to-office policies, team structures, deployment handovers, framework dependence, career competition, and product work that prioritizes busywork over value. ### Source excerpt Things I love and hate about the state of software companies in 2024 Disclaimer: This started as a rant, not meant to be published. But sticking to my "New Year's resolution" to write about what triggers me most, I decided to publish it anyway. I wanted to publish it as a LinkedIn post, but it got too long. So here is the unshortened, unpolished and authentic original version of this document, most of which I wrote on my phone after waking up on a Sunday at 5:45am. 😬 ## Hey Tech Recruiter, Here Are Some Tips from a Developer DevFeed: [Hey Tech Recruiter, Here Are Some Tips from a Developer]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-01-03T08:57:36.021000Z Content type: opinion Language: en Sources: [Eevis Blog]() Topics: [Front end](), [Back end](), [JavaScript](), [DevOps](), [Accessibility](), [Java]() Tags: [accessibility](), [backend](), [blog-post](), [developer](), [devops](), [frontend](), [java](), [javascript](), [rant](), [tech]() ### AI overview An accessibility-focused frontend developer shares personal advice for tech recruiters, including avoiding unsolicited or repeated calls, distinguishing frontend, backend, and DevOps roles, separating Java from JavaScript, providing client context when possible, and considering accessibility in company websites. ### Source excerpt I wrote a rant to LinkedIn in the summer, summarizing a couple of tips on how (not) to contact me and similar stuff. Since then, I've been thinking about writing a blog post about this topic, and here it finally is! I've had good experiences with tech recruiters over the past years, but unfortunately, there have also been bad experiences. And this blog post comes from those occasions. Here's the original rant: Dear tech recruiter, here are a couple of things I'd wish from you. ✨ Please don't call me. Even though you can find my number somewhere, it's not an open invitation to call. I hate speaking on the phone, so you calling me unsolicitedly makes me anxious. And I don't want to work for your company or your client if you make me anxious. ✨ Please don't call me many times. You know, the seventh call within three days is just too much. (The first one was too, but... seventh. C'moon.) ✨ If you say you're a tech recruiter, you really should know the difference between frontend, backend, and devops. And you should look at my profile at least just enough to know I'm a frontend developer - and not contact me with backend / devops-positions. ✨ Oh, and a tip: Java and JavaScript are different languages. Me having JavaScript on my profile does not mean I have extensive knowledge on Java. ✨ I won't answer "Hey I have this mysterious client you would be lucky to work for"-type of messages. Sorry, I know you always can't disclose the client, but I want to know where I'm getting into if I take a call with someone. And a ✨Bonus Tip✨: Oh, and if your company's/your client's website has these fancy animations/auto-playing things that make me literally sick I don't want to work for you or your client. I know I'm an accessibility specialist who could come and fix these things, but from the messages I've received, you're not looking for that. You're looking for a backend developer. So... no. Yes, it's been one of those weeks. Source: LinkedIn These tips are written from my perspective, a ## A critique of Google search ads and SEO-focused results for remote-work queries DevFeed: [A critique of Google search ads and SEO-focused results for remote-work queries]() Original publisher: [Read original article]() Author: Michael Dubakov Published: 2022-11-25T15:06:35Z Content type: opinion Language: en Sources: [Stories by Michael Dubakov on Medium]() Topics: [Search engine optimization (SEO)](), [Google]() Tags: [ads](), [advertising](), [google](), [marketing](), [rant](), [search-engine](), [seo](), [spam]() ### AI overview The author criticizes Google search results for a remote-work query, describing prominent ads and generic SEO-focused articles that they found lacking in practical information. They report finding more useful resources through Hacker News and express frustration with the search experience. ### Source excerpt I used to love Google. Now I don't. I used to enjoy search for new information and explore some new topic in Google. Now I don't. I'm on the verge of switching to another search engine. Yesterday I dug into remote work. I searched for various info, primarily I wanted to find exact remote companies practices from real practitioners. This is a typical screen in Google for any relatively generic search request. Screen 1. Ads On the first screen I see only ads and some glimpse of hope in the footer. I have to scroll down. Screen 2. SEO-optimized bullshit No hope. All these articles are not good enough. All are generic, and I have a feeling most of them were written by people with zero experience in remote work. I got very little interesting info from them. I have to scroll down. Screen 3. More SEO-optimized crap More SEO-optimized articles, maybe HBR was relatively OK. I have to scroll down. Screen 4. More Ads Final screen has more ads. Is it me? Maybe in some poor country with GDP < 1K per person I will see less ads? Not sure there is VPN for South Sudan... Next page... It appeared to be very hard to find good resources about remote work. Google is filled with generic, non-concrete, SEO-oriented bullshit. I had to dig this piece of crap for an hour to find some rare gems. Most gems I found on HN. My rant is over. Hug me, please. P.S. HN discussion thread ## Back to Firefox (Nightly) DevFeed: [Back to Firefox (Nightly)]() Original publisher: [Read original article]() Author: Stanko Published: 2019-09-26T00:00:00Z Content type: opinion Language: en Sources: [Stanko Tadić]() Topics: [Firefox](), [Firefox Nightly](), [macOS](), [cpu]() Tags: [battery](), [cpu](), [firefox](), [firefox-nightly](), [issue](), [macos](), [rant](), [release](), [stable](), [version]() ### AI overview The author returns to Firefox after a MacOS scaled-resolution issue that caused very high CPU usage and battery drain was fixed. The fix was expected to reach stable Firefox 70 in late October 2019, while Firefox Nightly offered an earlier, potentially unstable version. ### Source excerpt Two years ago I wrote this rant. Firefox had a problem on MacOS on scaled resolutions, resulting in insanely high CPU usage and battery drain. Issue is finally fixed, and I'm happy to say I'm using it again. The fix is expected to land in the stable version in late October 2019, with the release of Firefox 70. Meanwhile you can download Firefox Nightly, which is the freshest (and sometimes unstable) version of Firefox. I'm really happy to be using Firefox again, and I think you should try it as well. ## Why Microservices Can Increase Setup and Debugging Complexity DevFeed: [Why Microservices Can Increase Setup and Debugging Complexity]() Original publisher: [Read original article]() Author: Map Published: 2019-03-13T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Microservice](), [Architecture & Design](), [debugging](), [systems](), [CI/CD](), [Kubernetes](), [Docker]() Tags: [complexity](), [continuous-integration](), [debugging](), [docker](), [k8s](), [microservices](), [monolith](), [rant]() ### AI overview This opinion article argues that the move from monolithic applications to microservices can introduce substantial setup, onboarding, debugging, and testing complexity. It notes that containers and orchestration help, but distributed services can make tracing errors and maintaining compatible versions more difficult. ### Source excerpt It feels like we're starting to pass the peak of the hype cycle of microservices. It's no longer multiple times a week we now see a blog post of "How I migrated my monolith to 150 services". Now I often hear a bit more of the counter: "I don't hate my monolith, I just care that things stay performant". We've actually seen some migrations from micro-services back to a monolith. When you go from one large application to multiple smaller services there are a number of new things you have to tackle, here is a rundown of all the things that were simple that you now get to re-visit: Setup went from intro chem to quantum mechanics Setting up a basic database and my application with a background process was a pretty defined process. I'd have the readme on Github, and often in an hour or maybe a few I'd be up and running when I started on a new project. Onboarding a new engineering, at least for an initial environment would be done in the first day. As we ventured into micro-services onboarding time skyrocketed. Yes, we have docker and orchestration such as K8s these days to help, but the time from start to up and running a K8s cluster just to onboard a new engineer is orders of magnitude larger than we saw a few years ago. For many junior engineers this is a burden that really is unnecessary complexity. So long for understanding our systems Lets stay on the junior engineer perspective for just a moment. Back when we had monolithic apps if you had an error you had a clear stacktrace to see where it originated from and could jump right in and debug. Now we have a service that talks to another service, that queues something on a message bus, that another service processes, and then we have an error. We have to piece together all of these pieces to eventually learn that service a was on version 11 and service q was expecting vesion 12 already. This in contrast to my standard consolidated log, and lets not forget my interactive terminal/debugger for when I wanted to go step by s ## How Public Online Complaints Are Changing Business Etiquette DevFeed: [How Public Online Complaints Are Changing Business Etiquette]() Original publisher: [Read original article]() Author: Map Published: 2008-06-02T13:16:31Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Publishing](), [Website](), [Users](), [Risk]() Tags: [publishing](), [rant](), [risk](), [users](), [web]() ### AI overview This opinion article argues that business etiquette is changing as employees and former employees increasingly publish complaints and workplace experiences online. It also notes that employers may examine applicants' social media profiles, blurring boundaries between personal and professional conduct. ### Source excerpt A recent conversation of someone that was offended when the were introduced to someone new, then was not greeted first since they were a female brought what follows to mind. The above is a train of thought that came from a 70 year old military wife. I do not believe this is common practice today and is quite rarely found as the common etiquette, but nonetheless I think what is proper etiquette in business is changing quite rapidly. Though I'm not sure if all of the older ideas and principles have gone away. I take as a first example zuckerburg, whom is a notoriously difficult interview. Not because he keeps things hidden, or is sealed tight about the company, but rather that his soft skills are not his strength. His strength is building a web product that millions of people find worthwhile to divulge hours of their day into it. Even two years ago when you were disgruntled with a company you may have gotten a few drinks in you and talked to a friend about your displeasure. But it certainly was not made fully public for anyone to see. At best you could only hope you were simply privy to things that would be brought to the publics eye from a larger misdoing either legally or that a mass-crowd found a problem with. But for simply being overworked, underpaid, or in some other odd way mistreated there was no politically correct outlet to speak through. However in the past years it has become extremely common for those that are still employed, or were employed to voice their complaints and bring to light the details that were once hidden. I think of Zed Shaw's rant on rails which calls out specific companies, or an older blog the diary of a mac genius, who gave detailed behind the scenes information of an apple customer support genius bar. While I'll concede for the mass majority if it's published it's doesn't mean its consumed, so it's not a dramatic effect on any single business, I still find it hard to believe that this overall shift of users freely publishing is not go