@Angel_gaitan_of@Porcelanosa_es Menudo pringao, ahora te llamará el gerente de una empresa que factura 1.000M€ porque no van a venderte las baldosas para tu taller cochambroso
@DAZN_ES@RCCelta 1) La amarilla a Gerard en el minuto 2 es una vergüenza
2) Esta sería su 2ª falta que hace, y cuanto más la veo, menos veo que toque a Aspas
3) Quien sí tocó a Raphinha es Mingueza pisoteando su tobillo en acción de roja con VAR, que no fue ni amarilla, a Ferran en Girona roja
I took an image of a 1-month price graph of $NVDA and gave it to @AnthropicAI Claude Opus Vision Model to analyse.
Here is the prompt I used:
This is 1 month price graph. Perform technical analysis and tell me if this is a buy or sell signal. Also indicate your level of confidence in the analysis
This is the analysis it gave after "seeing" the chart:
--------------
Based on the technical analysis of the 1-month price graph for NVIDIA Corporation, this appears to be a sell signal with a relatively high level of confidence. Here are the key observations:
The stock price has formed a clear bearish reversal pattern known as a "double top" around the $878 level. This pattern suggests that the uptrend has lost momentum and a trend reversal may be imminent.
After forming the double top, the price has broken down below the support level around $840, confirming the bearish signal.
The RSI has formed a bearish divergence, where the price made higher highs while the RSI made lower highs. This divergence indicates that the bullish momentum is weakening and a reversal is likely.
The stock price has closed below the short-term moving average (not shown in the image), signaling a potential shift in the trend from bullish to bearish.
The trading volume has been relatively high during the recent price decline, which is a negative sign as it suggests strong seller interest.
Confidence level: High (8-9 out of 10)
The confidence level in this sell signal is high because multiple bearish technical indicators are aligned, including the double top pattern, the breakdown below support, the bearish RSI divergence, and the close below the short-term moving average. Additionally, the high trading volume during the decline adds credibility to the bearish signal.
However, it is important to remember that technical analysis should be used in conjunction with other forms of analysis, such as fundamental analysis and risk management techniques. Investors should always conduct their own due diligence and consider their individual risk tolerance before making any investment decisions.
𝗛𝗼𝘄 𝘁𝗼 𝗯𝗲 𝗮 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝘃𝗶𝘁𝘆 𝗺𝗮𝘀𝘁𝗲𝗿?
Use a few simple techniques:
1. Focus on ONE thing. Block your time in the calendar for everything and try to focus on the current task only.
2. Use 3:3:3 Plan. 3h to work on your most important projects. 3h for shorter tasks. 3h for maintenance activities.
3. Use a deep work practice, for at least 4h per day, with no distractions (use airplane mode on your phone).
4. When learning something new, apply the Feynman Technique. Pick a subject, attempt to explain it to a 5-year-old, then do more research to fill in any knowledge gaps.
5. Organize your duties according to an Eisenhower Matrix. The aim is to spend more time on vital tasks that advance your long-term values, missions, goals, and principles.
6. Processing messages and emails in bulk during one to three condensed times during the day.
7. If you want to improve in something, do it for 20mins per day. After a year, you will be better than 90% of people.
8. Use the Getting Things Done methodology to track everything you do efficiently.
9. Use Zero Inbox Policy. Get rid of unnecessary emails immediately. If the email requires someone else's attention, forward it. If an email takes less than a few minutes to reply, do it directly; otherwise, schedule a time to deal with it.
10. Beat procrastination with Pomodoro. Choose a task, set a timer for 25min and work on it without distractions, take a short break, and do it again. After 4 sessions, take a more extended break.
11. Create yearly, monthly, weekly, and daily goals and plans. With the goal, you will probably get nowhere.
12. Do daily and weekly reviews. Ask yourself: "What did I do today that was aligned with my goals?" "Can I improve something?"
13. Learn to say NO to many things! One no is yes to many other things.
14. Walk 30mins every evening. Even better, do a walking meditation during this time.
15. Automate everything you can. Try to use different tools to automate everything you can, especially repetitive tasks.
To learn more about it, check out my newsletter in the comments.
#technology #softwareengineering #techworldwithmilan #productivity #gettingthigsdone
𝗧𝗼𝗽 𝟮𝟬 𝗦𝗤𝗟 𝗾𝘂𝗲𝗿𝘆 𝗼𝗽𝘁𝗶𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝘁𝗲𝗰𝗵𝗻𝗶𝗾𝘂𝗲𝘀
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
𝗙𝗮𝗰𝗲𝗯𝗼𝗼𝗸 𝗰𝗿𝗲𝗮𝘁𝗲𝗱 𝗮 𝘁𝗼𝗼𝗹 𝘄𝗵𝗶𝗰𝗵 𝗱𝗲𝘁𝗲𝗰𝘁 𝗮𝗻𝗱 𝗿𝗲𝗽𝗮𝗶𝗿 𝗯𝘂𝗴𝘀 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗰𝗮𝗹𝗹𝘆
The recent document by engineers from Facebook explains how they wrote a tool that can automatically fix bugs. In the paper, they introduced 𝗦𝗔𝗣𝗙𝗜𝗫, an automated tool designed to detect and repair bugs in software. The tool has suggested fixes for six essential Android apps in the Facebook App Family: Facebook, Messenger, Instagram, FBLite, Workplace, and Workchat.
How Does It Work?
𝗦𝘁𝗲𝗽 𝟭: Detect a Crash - Another tool, 𝗦𝗮𝗽𝗶𝗲𝗻𝘇, finds app crashes. When Sapienz identifies a crash, it is logged into a database.
𝗦𝘁𝗲𝗽 𝟮: Identify the Problem - SAPFIX pinpoints the exact line of code causing the issue. It first checks if the crash is reproducible. If it's not reproducible, the crash is discarded. It uses a technique called "spectrum-based fault localization" to identify the most likely lines of code responsible for the crash.
𝗦𝘁𝗲𝗽 𝟯: Suggest a Fix - Using predefined templates or code mutations, SAPFIX proposes a solution. After identifying the fault location, SAPFIX attempts to generate a patch. It employs two strategies:
🔹 𝗧𝗲𝗺𝗽𝗹𝗮𝘁𝗲-𝗯𝗮𝘀𝗲𝗱 𝗙𝗶𝘅𝗶𝗻𝗴: SAPFIX uses predefined templates to suggest fixes for common bugs. These templates are designed based on standard developer practices.
🔹 𝗠𝘂𝘁𝗮𝘁𝗶𝗼𝗻-𝗯𝗮𝘀𝗲𝗱 𝗙𝗶𝘅𝗶𝗻𝗴: SAPFIX resorts to a mutation-based system if the template-based approach fails. It systematically applies a series of code mutations to the fault location to generate potential fixes.
𝗦𝘁𝗲𝗽 𝟰: Test the Fix - The proposed solution is tested to ensure it's valid. It uses the test cases from 𝗦𝗮𝗽𝗶𝗲𝗻𝘇 to check the validity of the patch. If the patch passes all tests, it's considered a good fix. After patch validation, SAPFIX uses 𝗜𝗻𝗳𝗲𝗿 (a static analysis tool) to analyze the proposed fix further. Infer checks if the patch introduces any new potential issues.
𝗦𝘁𝗲𝗽 𝟱: Review - Developers get the final say, reviewing and approving the fix.
Check the entire document in the comments.
Image credits: Facebook.
What do you think about this?
_______
If you like my posts, please follow me, @milan_milanovic, and hit the 🔔 on my profile to get a notification for all my new posts.
Grow with me 🚀!
#technology #softwareengineering #programming #techworldwithmilan #coding
Another massive week for AI.
Major developments from UCSF, Meta, CoDeF, Midjourney, IBM, OpenAI, Snapchat, Microsoft, Banijay, Google, Twilio, Hugging Face, Nvidia, Amazon, China, India, YouTube, and Genesis Therapeutics.
Here's the rundown (thread 🧵):
La IA puede aumentar la productividad de los negocios un 40%.
Y el 77% de nuestros dispositivos la usa.
Sin embargo, solo el 33% de la gente sabe sacarle provecho.
Por eso, te traigo 7 de las mejores herramientas con IA para potenciar y mejorar tu marketing:
Madrid produce el 5% de la electricidad que consume.
No solo las demás provincias ponemos nuestros parajes para abastecerlos, si no que ahora no quieren ahorrar como los demás porque claro, Madrid es España.
.@Helium, often cited as one of the best examples of a Web3 use case, has received $365M of investment led by @a16z.
Regular folks have also been convinced to spend $250M buying hotspot nodes, in hopes of earning passive income.
The result? Helium's total revenue is $6.5k/month