We talk a fair amount on this blog about how to have better meetings. And we should! Taking the time for some meetings will save time over all… but it’s a delicate matter and one of great responsibility. But let’s say you feel like you get it. You’re the person charged with meetings going well, and you know which agile ceremonies are worth having regularly, how to determine other things worth discussing synchronously, and how to create and stick to an agenda. But you get it, and you’re hungry for more.
At Truss we believe that effective collaboration is a cornerstone of any successful team. Earlier this week I wrote about the research I did into effective collaboration. I’ve also developed a framework for thinking about collaboration which I shared as part of my workshop on collaboration on April 13th, 2018 at ACT-W (Advancing the Careers of Technical Women).
No matter how dedicated and efficient your team is, a few bad meetings can derail their productivity and their morale. In this final part of our three-part series about maximizing the value of meetings, we talk about one of the aspects of a good meeting: the facilitator
While a meeting can be a productive way to drive a project forward, many meetings are the opposite—they disrupt productivity and waste valuable time. To ensure that a necessary meeting doesn’t go off the rails is a bit of planning and someone to facilitate the process.
We’ve all been in bad meetings. And no matter how great your crew is, bad meetings waste time and can degrade the culture you’ve worked hard to build. We’ve talked before about which meetings are worth having, now it’s time to dive into how to get the most out of those meetings.
Our engineering architect Nick Twyman led the assembled team in a session to brainstorm issues which might be severe enough to tank the project. He opened with the prompt, “Imagine you’re presenting to the entire company 12 months from now and must explain why this project completely failed.”
What can containers bring to your testing? We look at CircleCI's readymade, language-specific containers and how you can use them for faster, more reliable testing and deploys.
In part two of three of Jen Leech's series on Project Management with <Build> by Femgineer, Jen and host Poornima Vijayashanker dive deeper into managing a successful project. This episode looks at navigating new ideas and unanticipated challenges
In the first part of a three-part series, Jen Leech joins <Build> by Femgineer. In this episode, Jen and host Poornima Vijayashanker dig into some valuable strategies that will address and alleviate your anxieties around managing your first high-stakes software project
Software updates can protect you against malware and hacking - threats that secure passwords alone cannot defend against. We’ll describe some of these threats and then tell you how to protect yourself from them by enabling auto-updates whenever possible and being consistent in manually installing updates when it’s not.
Complex passwords and memorable passwords seem to be at odds with each other. In this post, Truss engineers explain how to use more secure passwords and protect yourself from future breaches that may include your online credentials.
A good retrospective is the most important regular meeting a team should have. When done well, the retrospective provides a clear way for a team to make incremental improvements over time. There are a lot of different types of retrospectives, so it can be hard to know where to start.
On December 13, Truss engineer Breanne Boland delivered her talk "Man, 'splained: 40-Plus Years of Man Page History" at Systems We Love, a new conference that we really hope to see happen again next year.
Below is the video of her talk - plus another 8.5 hours of great material.
A man page is the most common form of Unix and Linux documentation. Despite the name, they’re not exactly what modern engineers expect from more typical product documentation - and they’re also definitely not tutorials. However, with their own particular format, they’ve become a vital part of regular learning and work for most developers, perhaps the most common “M” in the admonishment to RTM. With something so omnipresent, it’s easy to take it for granted - there’s a utility, so the utility has a man page. Of course.
But the history of man pages is tied inextricably to the history of Unix (in fact, they share a birthday) and is threaded through a certain formative era of computer science. Man pages go back to Bell Labs, back to Jerry Saltzer’s doctoral thesis proposal in 1964, back to decisions that were made without the intention of determining the way certain areas of programming would work for decades. And maybe that’s the biggest lesson of this whole story: never treat a solution as a stopgap or a prototype (particularly if you’re working in Bell Labs in the late 60s or early 70s). Your “This’ll do for today” could become the standard for the generations to follow.
Whether you’re interested in becoming a mentor, have been mentoring for years, or are curious about teaching practices in the context of software development, Truss engineer Andrea Mitchell discusses five pieces of advice that should give you a general idea of what to aim for and expect from the mentor-mentee relationship.
Just two years ago I made the decision to change the course of my career and attend Ironhack Bootcamp to become a software engineer. After four years of working in the tech industry as a QA Engineer, becoming a coder felt like an inevitability. I was ready for the challenge, and fortunate that my experience provided me with an arsenal of skills that would help me succeed at bootcamp.
Many of my colleagues were not so lucky. Despite the hours they had already spent studying, the majority seemed technically underprepared for the coursework. Many were lacking basic computer skills and as a result, struggled to keep up with the intense pace of the class. I ended up spending a significant portion of my time teaching and coaching other students, and it got me thinking about what our program could have done differently to better prepare incoming students. What skills can students learn at home with relative ease so that, during their program, they can focus on developing the skills where bootcamps provide the most value?
Truss’s CEO discusses his recent TechCrunch post and how to position your company’s practices and your network for real strides toward diversity.
Many tutorials attempt to address PATH in a sentence or less, if at all. And, worse, other tutorials (or attempts at them) assume more initial knowledge than a lot of novices have, flinging out disconnected jargon in a well-intended flurry that can push even true believers away from learning this small, vital skill.
Today, we fix that. Join us.
We put together a 2 minute video showing how to use Leave Now with your everyday calendar to help you arrive to your meetings on time. In addition, you'll see a preview of some of time-saving features in our upcoming release.