Pradosh Dash (@ppradosh) header
Pradosh Dash (@ppradosh) profile picture

Searching the meaning of life and trying to make the surrounding better for future...

india
Joined March 2011
Pradosh Dash retweeted
Freelancers are making $10,000 in a month 🔥🚀 700. Fiverr 699. Toptal  698. Jooble 697. Freelancer. com 696. Upwork 695. Flexjobs 694. SimplyHired 693. Linkedin ...... Choose the right platform & start earning in $DOLLARS 💰🤑 Simply: 1. Follow so I will Dm 📥 2. Like and Repost 3. Comment “send” to receive your copies!!
1,017
863
10
1,766
179,209
Data cleaning is one of the most important skills for a Data Analyst. Not Excel. Not SQL. Not PowerBI Without clean data, any analysis done is unreliable. Here's my Data Cleaning 101:
28
418
15
1,588
163,011
𝙏𝙧𝙖𝙙𝙞𝙣𝙜 𝙄𝙣𝙙𝙞𝙘𝙖𝙩𝙤𝙧 के 𝘽𝙖𝙨𝙞𝙘 𝙐𝙨𝙚-- 📍 MACD- बहुत सारे लोग इसका उपयोग Buy/Sell के लिए करते हैं । 📍 RSI- इसका उपयोग लोग Stock के Overbought/Oversold को पता लगाने के लिए करते हैं । 📍 BOLLINGER BAND- इसका उपयोग Volatility Level को Check करने के लिए करते हैं । 📍 9 EMA- इसका उपयोग ज्यादातर लोग Short Term का Trend जानने के लिए करते हैं और साथ ही TSL के लिए भी उपयोग करते हैं । 📍 20/21 EMA- इसका उपयोग बहुत सारे लोग Support/Resistance की तरह भी करते हैं जहाँ 20/21 EMA पर आने पर Buy/Sell की Opportunity खोजते हैं । 📍50 SMA- इसका उपयोग लोग Trend Check करने के लिए करते हैं । 📍 50 EMA- इसका उपयोग ज्यादातर लोग अपनी Position से Exit करने के लिए करते हैं । 📍 200 EMA- इसका उपयोग ज्यादातर लोग Long Term के Trend को जानने के लिए करते हैं और कई लोग अपनी Position भी Higher Time Frame पर यहां पर Entry/Exit करते हैं। 📍 VWAP- इसका उपयोग लोग Support/Resistance की तरह करते हैं और ये सबसे ज्यादा उपयोग होने वाले Indicators में से एक है। 📍 ADX- इसका उपयोग लोग Trend की Strength जानने के लिए करते हैं । इस पोस्ट को #BookMark कर लें जिससे बाद में Revision करते Time आसानी हो..साथ ही ज्यादा से ज्यादा #Retweet करें जिससे ज्यादा से ज्यादा लोगों तक पहुँच सके । जय केदार..कृपा अपार 🖤 #TradingStrategy #Learning
16
297
5
1,007
182,731
Five courses that will help you to learn Python: 1. Learn Python Learn the basics of the Python programming language, and why it's taking over in popularity. You'll get hands-on practice with all the building blocks to ensure you excel as a Pythonista. 🔗 boot.dev/learn/learn-python 2. Learn Object-Oriented Programming Build a link analyzer in Python that creates an internal linking profile of any website. 🔗 boot.dev/learn/learn-object-… 3. Learn Algorithms Big-O complexity is arguably the most important concept students learn in a formal CS degree. This Python course will give you the foundation you need to start your career off on the right foot. 🔗 boot.dev/learn/learn-algorit… 4. Learn Data Structures If you've had trouble getting past a hard whiteboarding session, this course is for you. You'll build data structures from scratch in Python and improve your problem-solving skills. 🔗 boot.dev/learn/learn-data-st… 5. Learn Advanced Algorithms Learn everything you need to ace tough technical interviews. This Python course covers graph theory, dynamic programming, and linear programming. 🔗 boot.dev/learn/learn-advance…
15
251
4
853
204,548
Clustering is a superpower. Learn it and you're an unstoppable force. Use these 5 powerful tricks to master clustering in 10 minutes: #datascience #python #rstats
16
182
3
1,149
299,777
Anyone with an Internet connection can learn Data Analysis for free: Excel - Microsoft Training Videos tinyurl.com/sxyuyd3m SQL - Mode tinyurl.com/mry3vsrz PowerBI - Udemy Course tinyurl.com/8ejmwjcb Python - Google Classes tinyurl.com/4nb2encb No more excuses.
22
744
6
1,929
248,864
Pradosh Dash retweeted
It's time to upgrade your LinkedIn profile. Forget about ChatGPT. You can use Leap AI (@leap_api) to generate your professional headshot in less than 10 minutes. Here's how to do it for free:
116
514
27
2,557
1,007,108
Don't pay ridiculous amounts of money to study Python, Data Science, and Machine Learning. Learn from the experts at Google, IBM, Stanford, MIT, and Harvard universities for FREE. (A thread) 👇 📌
12
262
1
870
180,507
Pradosh Dash retweeted
🤖 60 Days Of Deep Reinforcement Learning In this repo, You'll find everything well arranged from articles, tutorials, youtube videos, papers implementations, projects and codes. 🔗 github.com/andri27-ts/Reinfo…
2
138
1
429
50,540
Best YouTube Channels to Learn…
21
1,504
12
4,257
385,977
Pradosh Dash retweeted
Prepare for your next job interview with AI: 1: Mock interview with AI interviewai.me 2: Interview questions interviewgpt.ai 3: Interview notes metaview.ai 4: Resume scan accio.springworks.in 5: Job search matchthatroleai.com 6: Apply automatically applyish.com 7: Resume to jobs hnresumetojobs.com
42
1,297
17
3,314
497,486
Pradosh Dash retweeted
You can now fine-tune an LLM without writing a single line of code! A breakthrough in the open-source LLM space that can increase the speed of AI development and adoption by an order of magnitude. Let me start from the beginning: A Large Language Model comes out of the factory knowing many things but with little expertise. Take GPT-4, for example. It can speak without pause about mathematics but struggles to solve most problems. It knows about photography but not about my photos. It knows about business but can't say a thing about yours. Fortunately, we can teach these models specialized knowledge. For example, we can force a model to always answer in a specific way or show it facts about a domain it didn't know before. We call this process "fine-tuning." For many use cases, fine-tuning a model is the difference between getting mediocre answers or feeling the tool is pure magic. While OpenAI's models attract much attention, many companies use open-source models like LLaMA and Falcon. This gives them more control over their data, expenses, and how the model responds. Unfortunately, fine-tuning a model is neither a simple process nor cheap. It takes a lot of time and GPU computing. It's also hard to find experienced people who know how to work with these models. While you can choose your adventure and do everything yourself, the @monstersapi team released the ability to fine-tune a Large Language Model without writing any code. You can use it with any of the following models: • LLaMA 7B, 13B • Falcon 7B, 40B • OPT 125m, 6B • GPT J 6B • Stable LM 3B, 7B • GPT 2 XL Besides the obvious advantages of not dealing with code, complexity, or hardware, using their no-code tool will also let you fine-tune a model at a fraction of the cost! Their secret is using a decentralized GPU platform, which makes the process much more cost-efficient. There's a simple step-by-step demo you can follow that will show you how simple the process is. Link in the next tweet. You can try their platform with 5,000 free credits using the code SANTIAGO.
42
458
26
2,772
1,273,577
Pradosh Dash retweeted
Google is offering a Generative AI Learning Path with 10 courses for FREE! - Intro to Generative AI - Intro to LLMs - Intro to Image Generation - Encoder-Decoder Architecture - Transformer Models and more A Thread 🧵👇
15
256
9
938
249,754
This Google drive contain training materials on - Linux and AWS Training - DevOps - Git - Maven - Jenkins - Ansible - Docker - Kubernetes 🖇️ drive.google.com/drive/folde…
38
541
7
1,756
289,304
What are the most common 𝗨𝘀𝗲 𝗖𝗮𝘀𝗲𝘀 𝗳𝗼𝗿 𝗞𝗮𝗳𝗸𝗮? We have covered lots of concepts around Kafka already. But what are the most common use cases for The System that you are very likely to run into as a Data Engineer? 𝗟𝗲𝘁’𝘀 𝘁𝗮𝗸𝗲 𝗮 𝗰𝗹𝗼𝘀𝗲𝗿 𝗹𝗼𝗼𝗸: 𝗪𝗲𝗯𝘀𝗶𝘁𝗲 𝗔𝗰𝘁𝗶𝘃𝗶𝘁𝘆 𝗧𝗿𝗮𝗰𝗸𝗶𝗻𝗴. ➡️ The Original use case for Kafka by LinkedIn. ➡️ Events happening in the website like page views, conversions etc. are sent via a Gateway and piped to Kafka Topics. ➡️ These events are forwarded to the downstream Analytical systems or processed in Real Time. ➡️ Kafka is used as an initial buffer as the Data amounts are usually big and Kafka guarantees no message loss due to its replication mechanisms. 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗥𝗲𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻. ➡️ Database Commit log is piped to a Kafka topic. ➡️ The committed messages are executed against a new Database in the same order. ➡️ Database replica is created. 𝗟𝗼𝗴/𝗠𝗲𝘁𝗿𝗶𝗰𝘀 𝗔𝗴𝗴𝗿𝗲𝗴𝗮𝘁𝗶𝗼𝗻. ➡️ Kafka is used for centralized Log and Metrics collection. ➡️ Daemons like FluentD are deployed in servers or containers together with the Applications to be monitored. ➡️ Applications send their Logs/Metrics to the Daemons. ➡️ The Daemons pipe Logs/Metrics to a Kafka Topic. ➡️ Logs/Metrics are delivered downstream to storages like ElasticSearch or InfluxDB for Log/Metrics discovery respectively. ➡️ This is also how you would track your IoT Fleets. 𝗦𝘁𝗿𝗲𝗮𝗺 𝗣𝗿𝗼𝗰𝗲𝘀𝘀𝗶𝗻𝗴. ➡️ This is usually coupled with ingestion mechanisms already covered. ➡️ Instead of piping Data to a certain storage downstream we mount a Stream Processing Framework on top of Kafka Topics. ➡️ The Data is filtered, enriched and then piped to the downstream systems to be further used according to the use case. ➡️ This is also where one would be running Machine Learning Models embedded into a Stream Processing Application. 𝗠𝗲𝘀𝘀𝗮𝗴𝗶𝗻𝗴. ➡️ Kafka can be used as a replacement for more traditional messaging brokers like RabbitMQ. ➡️ Kafka has better durability guarantees and is easier to configure for several separate Consumer Groups to consume from the same Topic. ❗️Having said this - always consider the complexity you are bringing with introduction of a Distributed System. Sometimes it is better to just use traditional frameworks. -------- Follow me to upskill in #MLOps, #MachineLearning, #DataEngineering, #DataScience and overall #Data space. Also hit 🔔to stay notified about new content. 𝗗𝗼𝗻’𝘁 𝗳𝗼𝗿𝗴𝗲𝘁 𝘁𝗼 𝗹𝗶𝗸𝗲 💙, 𝘀𝗵𝗮𝗿𝗲 𝗮𝗻𝗱 𝗰𝗼𝗺𝗺𝗲𝗻𝘁! Join a growing community of Data Professionals by subscribing to my 𝗡𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿: newsletter.swirlai.com
29
394
5
1,606
240,202
Pradosh Dash retweeted
Free 10 week python course youtube.com/playlist?list=PL…
11
865
12
2,816
428,594
Pradosh Dash retweeted
Fundamentals of event-driven architecture Here are some thoughts I have been diving deep into this year, with things I learn about EDA I wanted to group them into three areas I think can help when you build EDA applications. Identify and design Like most things I think you have two options here, start implementing or stop and understand behaviour of your system. Previously I used to just dive in, but now understanding domain-driven design, event-first thinking it's important to map domains, highlight boundaries and design events before diving deep. Collection of patterns Once domains are identified, understanding messaging/event patterns can really help. Here we talk about integration patterns (e.g Claim check, splitter, message translator), just having an understanding of what patterns there are, can really help you map these patterns to various uses cases you will come across. Operational and maintenance Often overlooked, but how do you keep your EDA applications successful in 12-24 months? Should you be documenting your events/producers/consumers? What about standards in your events/architecture? What about distributed tracing for your events? These things need to be considered to make sure you have a high chance of success. If you want to learn more I have a visual and extra resources for you 👇 serverlessland.com/event-dri…
1
104
1
396
44,887
Pradosh Dash retweeted
Free complete Numpy library youtube.com/playlist?list=PL…
6
236
2
1,087
228,945
What is the difference between 𝗟𝗮𝗺𝗯𝗱𝗮 𝗮𝗻𝗱 𝗞𝗮𝗽𝗽𝗮 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲𝘀? Lambda and Kappa are both Data architectures proposed to solve movement of large amounts of data for reliable Online access. The most popular architecture has been and continues to be Lambda. However, with Stream Processing becoming more accessible you will be hearing a lot more of Kappa in the near future. Let’s see how they are different. 𝗟𝗮𝗺𝗯𝗱𝗮. ➡️ Ingestion layer is responsible for collecting the raw data and duplicating it for further Real Time and Batch processing separately. ➡️ Consists of 3 additional main layers: 👉 Speed or Stream - Raw Data here is coming in Real Time and is processed by a Stream Processing Framework (e.g. Flink) then passed to the Serving layer to create Real Time Views for low latency near to Real Time Data access. 👉 Batch - Batch ETL Jobs with batch processing Frameworks (e.g. Spark) are run against raw Data to create reliable Batch Views for Offline Historical Data access. 👉 Serving - this is where the processed Data is exposed to the end user. Latest Real Time Data can be accessed from Real Time Views or combined with Batch Views for full history. Historical Data can be accessed from Batch Views. ❗️ Processing code is duplicated for different technologies in Batch and Speed Layers causing logic divergence. ❗️ Compute resources are duplicated. ❗️ Need to manage two Infrastructures. ✅ Distributed Batch Storage is reliable and scalable, even if the System crashes it is easily recoverable without errors. 𝗞𝗮𝗽𝗽𝗮. ➡️ Treats both Batch and Real Time Workloads as a Stream Processing problem. ➡️ Uses Speed Layer only to prepare data for Real Time and Batch Access. ➡️ Consists of only 2 main layers: 👉 Speed or Stream - similar to Lambda but (optionally) often contains Tiered Storage which means that all of Data coming into the system is stored indefinitely in different Storage Layers. E.g. S3 or GCS for historical data and on disk log for hot data. 👉 Serving - same as Lambda but all transformations that are performed in Speed Layer are never duplicated in Batch Layer. ❗️ Some transformations are hard to perform in Speed Layer (e.g. complex joins) and are eventually pushed to Batch storage for implementation. ❗️ Requires strong skills in Stream Processing. ✅ Data is processed once with a single Stream Processing Engine. ✅ Only need to manage single set of Infrastructure. Have you dealt with Kappa architecture in your day-to-day? What are your thoughts around it? Let me know in the comments 👇 -------- Follow me to upskill in #MLOps, #MachineLearning, #DataEngineering, #DataScience and overall #Data space. Also hit 🔔to stay notified about new content. 𝗗𝗼𝗻’𝘁 𝗳𝗼𝗿𝗴𝗲𝘁 𝘁𝗼 𝗹𝗶𝗸𝗲 💙, 𝘀𝗵𝗮𝗿𝗲 𝗮𝗻𝗱 𝗰𝗼𝗺𝗺𝗲𝗻𝘁! Join a growing community of Data Professionals by subscribing to my 𝗡𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿: newsletter.swirlai.com
7
190
3
856
153,158