bluewalt

I just found out this package and absolutely love the idea of "sanitizing" the queries. However I'm just wondering: if I'm a solo dev and I already monitor all my endpoints using Django Debug toolbar, how is it still useful to use this package?

Exactly. I end up to get use to this fuzzy text, but the first time was like "Ughhh this is ugly".

Another major issue not mentioned with non-retina displays is that you have to chose between a decent on-screen text size and pixel scaling.

For example, I use a a 4K 27" LG monitor. If I use native 4K resolution, the text is way too small. If I use 2:1 resolution, the text becomes too big and I lose real estate. I ended up with a scaled resolution with pixel approximation. I won't explain here why it may be a problem for some people, but it is.

> links can change

I guess you could use bit.ly links rather than direct urls to build an abstraction

Question: can you read cards from the other side? I mean, imagine your cards are stuck on a wall in your room, can you still read them?

Great! I'd like to do the same but not sure of using NFC tags rather than printing and sticking QR Code stickers directly to the back of the card? Please help me compare both approaches. For now, I'm thinking of:

Pro's of QR Codes: Cheaper to print, no configuration required, any smartphone can use it.

Pro's of NFC Tags : Better listening workflow without having to open camera

I must +1 this, Django ninja is outstanding.

For me, the BaaS philosophy is to simplify development by using an "all-batteries-included" platform. I know some people use Supabase just for the free postgres or other things, but I don't like to use multiple providers for a single simple project. That's why it makes no sense to me currently to use Supabase until there is no functions.

For everyone opposing Django to FastAPI, please take a look to the excellent Django Ninja: https://django-ninja.rest-framework.com/

And you end up with tons a network calls and services to monitore, logs, manage and pay.

I'd do the exact opposite by default, trying to have the most cohesive service, and occasionnaly use some external APIs when I can't do the stuff by myself (eg. Stripe)

That's a very strong advice to remove irrelevant guilt. Many people bind success with money. That's just one thing you can benefit.

That's a relevant advice IMO.

However, as a tech guy trying to build stuff too, I need continuous motivation for this. I need to stay in a "flow" state. And a good fuel to this is to learn new cool things during the journey.

To put it differently, I think you need to find the right balance between fun and efficiency, even if your goal is to earn money in the end. Trying to always look for the maximum efficiency could be a short term vision that quickly lead to boringness.

https://noteplan.co/ -> Calendar, notes, and todo in the same place. Very convenient to me.

"Thousands of businesses in production" + "still pre-1.0" in the same sentence perplexes me a lot.

You can not say you get feature parity just after plugging an ORM to express. Of course if you're building a todolist, I understand the point, but as soon as you have more need, the journey of searching for packages, comparing them, test them, read their doc, starts. Some things I have in mind: security, authentication, file uploads, role management, testing, cache, admin, etc.

I don't know Phoenix enough to make a fair comparison, but I'd say it have major features Django doesn't have (like LiveView), but the opposite is probably true.

But as soon as you go to the JS world, you won't find any full-featured framework like Django or Rails. The Django's philosophy is that all components are built by Django team itself whereas in the JS world, existing frameworks tend to gather independent components and define conventions to make them work together in an elegant way, which is very different.

While it sounds neat in its area, it seems to be the same philosophy than nest js: an opinionated way to gather a set of trendy tools (React, GraphQL, Prisma, Jest, WebPack, Babel, etc.) and enforce conventions around them.

To me, it remains different from Django (or Rails) in a sense Django developed all the framework components themselves, which has major implications.

As you said, you define your creativity by your code itself. I think some programmers (at least me) want a wider freedom, for example about features, or process, or devops stuff, etc etc. I think the more you're in a big structure with defined roles, the more it's difficult to have this freedom, not only about the way to code, but the way to work.

I thought it was a clickbait at first, but to be honest, the first paragraph sounds sadly true to me. I have been a CTO and co-founder and loved coding that way, because it was a highly creative job, in which my brain was used for many other things than coding.

But now, I'm looking for a new job, and what I feel with permanent positions as a full stack developer I'm applying for, is that business/management people are looking for nerdy people to EXECUTE their visions ("heyyyy we need a ninja hacker, you'll have free beers and pizzas !").

Sometimes I have the feeling that if I introduce myself as a developer, I look like 10 times worse than what I actually am.

PS: I'm not living in California, developers are not considered rockstars everywhere in the world, unfortunately.

I think this mindset can lead to missing opportunities to build products actually faster. Having both code-first and product-first in your company is truly complementary IMO.

CEOs that only wonder "can it be built fast" have a very short term vision. I keep hearing things like: "anyway, we are a startup so we will pivot hence code quality is not important right now, we need to push features!". The thing is, you don't need to reach many years so that "average to bad" code makes a new feature 10x longer to be delivered. Any experienced developer understand how a good code is truly valuable to a company for delivering. And even if it's very true in long term, this is true as well at the very first stages.

But I'd say a very good developer is not product-first or code-first, he's both, you don't need to oppose both profiles. This very good developer is mature enough to know when a code refactoring will lead to a better productivity. And he's mature enough to know that this imperfect function is OK to keep as is because it has no real implication.

"Your Lifestyle has already been designed" from Raptitude blog. https://www.raptitude.com/2010/07/your-lifestyle-has-already... (the title is self explanatory)

- A sneaker cleaner kit, to keep my sneakers clean with no effort.

- A 15000 lux day lamp, because my apartment is pretty dark, why causes some sort of depressing feelings over time

- A Brita Water Filter Pitcher, which replaces all the bottles of water I needed to buy and carry.

- Magnet app (mac OS) to organize windows quickly with keyboard shortcuts.

May I ask why you don't manage to make your room completely dark instead of wearing a mask?

Technically speaking, I agree, but if you think of Uber for example, let's say you make the exact same app, how do you market it then?

Just don't read the answers to your comments :p

No cars in the center of the cities, only bike lanes, pedestrians, places. In cities like Paris, cars are completely useless.

> The dependency version is specified separately from the lock file.

That. The simple fact that a Pip file mixes both the packages you want and the dependencies required by this package, is a valid reason to switch to Poetry IMO.

I replaced all the pyenv (and any version management in my projects) by the awesome VS Code remote development with containers. This is a game changer to me. 1 container = 1 clean installation, completely isolated, and you can share with your teammates.

Then I disable the use of virtual environments in Poetry, because it's a useless overhead.

Then for updates, I just change versions in my Dockerfile or .toml and rebuild the container from scratch in a few time, which is cleaner than manual updates for everything IMO.

> Some people work with code from 13" laptops. And viewing diff of two files of 79 char per line max becomes very convenient.

I think it's not the only reason. Limiting columns forces developers to read more vertically, which is less tiring for eyes. For example, try to read a book on a 27' monitor with no max width. Going to the next line will quickly become painful.

I don't understand all the yelling about this Copilot stuff.

1) It's not your code that is proposed by copilot, but a mix of thousands and thousands codes, that can not be linked to one specific person. It's like you take 1000 portrait photos and make a new one. How can you prove your photo has been used?

2) How what's done by Github is causing you any damage, directly or indirectly? If you want to sue someone, you'd better prove any damage to a judge.

3) Because of all of this yelling, I'm pretty sure Github will add a per-repository option to disable code scraping. But I still don't understand what you'll win.