text stringlengths 0 1.82k |
|---|
• Learning from hands-on experience with oscilloscopes and other tools |
• Balancing software and hardware interests as a maker or hobbyist |
• Value of simulation in learning about electronics and computer architecture |
• Discussion of the NAND To Tetris book and course on Coursera |
• Feedback gathering on tooling and bigger picture problems |
• Importance of considering the needs of newcomers vs. existing users |
• Identifying areas where historical conventions may be a barrier for those without a Go background |
• Exploring ways to make learning Go easier for beginners |
• Potential improvements in language features, tutorials, and documentation for newcomers |
• Using user studies to gather feedback from people with no prior knowledge or experience with Go |
• Difficulty in finding resources for newcomers to learn Go |
• Need for a more comprehensive and structured onboarding experience |
• Issues with toolchain, including cryptic error messages and difficulty installing dependencies |
• Lack of canonical tutorials and guidelines for using the Go ecosystem |
• Proposal for a website or resource that provides a clear path from beginner to advanced developer |
• Discussion of Rust's book as an example of a comprehensive guide to an ecosystem |
• Need for better communication and feedback mechanisms within the community |
• Discussion of the Go language community's growth and scaling challenges |
• Proposal for establishing workgroups or focus groups to facilitate collective discussion and decision-making |
• Recognition that current communication channels (e.g., issue tracker, proposal process) are insufficient for brainstorming ideas and gathering feedback |
• Importance of creating a lightweight medium for idea generation and discussion |
• Consideration of making Go Team approachable and receptive to community input |
• Proposals for cloud-related workgroups that are provider-agnostic |
• Discussion of how Kubernetes' special interest groups operate and potential application to the Go language community |
• Linode's cloud infrastructure options and pricing |
• Importance of communication in scaling the Go language community |
• Benefits of special interest groups (workgroups) for improving communication between the core team, community members, and contributors |
• Potential topics for workgroups, including documentation, outreach, and Kubernetes-focused groups |
• Chaos Monkey project by Netflix and its transition from Java to Go |
• Pumba: a chaos testing tool for Docker that simulates network conditions |
• Chaos testing in production as discussed by Erik St. Martin and Carlisia Thompson |
• New release of Go (1.7.3) with minor bug fixes |
• Community efforts to revitalize local Go meetups in Chicago and Minneapolis |
• Shoutouts to open source projects, including the Kubernetes special interest groups and the Gopher Slack bot |
• Erik St. Martin crashed during the show due to saying "power user" |
• Jaana Dogan talks about co-op implementations in Go and her work on IoT-related protocols |
• Jaana Dogan mentions her private repositories with hardware interoperability code for Go |
• Discussion of community growth and meta work groups, with potential issues arising from rapid growth |
• Proposal for live streaming sessions to facilitate brainstorming and interaction among developers |
**Erik St. Martin:** It's episode \#22 of GoTime. Today's episode is sponsored by Linode and Code School. Today on the show we have myself, Erik St. Martin, we have Carlisia Campos - say hello, Carlisia. |
**Carlisia Thompson:** Hi, everybody. |
**Erik St. Martin:** She's still laughing from everything that happened before the show, I can hear it. |
**Carlisia Thompson:** I'm trying to hold it back. |
**Erik St. Martin:** Brian Ketelsen was not able to make it, but today standing in for him we have Cory LaNou. Say hello, Cory. |
**Cory LaNou:** Hey, everybody! |
**Erik St. Martin:** And our special guest today is a core contributor to Go and probably familiar to just about everybody. I'll go ahead and let her give her own introduction. JBD. |
**Jaana Dogan:** Hello. I work on Go. I actually have been contributing to the project for the past years, and I've just started to contribute as a part of my full-time job. My role in the team is pretty unique. I wouldn't say that I am contributing code to the project at this point; the team wants me to be a user, a p... |
I'm kind of like a typical Gopher, but live in maybe one release cycle in the future, and exposed to tip, development going on on the tip and what is coming up next. My responsibility is particularly giving feedback about the usability API design, where things require more thinking from the user's perspective. I've rec... |
**Erik St. Martin:** So what types of applications are you developing? Because it seems like you do a lot of stuff in hardware, audio and mobile... Is this kind of tackling each of these areas and just trying to build applications and see what you run up against? |
**Jaana Dogan:** Yes. I was originally working for Google Cloud, and somehow bootstrapped all the cloud libraries, some sort of like good API design and idiomatic libraries, and everything around cloud products and how we can actually interact with the ecosystem so much better. I kind of like moved to another role to w... |
\[03:43\] As a continuation of that work, last year I was working with the Android team. Android is going through some sort of reorganization when it comes to building some tools and some more structure to build custom Android kernels. The team also wanted to expose GPIO and other peripheral communication interfaces fr... |
**Erik St. Martin:** So this is sort of like people who are using ODROID or Xen BeagleBoard Blacks and things like that, that even can get Android on? |
**Jaana Dogan:** Yeah. This is just Linux boards. This has been such a historically much requested feature, to be able to extend Android with board-specific hardware abstraction. What was historically requested was a more extendable hardware abstraction layer, so you can contribute more board-specific things and extend... |
**Erik St. Martin:** Awesome. Brian's been playing a little bit with writing Go on a Raspberry Pi for his smoker. |
**Jaana Dogan:** Oh, nice. That's awesome. |
**Erik St. Martin:** That's just too much fun. Smoking dinner with Go. |
**Jaana Dogan:** \[laughs\] |
**Erik St. Martin:** I just love creativity with that, and we've seen a bunch of that stuff, too. You're constantly showing stuff off on Twitter. |
**Jaana Dogan:** Yeah, there are billions of projects. I have billions of projects; I personally like physical buttons a lot, so I just realized that my entire world is surrounded by software and touch screens and things; that's why I was just replacing things with hardwired physical buttons that I feel more comfortabl... |
Due to the relationship with the Brillo Project, the Android project is called Brillo Project. Android focusing on the embedded aspects - it's called Brillo. We're getting so much stuff from China every month... We had this huge repository of devices around and sensors and all sorts of displays. It was really fun times... |
**Erik St. Martin:** It occurred to me one day, because I was looking at the piles of stuff I have here... Because I have a similar thing - when I'm tinkering with electronics, why am I gonna buy one chip from SparkFun or Adafruit when I can just buy like a hundred of them for a similar price from China? And then all t... |
**Jaana Dogan:** \[laughs\] We created a couple best combination of things, because I was working on a developer-facing product and we were also trying to come up with a set we can propose as a de-facto combination of those little devices, so the users can run the tutorials with them. And yeah, we've been thinking too ... |
**Erik St. Martin:** So Cory and Carlisia, do either of you have experience tinkering with the hardware side of things or embedded? |
**Carlisia Thompson:** \[07:52\] I did at the Gopher Gala last year. Nathan had a project and I joined to help him a little bit, with also somebody else here from San Diego Ravi. So I got to play with a Raspberry Pi, and we put in code that actually made the Raspberry Pi use a motion sensor, and that was very cool. |
I sort of have an irrational aversion to hardware, because my impression is that hardware doesn't work when I touch them. \[laughs\] I don't know, it's completely irrational. So I try to stay away from hardware in general, although it's pretty cool. |
**Erik St. Martin:** You give off like a static charge that just messes up all electronics? |
**Carlisia Thompson:** Yes, but it's like... It's supposed to have a button and I don't find a button, and these ridiculous things... But at any rate, I thought the Raspberry Pi is small and I could handle it, so I really fell in love with it. But I didn't play much with it after that. |
**Erik St. Martin:** One of the things that I think I loved the most was learning how simple serial protocols are. Then what you do is you buy yourself a logic analyzer and then you start finding random pieces of electronics and trying to find the chips and what their serial ports are, and then start geeking in on what... |
**Jaana Dogan:** Are you doing any serious debugging that way, or is it just how you investigate what is going on...? |
**Erik St. Martin:** It's more from just like a reverse-engineering standpoint, like "How does this work?" I've tried a couple of times to send my own commands and stuff on regular boards, but that's usually where it gets not so simple, because ordering comes into play. Reverse engineering any sort of protocol is hard ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.