huganabaga

4 ms·

1.
by huganabaga 3y ago
> Why would you build something to throw away before it ships? That's because you learn things along the way. About underspecified requirements, about design choices that looked good on paper but ended up brittle, about tech that pr
2.
by huganabaga 3y ago
Of course they "cost". But the issue is the mindset that they are "extra". They are not. They are an integral part to professional software engineering. You can't take them away without moving from a professional cr
3.
by huganabaga 3y ago
Everybody has time to write an automated test. If you don't, then you don't have time to write code in the first place. That's the difference between professional software engineering and just hacking something quick in your
4.
by huganabaga 3y ago
My personal conclusion is to never work under management who are not software engineers themselves. All my bosses understand what building great software entails since they could do it themselves. So what I do to improve qualiry has always
5.
by huganabaga 3y ago
Those competitors will be known for crap quality and eventually their product beasts will be unmaintainable and hard to extend. So, while you keep steadily improving and extending they will eventually fold under their own unsustainable mess
6.
by huganabaga 3y ago
> ship awesome product and iterate as fast as possible And that attitude is why so much software just sucks. Spending some time to contemplate and test and find out what's good and throw away what's not before it ships, all tha
7.
by huganabaga 3y ago
But it saves heaps of work after. Far beyond 20%. (The projects I work on typically spend over 50% on automated tests, but I'm in an area of the software industry where we really can't have and bugs escape into the wild. I wish mo
8.
by huganabaga 3y ago
> Writing documentation is always a time sink, though, in my experience. Or maybe I'm just not good at it :P It's usually an additional day of work overall, though. And it saves you days and days of re-discovering truths about
9.
by huganabaga 3y ago
>invest in tooling which makes it "cheap" to do the right thing. However this is not easy to pull off. Automated testing FTW. Then you can change and refactor and extend all day, as long as the tests are all green, you are gold
10.
by huganabaga 3y ago
And that's a problem. Often there are full of issues which eventually are all known but never fixed. Updateability is the defining advantage of software over pure hardware solutions. If you don't use the advantage then you are s
11.
by huganabaga 3y ago
Putting "automated testing" into the last 1% is the issue right there. It needs to be part of what you are doing from the start. You are done when your automated tests are complete and reliably green, not when some underpaid teste
12.
by huganabaga 3y ago
The key here is the dishonesty in society. It annoys me every day. I hear 30-year old overpaid software engineers brainstorming how to cheat the ticket checks at the ski resort. I watch people at all-you-can-eat buffets piling more food on
13.
by huganabaga 3y ago
The ISBN could be the bank account. Like a DOI. Or a BTC wallet address. Access/control over it could be transferable.
14.
by huganabaga 3y ago
If a product is crap, don't buy it. Perhaps a real book on real paper is an alternative?
15.
by huganabaga 3y ago
> Why do you hate Jupyter notebooks so much that it reaches “worst thing to ever have happened“ status? It's the "with a passion" part. A certain sub-population is prone to deciding that they love or hate something, ba