use tailwindcss but still use inline css 😑

I don't like when client decide which tech use in the project. I got some weird tech request like:
1. Move existing database from postgresql to Hadoop because hadoop is Big Data (is kinda move from amazon rds to amazon s3 just why? have you index, cluster your postgresql table?)
2. Move from mysql to postgresql because mysql cause deadlock (maybe their previous developer just fucking moron)
In this situation we just explain why we don't use that and propose alternative solution. If they insist with their solution either ignore it or decide not continuing the project.

Today I got fierce fighting against rust compiler, It was stressful but fun at the end :)

I got some problem. I work on some company maintaining web application. Every time I add some feature I often accidentally break other features. I read about testing (unit test, integration testing, etc) and ask my project manager and CTO to implement test on our web application but they refused it. The reason is because the web application is already large and it will take a long time to implement. Actually maintain this application is very stressful because it takes along time to add new feature and every time I break something either CEO or Client will scold me. Do you guys have idea/solution to solve this problem?

this afternoon, we got email from our pentester. He said that he got some security vulnerability in our project. He found .git/ folder in project directory in production server. He considered it as security vulnerability because user can see all git branch on remote repo. He recommend us to remove that folder but the problem is, we using CI/CD so we need that .git/ folder. My question is it bad practice to use git on production server?

Any suggestions/tips or tricks how to find linux compatible laptop? I can't buy preinstalled linux laptop (system76, tuxedo, purism, etc) because is not available in my country.

have you ever experienced this in postgresql? Remove unique constraint in table, end up remove all data on table. My friend experience this issue this morning. Is it possible? or due my friend clumsiness?

I found weird that some developer never ask why when facing a problem. "What do you mean never ask why?" here some story.

Let's say a developer work with simple app. Laravel as Backend and Postgresql as Database. He face a problem that the app very slow when searching data.

In order to solve that problem he implement cache using redis but he found problem that it fast occasionally. In order to solve that problem he implement elasticsearch because he think elasticsearch very good for search but he found another problem that sometimes data on postgresql out of sync with data on elasticsearch. In order to solve that problem he implement cronjobs to fix out of sync data but he found another problem that cronjobs cannot fix out of sync data in real time. and so on...

Do you see the problem? He never ask why the app slow. Which part search the data? Backend or Database (Search in the Backend mostly slower than Database because Backend have to get all data on database first). Has the query been optimized? (limit offset, indexing). How about the internet connection? etc.

For me it's important to ask why when facing a problem and try to solve the problem as simple as possible.

git commit message that I hate:

1. "Adjustment"
2. "Improvement"
3. "Fix Bug"
4. "I commit it but there are bug in this code"
5. "Client request"

YOU KNOW BE MORE SPECIFIC ON YOUR COMMIT MESSAGE!!!

I see some of web framework use .env to store configuration file (eg Laravel, CI). Is there any benefits to store configuration file on .env file? Is it consider a good practice?

redux? why use redux? while you can put all global state in localstorage. (hmmm... -_-)

Our story start like this.

Boss: Hey programmer A, Can you implement {feature X} on this application?

Programmer A: I suggest not implement {feature X} because {negative impact of feature X}

Boss: Ok

Boss asks Programmer B.

Boss: Hey programmer B, Can you implement {feature X} on this application?

Programmer B: Of course, no problem

Programmer B asks Programmer A.

Programmer B: Hey Programmer A, Do you know how to implement {feature X} on this application? I have no idea.

Programmer A: WHAT!!! do you know that {feature X}, Will negatively impact our application?

Programmer B: Well that's our boss want, I can't say no.

Programmer A: (F**k I hate this guy)

We move to microsevice architecture to improve our web performance, Is that make sense?