HN user

tcbasche

463 karma
Posts13
Comments350
View on HN

I’d say it’s easier to tell in the US as cities and towns tend to be heavily divided into class-based areas. Not to mention people in general are far more comfortable “showing off” their financial status.

Finland is a lot more homogenous in that sense and people certainly don’t flaunt their wealth.

What does the object have to do with http status codes? It completely entangles the HTTP layer with the database model.

I think most senior or experienced Python developers tend to steer clear of Django.

It's just that you don't hear about it because it's mostly junior / less experienced developers writing about Django online.

edit: having said that, I wish we would be more skeptical of magic frameworks like Django in the Python community at least. Things like 'get_object_or_404'[1] should be burned to the ground.

[1] https://docs.djangoproject.com/en/4.1/topics/http/shortcuts/...

I worked alongside many consultants in Canberra in mostly government agencies and there were a lot of solutions architects and project managers earning roughly $120 an hour pre-tax.

The catch was you need to be a citizen obviously to get even a low security clearance, but from memory some agencies were quite lax and didn't bother for baseline clearance.

It seems like your mind is already made up, but in any case:

https://rednose.org.au/article/Co-sleeping_with_your_baby (Australian non-profit raising awareness against SIDS)

https://raisingchildren.net.au/newborns/sleep/where-your-bab... (Australian government-based parenting resources)

https://www.nhs.uk/conditions/baby/caring-for-a-newborn/redu... (UK Health service)

It's all official health advice from government bodies which say it's unsafe regardless of the parents situation.

I've found though this debate is similar to the "anti-vax" one, in that most people are quite emotional about it regardless of evidence, and can't generally be persuaded.

I quit somewhere after a week. Basically it wasn’t what was advertised (job was supposed to be Python backend but was mainly maintaining Ansible scripts) and the turnover on the team was astonishing. The pair that interviewed me had both quit by the time I joined and nobody there at the time I joined knew even what the point of the project was.

It's the classic HN echo chamber. It's the same people that say nobody uses Amazon anymore, Google search doesn't work, everybody codes in Clojure now etc. etc.

- don't choose lazy pluralization - eg instead of `names/name`, use `nameList/nameItem`

Isn't this just extra noise? If the type of the variable is an Array wouldn't `nameArray` be superfluous? Worse still is if the type changes but the name stays the same.

I get the advice is probably Javascript specific, but even in a Typescript world it doesn't make much sense to me to do this kind of type-in-name encoding.

Clean Code has some truly awful and aged code examples (the prime number generator for instance) and constantly ignores its own advice particularly around avoiding side effects and “single purpose” functions. Working Effectively with Legacy Code is my go-to junior dev example as I think it’s most important to understand what that means and what it looks like early on!

Assuming you have a job already what skills do you feel are lacking that you could brush up on? IMO it makes little sense to pick up on tech for the sake of trends or popularity unless it helps with either finding a job or being more effective at your current one.

Having said that a great deal of being senior is possessing people skills - communication, being able to give feedback etc. That’s what I would focus on - learning tech should be the east part!

- Moved 15000ish km to a different continent / hemisphere

- Bought a house

- Got a great job working with awesome people

- Wife had a kid

- Finally grokked functional programming

Although sadly I read a lot less this year than last. I guess a lot of big stuff happened this year …

Yeah I suspect your latter point is very much the case and part of my point.

I guess it was an interesting tradeoff they made early on that seems to have paid off. I just wonder what the development experience is like…

Has anyone actually really noticed the performance of Stack Overflow? It feels like your average website before the JS bloat took over most “forum” style sites. I wonder if they’ve traded off performance (and by the sounds of it, maintainability) with cost by squeezing all they can out of a minimal amount of hardware.

I feel like having automated testing though is objectively beneficial. I imagine SO make up for that by having a QA team and spend a heap of time manually testing stuff at the expense of “performance”.