krzepah

I agree with you, the caching mechanism and ways to communicate with the API from your scripts would have been way more interesting to read about

Be honest, try to give them other options as soon as possible, give them a number their future potential employer can call. Maybe even write something

lmao :')

Hi !

Am I missing something ?

Direction out of touch with the importance of cultural well-being. At this point I'm not accepting talks with companies that do that and point them to their online onboarding and processes. If they are so lonely that they value what they see more than the work done then I have other companies and other priorities.

When I read things like that it pulls me away even further from continuing CS. How blind are you that you do not realise that forcing a software execution is not ransomeware ?

I'll tell you what's wrong here : Docker is a fantastic technology but it simply couldn't find a suitable market tactic.

Now it resolves to this shitty practices. I don't even know how you can begin to think that it would add ANY burden to them NOT to run the update on your computer.

And here is my problem : It's my computer, I decide what is ran on it or not.

Next day we have some idiot getting keys on the docker update system and we simply have built a technologic crash because suddenly nobody can decide wether that update is ran or not.

Keeping control away of the user is the most stupid thing there is.

I've got another one : It's your device, you shouldn't be locked out of it because of some update that now requires you to authenticate to whatever online service they have the fantastic idea of coming up with.

The most stupid thing I can think of is that the downloader changes version less often that the said software. So you download your "downloader" which points you to the latest version of the software.

Not related to this, but I got locked out of my apple account few days ago, this means : loose of everything I bought, cannot update any software. Only way to retrieve said account was trough a SMS system that was locked on a non mobile phone. They nicely allowed me after to use my email account for it (which was already linked), and promptly asked me to a new number.

To my surprise, this account status went back to it's original state (which mean I STILL have to re-do all of this process) and I'm still locked out of it.

But they took my money, they took my phone number. And they are happily locking me out every few because they basically do wtf they want.

I'm not buying any apple product anymore and I'm making sure everybody I know about knows about it. This company is a lie. These people are doing racketing in day light.

Microsoft has trouble with UI design and it only got worse. Think about the "help" buttons that are on win system preferences, instead of directing you to the option they send you to google or bing. It's ridiculous.

fun fact comment, Asimov thought about this, I'm quoting the short part that is relevant from this article on wikipedia :https://en.wikipedia.org/wiki/Foundation_series "One key feature of Seldon's theory, which has proved influential in real-world social science,[3] is the uncertainty principle: if a population gains knowledge of its predicted behavior, its self-aware collective actions become unpredictable."

What I dislike about heavy test process is that you basically might be writing b*lshit until your product owner validates the implementation.

You are making judgments about OP using Docker. But from my point of view you are a true pain to work with because you do not containerise your work. Anytime I'd have to work with one of your creations I'd have to go figure what you are using, set it up and make sure it works. That's a waste of time and you are promoting that very fact because you were unable to figure any usage for it. I doubt OP has only "read some blog post about it somehwere" It's literally wide in usage by a lot of companies. "People who like Docker often seem to be working in larger teams, which is totally fine and they're probably right to use Docker." -> it's actually about that, it is useful is scaling that's true, but it's also very useful just to share the env your software should work with. And I'd dare to say that giving a Dockerfile is now standard practice.

"Just use the same Python version and a roughly similar PostgreSQL version in development and production, and you're good to go" -> And that's more time than it would take to re-use that Dockerfile and docker-compose that i literally wrote once and go to once in a while.

Hi,

Having a React / Vue whatever in addition to your Django server allow you to split the "View" from the "Model-View-Control" paradigm that Django respect, when you have django & react, Django is only "MC" and react becomes "V"

Simply put, when you are in the template paradigm you are producing HTML files, when you are using React you are generating HTML.

For instance, I'm not building up an "account" page, i'm building up a "detail" page that can be reused with a query that I'm passing in. That query is a function that defines the call to Django. Eventually I'm passing parameters to the component to drive it's behaviour.

I'd simply suggest you to go learn some react, it is difficult and it takes time, but it will allow you to see more solutions to problems that you might be handling in the "industrial" way (eg: writing 10 templates and having some jquery mixxed in the html)

I've been working with django and react for a while now, and i'm now used to 100% coverage without much hassle and very good productivity (dare I cite my boss :) )

"I don't want to go full SPA with Django as this defeats the purpose of Django IMO" -> What is this "purpose" ? Django is here to help me model my database, handle few permissions and bring few API up online, I see no problem with having a PWA in front of it. Are you trying to get all of your website server rendered ? In which case you could do that without having to worry about integrating it with Django... TBH after 5 years of react and 8 of Django, i'm just not mixxing them up except for the front-end calling a query on the back-end (which both can be served at the same domain using nginx) ;

It is not. If you intend to have a react front-end then this front-end becomes the "V" in the MVC, while django becomes only the M & C;

Having something cohesive is much more reliable than having some template there, some js there, some template there again.

If you stick up to one way of doing things, testing and debugging becomes trivial because you are not mixing up three different way of doing something

Honestly in the real world you would generally already know if the need expressed is meant to be a web service (for instance) and if it requires a database - and in those cases, most framework already propose an sqlite / fully-fleged database in the same code.

If we already know that a database might be required later then using something like sqlite straight is smart move that would allow you to write code that is instantly going to work when you actually need something fully fledged instead of re-writing it.

Knowing if you need a database or not is simply one of the first things you know, and writing code before setting that up is a waste of time or a learning process.

Programmers write code. Good programmers think about data movement

Simplicity is what strikes the brightest of minds, some prefer to have simple shortcuts and a tone of sh*tware that prevent the user from knowing how to use it's tools (git, configuring an IDE), some prefer to have something they can master over the years, is standard in the industry, and that doesn't induce tons of un-controlled behaviours.

What are you talking about ? Most people working with sound today do so by using a DAW like Ableton, QBase or Fruity Loop that work on Windows or sometimes Mac Os

Thank you for the summary

yup ^^

Actually don't say you are going to "porter plainte" in a café, you will look like a Karen with extra steps

edit : Porter plainte means filling the papers to a Police station to start a judiciary procedure against someone, you'd do that for violence, theft, rape etc...

I haven't rushed out to hooks when they got out (i'm a preact user not react) to the point that I got an intern tell me "Oh you don't use hooks, I'm not used to work like that".

After digging into them, they are a nice addition for some specific niche scenario where the component is not using any kind of global storage. But from the little experience I had, they bring almost nothing new (I could do the same without them) and they are also kind of difficult to read.

If I had to put a ADR for it, I'd simply skip it trough and specify storage / class components as being much better just because of readability and consistency.

Now maybe they have some better perf but it seems to me they are an addition that came because of the functional frenzy that react has gone trough.

Maybe we got too far, maybe we didn't really need them. Maybe they just look cool.

In the end, i've replaced all my hooks with either GS or Component just because I'm more confident about how my peers will be able to read the code.

Thanks for the read ! I didn't know svelt and it seems like it has solid motivations. I should definitely check it out.

I'm actually more of a preact fan and the community Jason Miller has created, their work have inspired me a lot in concern of front-end and javascript dev.

ctrl-f hook is effectively something that has to be considered when implementing such feature.

I'd argue that the list & search feature it self is hard, not as something to put on and program and get working, but as a user-experience and design perspective (I'd like to thank you about pointing that out by the way, I will definitely spend some time making sure it's there for my app)

The reason I can think of, is that we do actually take control over parts of the applications in a way that was not imagined when browsers implemented search function.

It almost feels like the "With big power comes big responsibility", but i don't like the word "power" in our case, so I'd change it to something alike to "With features that have extra consequences we need to have an equal amount of extra care to even considering them." as if it was hidden and we needed to understand the tool better to have it properly done.

I guess front-end dev is easy to get in and understand, but hard to master, and that could be why we end up with these rampant "half-done" apps that do not take those extra steps.

In the end, the rushed dev will probably just look to have it's app working and will not check these kind of "bugs" that have been caused by his decisions,

Tbh, without this discussion i'd probably have missed it too

Honestly I like HN but the constant talk about PWA vs pure HTML apps has became tiresome and unproductive. I haven't seen a single argument that's properly stated about why we shouldn't do them.

Having argument alike "Oh I have to dev that feature therefor X sucks" is not a good enough opinion that i would like to read here neither.

What are you talking about ? Are you saying a search feature is not necessary in my specs because you like using f3 or ctrl-f ?

"On mobile, using menu to search in browser menus" -> This is not a sentence.

I do add a "few bytes" to "reimplement" a "browser feature" ; but the reality is that i HAVE to implement search because it is hitting on 730000 per year records;

How is you ctr-f or f-1 feature is gonna search on 2190000 rows in 3 years ?

Again, you are too happy about your opinion that you spite it out like truth without even understanding specs.

Specs is what allow you to understand what's required, it makes no sense what so ever to talk about technology without understanding WHY you use it in the first place.

Is it meant for public ? employees ? How many rows do they deal with in their actual everyday workflow ?

You are pushing your workflow so much that you don't even consider about your users and that's another red flag for me.

PWAs have given so much in term of capabilities and mastery that I honestly wonder why I'm still talking about such things on HN while proper workflow about architectural design are ignored here.

Thanks i haven't thought about that one. But i'd definitely try to stick up to css even if I'd have to dev that feature. Maybe by trying to change the var(--color) i've setup in my colors.css ;

I'd note out that this feature is also so edgy that the pushed argument shouldn't even occur that much.

It would be like "Oh hei, I need to dig up that super edgy star shaped hole using that shovel so I'm using it that way. Oh see, when I use it that way i'm inclined to do X. Therefore my shovel is encouraging me to do X."

There is a great article that went uncommented on HN about Architectural Decision Records.

https://github.com/joelparkerhenderson/architecture_decision...

The simplest of them include "consequences" of architectural decision. For PWA these include the development of that kind of features.

Now to be absolutely honest. I prefer having a dedicated back-end that does one thing well and a front end that does one thing well. Even if I have to put in extra effort with few features just to have my source-code more dedicated and therefore cleaner to work with.

The thing is that PWA not only included the front-end dev, they also reduced the complexity of back-end. And that's a huge win I'd pay with these kind of features happily.

Stop crying around on HN and go dev your feature