Hacker Newsnew | past | comments | ask | show | jobs | submit | tcbasche's commentslogin

McFlimsey and Company


Thanks ChatGPT


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.


I'd say this is mostly due to the fact that building software in many companies is largely a social activity, and there's an interesting intersection of personalities and motivation that ultimately disincentivizes building good quality software


I love that first point and I wish it was something that was applied even further to other pieces of data - integers and floats are intended for mathematical operations and so to make database row identifiers integers always seemed strange to me.


That's a symptom of what's known as Primitive Obsession. Back in the days of programming languages before declaring new abstract data types with either prohibitively expensive (in time and/or memory) it was valid limitation. Today, there's rarely an excuse.


Doesn’t it kinda depend on the problem at hand? Or maybe I misunderstand what a design pattern is.


Have you tried talking to them one on one?


tests

Do you really step through the debugger to see if something works?


When a test fails it can be difficult to pinpoint where in the pipeline it's failing. Using a debugger and setting break points is really helpful to help find the location where things are going wrong.


So you debug it then you write the tests? Or you write the tests first then you debug? Because you gotta debug it at some point.


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/...


> Things like 'get_object_or_404'[1] should be burned to the ground.

Why? A shortcut like that is useful all the time when writing URL handlers (views in Django).


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


So we should also get rid of `.orElseThrow()` (by default a `NoSuchElementException`)?


If it was .orElseReturn404 then yeah. My point is HTTP codes have no place outside of HTTP endpoints


Sweeping generalisation or what?


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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: