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

I thought those were common sense until I worked on a program written by my colleague recently.

That's also why it is difficult for me to tell what I've done in the standup meeting on another day. If I tell people I just spend time on "thinking", they will say it is too vague.


If you say "I was analysing the problem, and evaluating different solutions, and weighting the pros and cons, for example, I thought about [insert option A] but I see [insert contra here]. So I also thought about [option B]... I'm still researching in [insert source]". I do not think that should be a problem. Is what I say constantly in our daily's. And of course, eventually I deliver something.


I thought people here bypassed the paywall to read.


From the introduction, I can see a list of backend technologies. But do they have a high level architecture diagram? I don't know what I really need for production setup.


I wanted the same info, sadly lacking.

AFAICT needs a db (MySQL/Postgres) and a cache (Redis/Memcached) and one (or more?) web workers.

Then optionally also Celery workers (for "async queries" i.e. slow running)... not sure how optional that is though.


Database mess is unavoidable because it needs to support different kind of customers.


Apart from ChatGPT, I can find answer in reddit instead of SO.


The punch card is the "design". From the video, it isn't user friendly to edit on terminal. (btw, it is rare to see full English UI in Japan) They can just replace the part to create the punch card. But the textile machine is totally fine to keep consuming punch card.

Tape is fine too but it is risky because factory may stop creating tape.


Recently I ask ChatGPT to do that. I become the one to improve it.


Clippy



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

Search: