News && events related to Toronto's JavaScript community. Join us on Slack: tinyurl.com/JoinTJS / Give a talk or workshop: tinyurl.com/TorontoJS

Toronto, ON
Coming soon: JS Tech Talk at @vmwaretanzulabs with support from @DevCycleHQ Thurs Sep 28 after work to be exact feature talks by Shruti Vellanki, Nik LeBlanc, Rob Jackiewicz guild.host/events/js-tech-ta…
1
3
5
412
Toronto JavaScript retweeted
I think one of the most under utilized resources that Jr's / aspiring web developers miss out on is pair programming sessions. Here's three communities that are tried and true: @torontojs Memphis Tech & Users Group @LawrenceDCodes for more info Learn, Teach, Build @jamesqquick These are well respected communities with well respected leadership teams. Every single one has virtual events that welcome everyone from all skill levels. Honestly, I think everyone should join community events every now and then, no matter where they are in their career. Strong communities are the bed rock of society!
1
1
9
403
I'm back 😁
4
1
20
708
Toronto JavaScript retweeted
What are DORA Metrics and how does DevCycle use them? Find out later this month as our VP Engineering @nikolasleblanc takes the stage @torontojs with "DORA at DevCycle: Tracking engineering metrics that matter" @vmwaretanzulabs 📈 Get your ticket at guild.host/events/js-tech-ta… 🎟️
2
4
186
Toronto JavaScript retweeted
legendary PR blockers
26
570
4,145
293,854
Toronto JavaScript retweeted
Replying to @saronyitbarek
@ania_kubow for JavaScript / databases @FreyaHolmer for explanations of the math behind code @kulkarniankita9 helps software engineers level up @/mattaniah for her creative coding shorts (I discovered her on TikTok and find her work very inspiring) youtube.com/@mattaniah?si=iH…
2
4
13
1,220
Friends on macOS, what VPN app are you using / do you recommend?
115
5
56
57,424
TorontoJS is a not-for-profit corporation with a mandate to support all in their learning and passion for sharing knowledge on JavaScript and software development in Toronto and GTA. If you would like to support us check out opencollective.com/torontojs
1
2
487
TorontoJS is starting a newsletter! In this email we'll occasionally: * 📆 TorontoJS events that are on the docket. * 🌟 Highlight projects from people in the community! * 🥕 Deliver Javascript news & facts. * 🏢 Share relevant job postings! Subscribe lnkd.in/d_CcyRD7 .
2
3
500
Toronto JavaScript retweeted
With the right prompt, ChatGPT (with gpt-4) is the best and easiest nutrition tracker I've ever used. I just message it the foods each time I eat (I keep a running chat for this) and it tells me the breakdown and keeps totals for the day. At the start of the next day I say "reset" and it does. If I'm considering eating something and want to know the nutritional analysis but don't want it added to the totals I add the word "maybe". Here's the prompt that sets this up: ---- I will list foods. Provide a nutrient analysis including calories for each food. Add the food to a list of food eaten for today and add the values to a running total for the day, unless I say “maybe”. If I say “maybe” then do not add that food to the list for today and do not add the values to the totals. Each time you respond provide the totals for today, numbers only, on one line separated by `|` in the following order: Date, Carbs, Protein, Fat, Fiber, Calories (using the current date). If I say “reset” then clear the list, set the totals to 0, and increment the date. ---- (You can customize it as you like, e.g. remove that last thing about totals separated by `|`). And some power features: you can describe some common meals that you eat with nicknames so that you can say something like "breakfast 1" and it will know what the ingredients are. If you make a mistake or want to change something just tell it what to change, e.g. "correction: that was 3 oz cheese, not 3 lb", or give it general things like "all milk is 2% milk".
1
2
13
1,292
Toronto JavaScript retweeted
women supporting women is not paid membership, is lifting each other up with available resources. #WomenInTech #WomenEmpowerment #WomenTechmakers #WomenWhoCode #DEVCommunity
1
2
234
🚨 Just 1 day left! 🚨 Don't miss out on the #TorontoJS Online Social happening tomorrow, August 30th: Friends + Code = LOVE! 🤝👩‍💻 Get ready to connect with fellow devs, chat JavaScript, and enjoy a laid-back evening of networking. See you there! 🌐🎉 bit.ly/js-social-online
1
708
Toronto JavaScript retweeted
Software estimates are one of the oldest lies we tell ourselves. We all know they don't work, but pretend they mean something and later feel enraged when shit hits the fan. I focused a big part of my undergrad on software estimation. After graduating, I wrote plenty about the topic. Then, I started working for a company where I spent years researching how to make better estimates. We sold multiple millions of dollars of software using the tools I built. I read everything there's to read. I could recite Steve McConnel's "Software Estimation" book from top to bottom. Here is the most important lesson I learned: People can't estimate software. It doesn't matter who they are or how much experience they have. Estimating software reliably is science fiction. And the best part: They will ask you to estimate something. They will tell you they understand it's not exact. They will promise they won't hold you accountable. And then they will. They always do. There are two solutions for this. Let's start with my recommendations for those who don't have a choice: 1. Remove "quick," "simple," "straightforward," "easy," and every similar word from your dictionary. Never use them. Don't let others use them when referring to your work. 2. Never volunteer an estimate. Everything you say will be used against you. 3. When forced, estimate work you know you can complete today. Always estimate with a range: "It will take me 2 - 4 hours." 4. Estimate anything you won't do today in days and weeks. Say, "I should finish that feature sometime this week." Do not estimate future work in hours. But we all know your manager will force you to give an estimate. Here is what you should do: 1. Estimate how long you think it will take you to complete the task. 2. Multiply the number by 3. This will be the lower range of your estimate. 3. Double the lower range of the estimate. This will be the upper range. Example: If you think something will take you 1 day of work, say "between 3 and 6 days." Here is the funny part: It won't take you between 3 - 6 days. This is as much bullshit as any other method you can think of. The true solution for this problem: Work for a company that doesn't care about estimates.
503
1,622
10,071
1,948,257
DCA airport has decent Wi-Fi "ip": "205.153.95.155", "hostname": "205.153.95.155.ipyx-135073-z…", "city": "Arlington", "region": "Virginia", "country": "US", "loc": "38.8810,-77.1043", "org": "AS23003 Metropolitan Washington Airports Authority", "postal": "22210",
1
2
774
Toronto JavaScript retweeted
Starting a video series today on @expo and Internet of Things 🎉! This video focuses on connecting @arduino to the internet. The next 2 videos will show how to set up @expo Push notifications for real time updates! Excited to advance the RN meta further💪 youtube.com/watch?v=LEeJZCOS…
6
12
76
7,898
tremendous reflections from within the direction of a community of many beating hearts and passions
3
261
Toronto JavaScript retweeted
One of the most common mistakes I see developers make is not asking for what they want. Your literally double your chances to get that thing when you ask For example, negotiate raises, ask to be on a specific project, share your goals, ask questions that are outside your scope but are important, ask if you need time off, ask for help and lots more.
4
4
697
Toronto JavaScript retweeted
1
2
206