marcoow

6 ms·

1.
by marcoow 3mo ago
cheadergen is an open source tool that our Rust lead wrote – not sth. we sell or anything
2.
by marcoow 2y ago
It does require manual approval for any new or growing files atm but adding some kind of setting for a threshold (maybe per file type) for which Gravity auto-approves might be a good addition in the future
3.
Gravity CI(gravity.ci)
11 points by marcoow 2y ago|3 comments
4.
by marcoow 2y ago
Gravity monitors build artifact sizes to prevent accidental increases – right in your CI pipeline.
5.
Gerust: Project generator for Rust back end projects(gerust.rs)
2 points by marcoow 2y ago|0 comments
6.
The guide to making remote work work(simplabs.com)
6 points by marcoow 6y ago|2 comments
7.
by marcoow 6y ago
I share learning and experiences from running simplabs as a full remote company for many years: * remote work is about culture, not getting everyone on Slack * transparency among the team is critical if you don't want to alienate team
8.
The True Cost of a Quickfix(simplabs.com)
4 points by marcoow 6y ago|1 comments
9.
by marcoow 6y ago
Patsy Issa makes the case for refactoring legacy code sooner rather than later
10.
Writing Rust NIFs for Elixir with Rustler(simplabs.com)
7 points by marcoow 6y ago|1 comments
11.
by marcoow 6y ago
Niklas Long describes the upcoming changes to Rustler and how it simplifies implementing Rust NIFs for Elixir.
12.
by marcoow 6y ago
> On the other hand middle-management is always trying to push their peons to predict the future and accept the liability. That's bad just middle management then though. It's also why I'm advocating against project manager
13.
by marcoow 6y ago
ShapeUp is great! I don't think a cool-down phase is good though – if something is important to someone and it is indeed important for the business but still doesn't get planned in any iterations that means either a) it's not
14.
by marcoow 6y ago
Indeed we disagree. I’d say the reluctance that’s relatively wide spread in particularly among engineers to even try and reduce risk as much as possible (within a limited scope) and framing that as „predicting the future“ is a huge fallacy
15.
by marcoow 6y ago
Hey, I’m the author. I think you Mis-interprete what I’m saying - of course understanding timelines and budget will often be a legitimate need of one or some stakeholders, among others. And of course making teams stick to deadlines when tha
16.
by marcoow 6y ago
Bug bashes are a bit like cool down periods in my experience – if your focus is 100% on features all of the time then every now and then you need to catch up on open bugs or piled up tech debt. I'd argue these types of activities are n
17.
by marcoow 6y ago
Sure, you should have bugs documented somewhere but I'm not sure a bug that hasn't been fixed for x months needs to be there since it's a bug the team obviously decided not to care about.
18.
by marcoow 6y ago
Not maintaining a backlog doesn't necessarily mean you cannot collect ideas etc. anywhere. I think the two main points are: * putting effort into preparing proper tickets for all these ideas is likely wasted time as 90% of the ideas wi
19.
Failing (and winning) at planning software projects(simplabs.com)
33 points by marcoow 6y ago|23 comments
20.
by marcoow 6y ago
Planning and estimating projects (or sprints within projects) is associated with a lot of uncertainty and frustration on all sides. At the same time, teams feel they have to adopt processes like Scrum (or their own interpretation of it) and
21.
CodeBot – execute JavaScript from your Slack chat(codebot.chat)
2 points by marcoow 10y ago|0 comments