So here are the ways you can join a developer community:
How to join a developer community?
or
How to find mentors/developer friends?
A detailed thread 🧵👇
So here are the ways you can join a developer community:
Many companies have their campus ambassadors/ Hack clubs / Developer club program that you can join or lead in your campus.
Some of my favorites:
⚡️Student Ambassador program @Microsoft (I am a part of this for 2 years now)
https://t.co/QidpryGvqq
More from Nirbhay Vashisht
(Java, Python, JavaScript, C, Go, C-plus plus etc)
A Thread🧵
Python 🐍
https://t.co/0vxUKsSAV0
C-Plus-Plus 👀➕➕
https://t.co/CEzjtEdiit
Java ☕️
https://t.co/GAvvcIdDBP
JavaScript ☕️📜
https://t.co/LD6bcVV2x6
C 👀
https://t.co/lvXGfsbK1X
Kotlin
https://t.co/nOwQeRrPF2
Ruby
Rust
https://t.co/iHNdFQ6NUU
C# 👀🔪
https://t.co/wYOihSDDqc
Go 🏃
https://t.co/NGLP4g33kd
Dart 🎯
https://t.co/c9qFFK9iBU
Scala
https://t.co/xTCWVpWDrR
PHP
F#
https://t.co/KBMWfdopZT
Jupyter
https://t.co/XZL5QtbCgu
R
https://t.co/I7NtwUPkc8
Haskell
https://t.co/6dDaC36tHB
Swift💨
https://t.co/1jK2gcXBke
Happy Coding 👩💻 👨💻🧑💻
Checkout my profile for more such tweets 😄
Here's a Detailed Roadmap for you 🧵👇
1. Start with https://t.co/LUATAaPiaW's - JavaScript Algorithms and Data Structures Certification and finish the "Basic JavaScript" module.
You'll get a basic understanding of JavaScript and Programming in general.
2. Move to https://t.co/ZDqK2dT8Iz and complete the following parts:
- An Introduction
- JavaScript Fundamentals
You'll start to understand Basic JavaScript concepts and their details.
3. Complete "Objects: the basics" section in https://t.co/ZDqK2dT8Iz
By this point you'll have a decent understanding of JavaScript Objects
4. Time to return to freeCodeCamp. Finish the following sections:
1. Debugging
2. Basic Data Structure
More from Software
Eng managers and directors, we have got to stop asking for "more headcount" and start treating this like the systems problem that it is. https://t.co/XJ0CkFdgiO
When people often have to spend weeks just to get a local development environment up, there is a lot to improve. \U0001f641
— Daniel Schildt (@autiomaa) December 20, 2020
If you are getting barely more than 50% productivity out of your very expensive engineers, I can pretty much guarantee you cannot hire your way out of this resourcing issue. 😐
(the stripe report is here:
Say you've got a strategic initiative that 3 engineers to build and support it. Well, they're going to be swimming in the same muddy pipeline as everyone else at ~50%, so you're actually gotta source, hire and train 6, er make that 7 (gonna need another manager too now)...
...which actually understates the problem, because each person you add also adds friction and overhead to the system. Communication, coordination all get harder and processes get more complex and elaborate, etc.
So we could hire 7 people, or we could patch up our sociotechnical system to lose say only 25% productivity to tech debt, instead of 42%? 🤔
By my calculations, that would reclaim 3 engineers worth of capacity given a team of just 17-18 people.
First, that time when an AWS employee posted confidential AWS customer information including including AWS access keys for those customer accounts to
Fresh data breach news-
— Chris Vickery (@VickerySec) January 23, 2020
Amazon AWS engineer exposes work-related keys, passwords, and documents marked "Amazon Confidential" via public Github repository: https://t.co/7gkIegnslx
Discovered within 30 minutes of exposure by my team at @UpGuard.
Discovery by @SpenGietz that you can disable CloudTrail without triggering GuardDuty by using cloudtrail:PutEventSelectors to filter all events.
"Disable" most #AWS #CloudTrail logging without triggering #GuardDuty:https://t.co/zVe4uSHog9
— Rhino Security Labs (@RhinoSecurity) April 23, 2020
Reported to AWS Security and it is not a bug.
Amazon launched their bug bounty, but specifically excluded AWS, which has no bug bounty.
Amazon Vulnerability Research Program - Doesn't include AWS D:https://t.co/stJHDG68pj#BugBounty #AWS
— Spencer Gietzen (@SpenGietz) April 22, 2020
Repeated, over and over again examples of AWS having no change control over their Managed IAM policies, including the mistaken release of CheesepuffsServiceRolePolicy, AWSServiceRoleForThorInternalDevPolicy, AWSCodeArtifactReadOnlyAccess.json, AmazonCirrusGammaRoleForInstaller.
You May Also Like
These setups I found from the following 4 accounts:
1. @Pathik_Trader
2. @sourabhsiso19
3. @ITRADE191
4. @DillikiBiili
Share for the benefit of everyone.
Here are the setups from @Pathik_Trader Sir first.
1. Open Drive (Intraday Setup explained)
#OpenDrive#intradaySetup
— Pathik (@Pathik_Trader) April 16, 2019
Sharing one high probability trending setup for intraday.
Few conditions needs to be met
1. Opening should be above/below previous day high/low for buy/sell setup.
2. Open=low (for buy)
Open=high (for sell)
(1/n)
Bactesting results of Open Drive
Already explained strategy of #opendrive
— Pathik (@Pathik_Trader) May 27, 2020
Backtested results in 30 stocks and nifty, banknifty.
Success ratio : approx 40-45%
RR average 1:2
Entry as per strategy
Stoploss = Open level
Exit 3:15 PM Or SL
39 months 14 months -ve, 25 +ve
Yearly all 4 years +ve performance. pic.twitter.com/nGqhzMKGVy
2. Two Price Action setups to get good long side trade for intraday.
1. PDC Acts as Support
2. PDH Acts as
So today we will discuss two more price action setups to get good long side trade for intraday.
— Pathik (@Pathik_Trader) June 20, 2020
1. PDC Acts as Support
2. PDH Acts as Support
Example of PDC/PDH Setup given
#nifty
— Pathik (@Pathik_Trader) June 23, 2020
This is how it created long setup by taking support at PDC.
hopefully shared setup on last weekend helped. pic.twitter.com/2mduSUpMn5