About
• Core Engineering: Go (primary), ~Python, distributed systems, APIs, Kubernetes / Cloud…
Articles by Carlisia P.
-
2025 Starts with (a New?) You
2025 Starts with (a New?) You
Hey, you! STOP listening to your Spotify Wrapped 2024 now! Why? Because if you keep playing your 2024 playlist, can you…
8 Comments -
Go: The Language, the Purpose, the Ecosystem, and the Community
Go: The Language, the Purpose, the Ecosystem, and the Community
-
Golang UK Conf. 2016 - Carlisia Campos - GoBridge and the Go Community / Initiatives & Opportunities
Golang UK Conf. 2016 - Carlisia Campos - GoBridge and the Go Community / Initiatives & Opportunities
Activity
-
Solomon Hykes and I at OpenStack Summit in 2013, shortly after Docker was released, where he was showing me how we could use Docker to solve our…
Solomon Hykes and I at OpenStack Summit in 2013, shortly after Docker was released, where he was showing me how we could use Docker to solve our…
Liked by Carlisia P. Campos
-
Testing concurrent code without the hacks, flakes, or long waits? Sign us up! 💥 Join Alexander Baygeldin at #GopherCon as he explores how the new…
Testing concurrent code without the hacks, flakes, or long waits? Sign us up! 💥 Join Alexander Baygeldin at #GopherCon as he explores how the new…
Liked by Carlisia P. Campos
Experience
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Education
-
Boston University
-
-
Research on Web Services Orchestration;
J2EE Application Sample (run on JBoss) with an Online Tutorial for BU Students. -
-
-
Volunteer Experience
-
Founding Member
GoBridge
- 4 years 8 months
Science and Technology
GoBridge is an open-source venture, part of the non-profit Bridge Foundry *Bridges program. Our core mission is to enable individuals to use Go as a tool for teaching and learning programming, regardless of gender, race, sexual orientation, ability, class, age and geographical location. All of our material is open source, and we encourage reuse!
If you are a company or individual interested in kicking off a GoBridge workshop: https://github.com/gobridge/workshops
I am no longer…GoBridge is an open-source venture, part of the non-profit Bridge Foundry *Bridges program. Our core mission is to enable individuals to use Go as a tool for teaching and learning programming, regardless of gender, race, sexual orientation, ability, class, age and geographical location. All of our material is open source, and we encourage reuse!
If you are a company or individual interested in kicking off a GoBridge workshop: https://github.com/gobridge/workshops
I am no longer active but would be glad to make connections if you are interested in participating.
Other similar profiles
Explore more posts
-
Paul Chiusano
I thought this was a good and very reasonable talk by Eleanor Millman on how to prioritize projects for a platform engineering team: https://lnkd.in/gaYtUHRH A few insights I took from it: - Unlike product features which can be more directly tied to revenue, platform engineering work is a couple steps removed. But that doesn't mean it's unimportant! Far from it, platform engineering projects can make everyone at the company more efficient, able to produce higher quality software, etc. - While "urgency" is always going to be a factor, you don't want to just be putting out fires, you want be able to prioritize work which is "high impact" ... even if that impact isn't felt immediately. - Good rule of thumb: prioritize "highest impact for lowest effort". - The talk has some ideas on what factors to choose for impact, and how to blend them. For instance "speed of development" is one factor, "cloud cost optimization" might be another. The weighting of different impact factors can change over time, depending on the needs of the business. I would say that a lot of companies don't have much methodology here but I can really see the value in codifying it. You can always change the methodology or the weighting if it's spitting out results that don't pass the smell test or you really feel it is leading the company astray. Clarity can give the org more freedom to put resources behind projects that would otherwise never be taken on. When things are unclear, prioritization still happens implicitly, but the decisions tend to be a lot more random and fear-based and the org is worse off as a result.
3 Comments -
Richard Greene
Our R&D team recently ran into a performance bottleneck in one of the hot paths of the product. After exhausting trivial optimizations in the C# code, the problem came down to the regex engine performance. So they leveraged Rust's regex engine from C# via FFI. What started as an experiment turned into a meaningful win. Using Cursor to generate the C# bindings for Rust made it surprisingly easy to build, benchmark, and iterate quickly — and in some cases, the result was ~6× faster than the original approach. If you’re curious about mixing C# with other runtimes, using FFI in real systems, or just enjoy performance deep dives in production code, this one’s worth a read. Full write-up by Dan Flomin on the Island Engineering Blog ↓
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content