hackforla / hackforla/engineering
Generate Questions for 2024-03-28: Elsy Pinzon (Android engineer at Microsoft)
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 42
- Forks
- 2
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Overview
We need to create a list of questions for our guest speaker [PERSON OR COMPANY] attending on [DATE].
### Action Items
- [ ] Send issue to Engineering Slack channel and ask Engineering members to write their questions in the comments.
- [ ] Send format of talk to guest
- [ ] Collate the questions into a list of unique questions (non-duplicated questions).
- [ ] Send ***Questions*** and ***Consent Form*** within 2 weeks of their talk.
- [ ] Update Wiki
### Resources/Instructions
Slack Announcement
:calendar: Mark your Calendars for Hack for LA’s Speaker Series - Thursday, 2024-03-28, at 6pm PT.
:mega: Elsy Pinzon (Android engineer at Microsoft) will be our visiting speaker for the Engineering Community of Practice.
:speech_balloon: Topic: Fireside chat about starting a career in Big Tech when you don’t come from a USA School.
:bust_in_silhouette: Elsy is a Software Engineer for mobile development and web applications who is about good practices, agile development, architecture, design patterns, algorithms and problem-solving. She fell in love with building mobile apps after getting her software engineering degree in Mexico City, and then she applied to Microsoft.
:star: Find out how her love of learning and new challenges helped grow and find a great team.
Thank you! Engineering CoP Co-Leads
- [WEBSITE FOR GUEST SPEAKER]
### Speaker Bio
[INSERT SPEARKER BIO]
Beitragsleitfaden
Rechercherichtung
Beginne mit den Action Items und der Slack Announcement in diesem Issue. Prüfe die Felder für Gast, Datum, Vortragsformat, Website und Sprecherbiografie und sieh anschließend die Kommentare nach eingereichten Fragen durch. Als abgeschlossen gilt die Aufgabe, wenn die Fragen zusammengetragen, die erforderlichen Materialien versendet und das Wiki aktualisiert wurden.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- android
- Bereich
- content, documentation
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 20/100