@SidTheITGuy Any examples?

Never feel like I stumbled upon any braggadocious bros when it comes to coding podcasts or other coding related content.

I do listen to some coding podcasts with 2 dudes but the feel very nice and not even remotely disgustingly dude-bro-ish.

Seems so common that I never wanna go freelancing ever again!

At least I would never wanna deal with client payments myself - and the types of deals that have to happen when they demand a big change and it's unclear if that should be extra $ or not.

Such a relief to work for a fixed salary.

I hope things get better!

When it comes to american sayings all I can think of is the "A healthy person has a thousand dreams - an unhealthy person only has one".

When it comes to "if you wait to feel to do it you'll never do it" my thinking is: sometimes it's fine to let my impulses lead the way, but often it's better to wait and see if the same vibe popus up again - if it doesn't it probably wasn't important.

In my experience it's always OK to admit that a requirement is overwhelming and will take much longer than a stakeholder imagines.

They will not be upset if you just honestly say you're in the middle of working on 4 other features and this is a big change.

(but they might be short sighted and just say "screw the other 4 features" without realising that'll delay the entire project)

But my advice is: don't say anything in spite like "I told you so" or "We started this projects 6 months ago, you had all the time to think about it." type thing - if you're gonna mention that - talk it over with your PM and mention it a few days later in a retro when you cool off.

Stakeholders are dumb and they hate being reminded of it in snarky ways. But if you can phrase it in a certain nice way they may understand.

@TerriToniAX Interesting. I gotta ask - how the business manage to avoid stuff like versioning and proper deploys for this long.

Is it because the dev-team is so tiny and has no power in the organisation, or because the tech was always ran by the some oldschool dudes for 25 years or because all hires are juniors afraid to change anything?

@TerriToniAX Interesting. I gotta ask - how the business manage to avoid stuff like versioning and proper deploys for this long.

Is it because the tech org is super tiny that no process improvements were ever a prio, or because the tech was ruled by an iron fist by oldschool devs who refuse to change anything for 30 years?

Yeah, I laugh whenever I hear someone say the old "programming is mostly math" - that may be true for 3d and embedded but not for the majority.

feels like I barely done any math in my career, at least not even close to what we had to do in college.

I know you're joking and exaggerating but if someone in my team said they wanted to refactor the codebase for a theoretical 5% COMPILATION perf boost (Presumably this has zero effect on the user) I would've forced them to measure how much time they actually spend waiting for compilation 🤣

Besides - if this is a new feature that may be baked into the dotnet core - is it really worth doing any refactoring to have it for 1.5 years before everyone else?

@lungdart ❤️ Agree.

My product dev team has managed to get rid of the Estimation process entirely - but whenever I talk to colleagues who work for consultant projects I am sadly reminded how "the entire reason we got a contract was that we estimated it could be done in 3 months" 🤣

The one estimate I can appreciate is when the PM uses ad hoc estimates to see if it's worth even discussing building a feature.

Like "I hear a couple customers asking for a bookmark feature - would that be a huge project?" - Yes "OK, I'll tell em it's a no go"

"I hear a couple customers asking for the menu to have a link to customer-service, would that be a huge project?" - No it's done in 2 minutes "OK! let's do it"

Which kinda stuff do people say you should've excluded from your PR?

---

Personally the last "Is the PR too big?"-debate I was part of was when we built a new website from scratch.

Co-worker got the ticket "Add menu bar with userName". The codebase at that time was in it's infancy so it didn't have much CSS for the site layout. And our test-suite did not have the capability to run clientside JS (which would be responsible for rendering the userName)

The resulting PR added a ton of code to our general site layout HTML/CSS to make sure the site looked like the design, and a ton of code to our test runner to make sure it could run clientsideJS.

I felt this was admirable work. But the PR got stuck in review for days and days as people debated the details the CSS layout and the pros and cons of different types of JS-runners in test suites.

Estimations are regularly off - even if you're doing highly repeatable work.

Consider that it's pretty regular that construction work ends up being delayed and costing 3x more than the planned budget - even when the construction companies have done pretty much the exact same thing dozens of times before, and there's not as many changes in construction as in software.

The idea that "you've done this before - so we can estimate it takes the same amount of time" rarely works.

Not to defend Safari’s devtools in general (I haven’t used them for months) but I bever had this particular issue - it ”works fine on my machine”

Is it like this all the time for you?

I’m thinking maybe it’s an edge case like if for example some JS is doing updates on the selected DOMElement or similar

One random good thing happening is that the deforestation of rainfortest in Brazil has decreased - lower now than the past 9 years after a regime change

Off the cuff reaction:

I'm thinking that it's so easy to test if ChatGPT has memory of past questions or not - that it's hard to imagine this is very unlikely to be a mistake - and also unlikely to be a blatant breach of their promise.

I imagine that most likely the user has misunderstood the ChatGPT settings or what they promise in their terms.

The user may THINK they are using a mode with zero memory - but if you actually read up on the terms it will state (either in plain text or in some intentionally confusing wording) that this is not the case.

I may be wrong. But I just find that memory of past convos is one of the first things everyone tests when using ChatGPT so it's unlikely such a glaring issue could exist.

@noyb What I've heard from the app-team that I work next to is that many app-platforms simply don't have any native feature for text-selection.

There simply is no such feature at all in the app context, so app developers are forced to build a custom implementation (Which some never end up doing)

Many news apps have implemented a Copy-feature where if you longpress to start selecting text (as you would in a mobile browser) you will just get a popover saying "Copy" which allows you to copy that one paragraph.

Unlike the web (or any Note-taking-app) where longpressing a piece of text would enter text-selection-mode where you can drag the textSelection-area freely.

@BordedDev But arguably it's not like these US recipe sites are clearly more SEO-optimized than the swedish recipe sites. What I've heard from SEO-experts - even when asking what would be the most evil way to hack SEO optimization - they have said that stuffing articles full of semi-relevant content would NOT be the way to go.

I wonder if it's the result of different SEO culture assumptions, where the US companies have consulted SEO firms that DO advocate that word-stuffing approach, while swedish SEO-firms don't.. even if it's unclear what's optimal.

Try giving him feedback. I know - it's not easy - and we can assume people like this are hopeless so giving them feedback would just make em feel bad. But sometimes there is hope.

For example: I've had a colleague who was the opposite of your guy: they were worried we thought their code wasn't good enough so they spend way too long looking for the optimal solution, and we had to tell them "just do it Good Enough".

This guy might have been the opposite, but still needs some guidance.

One of the most maddening things to me is american recipe websites - compared to swedish recipe websites

In sweden a recipe website content is just just 1. headline 2. ingredients 2. how to make it

In the US it's

1. the history of the stove top

2. four pages of facts about lime juice

3. - click to scroll down to the ingredients list-

3. twelve variations of this recipe

4. my family's ratings of this recipe

5. interesting thoughts

6. ingredients

7. history of cinnamon and the spice trade

8. how to cook

For example https://loveandlemons.com/paloma/

I know "they do it to make you scroll through as many ads as possible" but what's interesting is that swedish sites never do this, it's just sites in english

I feel ya.

But at the same time I feel that many of these crappy changes were inevitable consequences of how the internet took over everything and forced businesses to go online.

In the Early Days of the Web you could have a free, ad-free magazine website. Cause they made their money from paper subscriptions and paper ads.

As the web became the primary source of income - they had to start using web ads and paywalls.

This post makes me happy :)

"for 1,80 per month she has a domain name (i asked if it will have SSL, that's still bit unclear)"

These days a setup without SSL is almost worthless as common browsers will flag any HTTP site as unsafe so it'll probably not get any visitors.

Sadly - many interfaces are very complex regarding how to configure it.

@lorentz I see, then my comments can be disregarded

(But maybe it's still true that IT would somehow feel that an increased volume of requests makes the matter more pressing. Despite all logic. I know I work that way and can't help it 🤣 )

Advice: Ask colleagues to make a request similar to yours.

Never underestimate the power of multiple requests.

At the website I work for we have a user feedback inbox. If 1 person mentions an opinon we might figure it could be an anomaly, if 2 or 3 people mention the same thing we will take it way more serious.

I figure IT might behave as the "bell curve meme".

* For small companies they are quite chill and allow permissions to those who need it

* For mid-sized companies: they are tasked with increasing security so they become overconfident in attempts to enforce a restrictive policy. (And they might argue devs are a minority, and this is a necessity for all the non-dev employees)

* For a large company, with a larger dev org, they realise they gotta chill out and give more permissions to devs

This is just anecdotal so take it with a grain of salt

I’m hoping the attacks on internetarchive will raise awareness of the importance of preserving history in a more official way

Many countries have a digital archive of every major newspaper print as part of the national library

(but I also assume some of the conspiracy theories are that nation states are trying to censor destroy the web… but still - I don’t think these newspaper archives would be around if they had only been private efforts)

I kinda forgive newscasters.

They are told to simplify things for the average person.

When it comes to subjects taught in science class they can assume there's some base level of knowledge - and they can actually have a scientist as a guest and let them mention stuff like electrons, the scientific method, chemical reactions etc. (Even though they often also simplify things to a 5 year old level and say stuff like "If a nuclear plant was a human, uranium would be like a hamburger")

Software on the other hand is not taught to everyone in school - so they have to assume zero knowledge.

Software is also abstract and invisible, unlike real world physics like explosions.

Webpack can be notoriously complex though.

(It really depends - in some new projects I've managed to copy-paste another project's webpack config and just get stuff working asap, in other projects I've got stuck with Webpack issues for a long time)

I'm curious what you mean regarding implementing NPM.

Was this your first time using NPM? Did you use to have a ton of 3rd party scripts imported before - but now you tried importing them as packages for the first time?

I rarely hear people imagine coding is easy

Most common thing I hear is people imagine that you build something once and then it's done an will last forever

"Isn't that website DONE?" 🤣 is a common question.

(But if we're honest, us devs might not be better, for example I've heard defvs say "I wonder what devs at Craigslist do - that site has not changed in years" but it is probably under constant development)

I would also consider this exact same rant would've been posted if DevRant would've been around when they switched from Iphone3GS to Iphone4

"Why make it thinner? Just keep it the same size and make the battery last longer"

Might be a constantly valid question though, just saying this is nothing new, just a continuation of thinnification going on for over a decade.

Did you learn anything about development philosophy or debugging strategies?