Codethink’s culture stems from the world of open source software. A large part of what it means to be a Codething is taking part in the sharing of knowledge across the company and learning on a daily basis. This practice drives the development of understanding in different areas of software, programming and allows staff to generally learn as a collective.
One way knowledge is shared around Codethink is through peer-led classes. Recently Daniel, a solutions architect at Codethink, has organised and led a series of classes for other Codethink engineers around Rust.
Rust is a relatively new programming language (Rust 1.0 was released in 2015) but one that is increasingly popular, achieving status as ‘most loved programming language’ in Stack Overflow’s developer survey each year since 2016. Rust boasts a very friendly, and growing community, reliably releasing regular updates, making it an attractive option for developers looking for a project to contribute to.
Rust has been turning heads as a modern alternative to some of the more traditional programming languages. As a memory-safe language, Rust is designed with security in mind -- it’s protection against memory corruption vulnerabilities has prompted security engineers to explore its applicability. Focus is increasingly placed on software security in the automotive industry and recent research has pointed at memory safety as a critical problem which needs addressing. This points to Rust as a potential solution and makes it a very relevant language for Codethink engineers, who work on automotive projects frequently.
Daniel’s Rust course was set up with the ultimate objective that attendees should become comfortable writing code in the language and for the whole group to agree that classes are no longer required. By setting the overall course objective with the group in mind instead of the individual, an environment of collaboration is fostered, where attendees are encouraged to help each other reach a common goal. This is a positive attitude to encourage and one that ultimately benefits a company in their day to day activities.
The schedule for the Rust course was set up with attendees’ work schedules in mind. Daniel delivers 1 hour of lecture style class each week which is recorded for future reference, and attendees agree to a matched amount of signposted, but self-directed, learning. Homework is also set for attendees in the form of programming problems, for which the lecture will be needed in addition to the self-directed learning. Although the course is set to be able to work around attendee schedules and company work comes first, a certain level of commitment to learning is required, which is made clear from the start.
The feedback of the course was positive, the engineers in Codethink share a passion for learning and improving in what they do and the opportunity to take part in Daniel’s Rust course proved popular. As a result of the high interest, the course will be run for a second time with another, larger group of engineers attending. Daniel enjoyed being able to teach other enthusiastic engineers about something he’s interested in and encourage discussion on the topic.
The sharing of knowledge in a company like Codethink is important and allows for technical competencies to develop at a faster rate than normal. This is because staff have more forums to connect on an intellectual level outside of project requirements. For a company where learning is an important part of day to day life, this format proved to be very successful.
For a company where learning is an important part of day to day life, this format proved to be very successful and allows us to grow our understanding in new technology areas. By doing this we become able to confidently engage with the challenges that those new technologies may bring.
- Using Git LFS and fast-import together
- Testing in a Box: Streamlining Embedded Systems Testing
- SDV Europe: What Codethink has planned
- How do Hardware Security Modules impact the automotive sector? The final blog in a three part discussion
- How do Hardware Security Modules impact the automotive sector? Part two of a three part discussion
- How do Hardware Security Modules impact the automotive sector? Part one of a three part discussion
- Automated Kernel Testing on RISC-V Hardware
- Automated end-to-end testing for Android Automotive on Hardware
- GUADEC 2023
- Embedded Open Source Summit 2023
- RISC-V: exploring a bug in stack unwinding
- Adding RISC-V Vector Cryptography Extension support to QEMU
- Introducing Our New Open-Source Tool: Quality Assurance Daemon
- Long Term Maintainability
- FOSDEM 2023
- Think before you Pip
- BuildStream 2.0 is here, just in time for the holidays!
- A Valuable & Comprehensive Firmware Code Review by Codethink
- GNOME OS & Atomic Upgrades on the PinePhone
- Flathub-Codethink Collaboration
- Codethink proudly sponsors GUADEC 2022
- Tracking Down an Obscure Reproducibility Bug in glibc
- Web app test automation with `cdt`
- FOSDEM Testing and Automation talk
- Protecting your project from dependency access problems
- Porting GNOME OS to Microchip's PolarFire Icicle Kit
- YAML Schemas: Validating Data without Writing Code
- Deterministic Construction Service
- Codethink becomes a Microchip Design Partner
- Hamsa: Using an NVIDIA Jetson Development Kit to create a fully open-source Robot Nano Hand
- Using STPA with software-intensive systems
- Codethink achieves ISO 26262 ASIL D Tool Certification
- RISC-V: running GNOME OS on SiFive hardware for the first time
- Automated Linux kernel testing
- Native compilation on Arm servers is so much faster now
- Higher quality of FOSS: How we are helping GNOME to improve their test pipeline
- RISC-V: A Small Hardware Project
- Why aligning with open source mainline is the way to go
- Build Meetup 2021: The BuildTeam Community Event
- A new approach to software safety
- Does the "Hypocrite Commits" incident prove that Linux is unsafe?
- ABI Stability in freedesktop-sdk
- Why your organisation needs to embrace working in the open-source ecosystem
- RISC-V User space access Oops
- Tracking Players at the Edge: An Overview
- What is Remote Asset API?
- Running a devroom at FOSDEM: Safety and Open Source
- Meet the codethings: Understanding BuildGrid and BuildBox with Beth White
- Streamlining Terraform configuration with Jsonnet
- Bloodlight: Designing a Heart Rate Sensor with STM32, LEDs and Photodiode
- Making the tech industry more inclusive for women
- Bloodlight Case Design: Lessons Learned
- Safety is a system property, not a software property
- RISC-V: Codethink's first research about the open instruction set
- Meet the Codethings: Safety-critical systems and the benefits of STPA with Shaun Mooney
- Why Project Managers are essential in an effective software consultancy
- FOSDEM 2021: Devroom for Safety and Open Source
- Meet the Codethings: Ben Dooks talks about Linux kernel and RISC-V
- Here we go 2021: 4 open source events for software engineers and project leaders
- Xmas Greetings from Codethink
- Call for Papers: FOSDEM 2021 Dev Room Safety and Open Source Software
- Building the abseil-hello Bazel project for a different architecture using a dynamically generated toolchain
- Advent of Code: programming puzzle challenges
- Full archive