Comments by "MrAbrazildo" (@MrAbrazildo) on "ForrestKnight" channel.

  1. My way of doing things is 2h for tactical work (coding in computer), and 1h of strategic work, away from computer. Quality software is done by both of these things. 4:11, if "perfection" is taken as some previous broad plan (strategy), it rarely will be perfect. Tactic is needed to give feedback. The same way, nobody should just code, because a good plan can save us from getting obscure paths. 3:15, a meeting to schedule things is a complete idiotic idea. The reason is obvious: there's no deadline in software. However, meetings to configure/update ways of how a team should work, establishing standards, rules and overall strategies is something that should be done, even often. 3:47, don't schedule, schedule is mistake. I can prioritize things (despite not ideal for me), but I'll finish them when the time comes, period. No schedule, no deadline. 5:14, even not having distraction by phone nor other big noticeable things, often appears some small/tiny things, like thoughts of jokes, emotions, interesting ideas (not related to the work), memories of something you can't miss (and have an idea to enforce it right now), and so on. So, the right solution for this is timed work. And if I'm completely honest, stopping the timer whenever these things come along (or I go to the bathroom), my 2h becomes 3:30, in which 1h was spent for strategic approach (paused timer). 6:41, but I'm pitching it. 4h is ideal. And by that I mean 2h timed, with honesty. I hate 8h, I can't take this any longer! This lets me with plenty of energy for doing things free of charge, like a meeting (demanding useful ones), writing a report (mostly from the current day), discuss some ideas (strategy in an amplified view). Of course, not as an obligation, but there's a tolerance and a good sense for these extras.
    1
  2. Dump C++ for memory safety is retarded, nowadays. Its tools catch all errors Rust does, without the compilation overhead. 3:20, that's the very reason why the language should not lose terrain. It gives us more freedom on how to do things. The #1 feature, above speed. 3:24, and at the same time have a high level language, with just a bit of effort. 4:38, Go is twice slower, and Rust seems to bring some stupid ideas, like not having classes nor inheritance (composition only). Is it right? 5:30, hm. I guess we should rewrite all Rust and Go in C++. 5:41, this is not enough. C++ doesn't deserve to be the new COBOL (alive due to its large codebases only). C++ is objectively better! 5:53, but Java being replaced by Rust... that's a good idea!
    1