Arif Setyawan retweeted
Kopi tubruk adalah human right. Minum kopi tubruk pagi, siang, sore, malam adalah Asian value.
Jangan tubruk yang lainโฆ
Ini ada yang capture potongan tabel jurnalnya. As expected pada banyak yg salah ngambil simpulan. Atau telan mentah2 simpulan orang lain.
Wasweswos
#mbelgedhes
Replying to @alandakariza
Di Instagram pada ngomelin gue, katanya mungkin semua respondennya laki-laki~
Sampai gue cari artikel jurnal yang disadur. Kita udah bener kok ๐
Respondennya laki-laki dan perempuan perokok. 95% perokok yang disurvey itu laki-laki.
Artikelnya: journal.fkm.ui.ac.id/jurnal-โฆ
50
Kayaknya salah ngerangkum iniโฆ
Sumbernya juga ga mudah diakses.
Pure cari traksi ini postingan.
#weakReference
This Post is from a suspended account. Learn more
1
75
Arif Setyawan retweeted
Laporan Keuangan Full Year 2023 GOTO sudah terbit
GOTO tercatat rugi Rp 90,4 Triliun !!!
Sebanyak Rp 78.7 Triliun di antaranya adalah Goodwill
Apa itu Goodwill ? Mengapa bisa besar sekali ?
BUKAN REKOMENDASI BUY SELL HOLD
Arif Setyawan retweeted
๐ง๐ผ๐ฝ ๐ฎ๐ฌ ๐ฆ๐ค๐ ๐พ๐๐ฒ๐ฟ๐ ๐ผ๐ฝ๐๐ถ๐บ๐ถ๐๐ฎ๐๐ถ๐ผ๐ป ๐๐ฒ๐ฐ๐ต๐ป๐ถ๐พ๐๐ฒ๐
Here is the list of the top 20 SQL query optimization techniques I found noteworthy:
1. Create an index on huge tables (>1.000.000) rows
2. Use EXIST() instead of COUNT() to find an element in the table
3. SELECT fields instead of using SELECT *
4. Avoid Subqueries in WHERE Clause
5. Avoid SELECT DISTINCT where possible
6. Use WHERE Clause instead of HAVING
7. Create joins with INNER JOIN (not WHERE)
8. Use LIMIT to sample query results
9. Use UNION ALL instead of UNION wherever possible
10. Use UNION where instead of WHERE ... or ... query.
11. Run your query during off-peak hours
12. Avoid using OR in join queries
14. Choose GROUP BY over window functions
15. Use derived and temporary tables
16. Drop the index before loading bulk data
16. Use materialized views instead of views
17. Avoid != or <> (not equal) operator
18. Minimize the number of subqueries
19. Use INNER join as little as possible when you can get the same output using LEFT/RIGHT join.
20. For retrieving the same dataset, frequently try to use temporary sources.
Do you know what is ๐ค๐๐ฒ๐ฟ๐ ๐ข๐ฝ๐๐ถ๐บ๐ถ๐๐ฒ๐ฟ? Its primary function is to determine ๐๐ต๐ฒ ๐บ๐ผ๐๐ ๐ฒ๐ณ๐ณ๐ถ๐ฐ๐ถ๐ฒ๐ป๐ ๐๐ฎ๐ to execute a given SQL query by finding the best execution plan. The query optimizer works by taking the SQL query as input and analyzing it to determine how best to execute it. The first step is to parse the SQL query and create a syntax tree. The optimizer then analyzes the syntax tree to determine how to run the query.
Next, the optimizer generates ๐ฎ๐น๐๐ฒ๐ฟ๐ป๐ฎ๐๐ถ๐๐ฒ ๐ฒ๐
๐ฒ๐ฐ๐๐๐ถ๐ผ๐ป ๐ฝ๐น๐ฎ๐ป๐, which are different ways of executing the same query. Each execution plan specifies the order in which the tables should be accessed, the join methods, and any filtering or sorting operations. The optimizer then assigns a ๐ฐ๐ผ๐๐ to each execution plan based on the number of disk reads and the CPU time required to execute the query.
Finally, the optimizer ๐ฐ๐ต๐ผ๐ผ๐๐ฒ๐ ๐๐ต๐ฒ ๐ฒ๐
๐ฒ๐ฐ๐๐๐ถ๐ผ๐ป ๐ฝ๐น๐ฎ๐ป with the lowest cost as the optimal execution plan for the query. This plan is then used to execute the query.
Check in the image the ๐ผ๐ฟ๐ฑ๐ฒ๐ฟ ๐ถ๐ป ๐๐ต๐ถ๐ฐ๐ต ๐ฆ๐ค๐ ๐พ๐๐ฒ๐ฟ๐ถ๐ฒ๐ ๐ฟ๐๐ป.
#technology #softwareengineering #programming #techworldwithmilan #sql
Arif Setyawan retweeted
If you're looking for a new job, don't simply tell your interviewer:
- "I've been a software engineer for 3 years"
You should measure your own experience in qualitative terms. Not number of years.
Try these ideas instead:
Arif Setyawan retweeted
|๏ฟฃ๏ฟฃ๏ฟฃ๏ฟฃ๏ฟฃ๏ฟฃ๏ฟฃ๏ฟฃ๏ฟฃ๏ฟฃ๏ฟฃ๏ฟฃ๏ฟฃ|
| We Love Open-Source |
|๏ผฟ๏ผฟ๏ผฟ๏ผฟ๏ผฟ๏ผฟ๏ผฟ๏ผฟ๏ผฟ๏ผฟ๏ผฟ๏ผฟ๏ผฟ|
\ (โขโกโข) /
\ /
โโ
| |
|_ |_
Arif Setyawan retweeted
๐ Go 1.21 Release Candidate 4 is released!
๐โโ๏ธ Run it in dev! Run it in prod! File bugs! go.dev/issue/new
๐ Announcement: groups.google.com/g/golang-aโฆ
โฌ๏ธ Download: go.dev/dl/#go1.21rc4
#golang
Coding can be incredibly rewarding. There's nothing quite like the feeling of finally getting that piece of code to work, or solving a particularly tricky bug.
1
1
177
Finally, don't be afraid to ask for help. There's a common stereotype of the lone coder who never asks for assistance, but the truth is that everyone needs help sometimes. Don't be afraid to reach out and ask for it.
1
1
144














