ferroman

4 ms·

1.
by ferroman 1mo ago
There are a lot of OSS stuff out there
2.
by ferroman 1mo ago
Clean Code wasn't trying to solve performance issues. It tries to solve issue with expensive code maintenance.
3.
by ferroman 1mo ago
because you are not buying software. You buying rent
4.
by ferroman 1mo ago
They proposed terms. You agreed. They act on them.
5.
by ferroman 1mo ago
not all products
6.
by ferroman 6mo ago
trust is very VERY expensive commodity
7.
by ferroman 6mo ago
easy way will always win
8.
by ferroman 7mo ago
"occurs when someone misrepresents, exaggerates, or fabricates an opponent's argument to make it easier to attack." You literally imagine something that isn't in this text and start theroritizing based on this.
9.
by ferroman 7mo ago
It's called "strawman fallacy", you replacing the thesis and add things that wasn't there to draw plausible conclusions instead of trying to get more information if there's not enough. Calling it "hypothesis&
10.
by ferroman 7mo ago
Using prompt as source of truth is not reliable, because outputs for the same prompt may vary
11.
by ferroman 7mo ago
> Figuring out how to get others to see what you see but this is exactly the point of article: event if you make them see, they just pretend they don't because it's not in their personal immediate interest to admit you are rig
12.
by ferroman 7mo ago
clinical psychologist's like to invent imaginary scenarios and add something that is not in text, aren't they?
13.
by ferroman 7mo ago
This is exactly my experience (and I've been doing this fo 20 years now). Saw it on every job I had. The usual bs is "we are developing new performance and grows framework" "promotions will happen on next cycle" &
14.
by ferroman 10mo ago
well, that whole post convinced me to not even try any of this lol. gl with community tho.
15.
Technical Documentation: My Personal Framework for a Better Guide(medium.com)
3 points by ferroman 3y ago|1 comments
16.
by ferroman 3y ago
I’m working on putting together a sort of personal framework for writing technical docs for software projects. This is stuff I'm really struggling with, so any tips are welcome.
17.
Minimalistic but useful project documentation(savvyclutch.com)
1 points by ferroman 9y ago|0 comments
18.
by ferroman 9y ago
That's cool
19.
The obvious plan how to manage technical debt(savvyclutch.com)
1 points by ferroman 9y ago|0 comments
20.
by ferroman 9y ago
You can generalize it, but that was a point to make the list more specific. And yes, world is a very different place today. The number of SW engineers doubles every year, so, at least half for them are new. We are engineers and we should
21.
by ferroman 9y ago
Teams, of course. The goal was to measure it, and we tried to be more specific.
22.
by ferroman 9y ago
It is relevant, but we try to make it more specific.
23.
by ferroman 9y ago
Unfortunately, it's much more complex than that. Does your software work? Does your software work right ? How quick you can add this to it? How to avoid bugs when you introduce complex change? How to share knowledge with new people
24.
by ferroman 9y ago
What do you mean? Is it's too low or too high?
25.
by ferroman 9y ago
Because it allow to keep the domain logic somewhere. In these days people don't do documentation, or documentation is always outdated. Having high-level tests in DSL will do more than just tests - it give you information how your appli
26.
by ferroman 9y ago
Domain-specific language of course. I prefer Gherkin.
27.
by ferroman 9y ago
Thanks for feedback. We decide that more detailed test - more precise measure, but we still try to keep the list as short as possible.
28.
by ferroman 9y ago
True, but not much team follow these, in practice. We just want to make it more specific and modern.
29.
Measuring software engineering competency(savvyclutch.com)
129 points by ferroman 9y ago|95 comments
30.
Allow to Send HTTP/2 Requests to APNS on CentOS6 and Python3.5(savvyclutch.com)
1 points by ferroman 10y ago|0 comments

More ›