mbrodersen

8 ms·

1.
by mbrodersen 4y ago
Excel is brilliant.
2.
by mbrodersen 4y ago
In my view there is no such thing as “tech debt”. The way I look at it, there will always be a delta between the code you have and the business features you want/need. Independently of whether the code was written 30 years ago or yes
3.
by mbrodersen 4y ago
“was previously fired from her job for sleeping in her car behind her place of employment.” The cruelty of managers never stops surprising me. As long as she is doing her job and is presentable etc. what’s the problem? Worst case just ask h
4.
by mbrodersen 4y ago
Agree. I was offered a green card and a 6 digit salary to move to the US. I declined and instead moved to Australia. One of my best decisions ever.
5.
by mbrodersen 4y ago
In my experience there is a strong correlation between your ability to communicate clearly and your ability to write clean maintainable code. The 10x developers I have worked with are all excellent communicators. The worst developers I have
6.
by mbrodersen 4y ago
Aussie here. Speak for yourself mate. The tech I am working on in Melbourne (Rostering/Pairing) is world class. We are routinely beating international companies 100x our size.
7.
by mbrodersen 4y ago
I work for a company where meetings are extremely rare. We only do formal meetings when everything else fails. It is one of the most efficient/productive companies I have ever worked for. The least efficient/productive compa
8.
by mbrodersen 4y ago
I have such fond memories of the ZX-Spectrum. I learned how to program machine code using it (hand translates from Z80 assembler) when I was 11 years old. No internet. Nobody I could ask for help. Just a book explaining how to do machine co
9.
by mbrodersen 4y ago
There is nothing magical about 40 hours. It just happens to be the number of hours that most companies (in the west) happens to choose for historical reasons: https://www.okta.com/au/identity-101/40-hour-work-week&
10.
by mbrodersen 4y ago
Perhaps start with fixing the planet we are currently living on?
11.
by mbrodersen 4y ago
Not my experience at all. I have worked for two really fucked up companies. But the rest were OK and my current job is pretty good.
12.
Professor Steve Keen explains why austerity economics is naive(youtube.com)
3 points by mbrodersen 4y ago|0 comments
13.
by mbrodersen 4y ago
Not my experience at all. We have zero problems maintaining large 20+ year monoliths written in C++. It’s all about how you architecture the monoliths and how you refactor as needed to improve it.
14.
by mbrodersen 4y ago
I wouldn’t be surprised if it is true. The larger the organisation, the harder it is to deploy well designed software architectures. Too many cooks!
15.
by mbrodersen 4y ago
> But when you say garbage like "100% nonsense" it's just fucking rude and against the rules here at HN. Don't say it again. Speak respectfully or don't speak at all. I found that commment to be seriously rude an
16.
by mbrodersen 4y ago
Years ago I found the perfect tool for managing anything from small personal projects to large complex software development teams: A prioritised to-do list. It’s simple. It works.
17.
by mbrodersen 4y ago
It is my experience as a developer that the shorter the feedback loop is, the more productive I am. Fast auto tests are really useful for this. Being able to test against an in-memory DB instead of a much slower “real” DB is another examp
18.
by mbrodersen 4y ago
A colleague of mine is working on one of the worst software systems I have ever seen or heard of. It is a 20+ years old micro-services architecture. More than 50 services all interacting with each other in mysterious time dependent ways. It
19.
by mbrodersen 4y ago
It’s a drop in the ocean. There are millions of programming jobs out there.
20.
by mbrodersen 4y ago
There are millions of programmers and programming jobs out there. More than 5 million C++ programmers alone. And then there are Java jobs, C# jobs etc. So the head line job cuts are a drop in the ocean.
21.
by mbrodersen 4y ago
Not my experience at all. The quality and experience of the team is IMHO the best predictor of code quality.
22.
by mbrodersen 4y ago
Declarative: Specify the result you want. Imperative: Specify (step by step) how to get the result you want. Examples: Declarative: I want a PC with the following code installed: X, Y and Z. Imperative: First upgrade X, then install Y, then
23.
by mbrodersen 4y ago
Years ago at university I wrote a small 2D circuit board drawing system in Fortran running on some old IBM mainframe computer. Only the first 6 characters of function names mattered so I ended up using the first 2 characters as the module&#
24.
by mbrodersen 4y ago
There is a lot of software out there written in C. All of which needs maintenance. At work new C code gets checked in every day for software that runs major companies around the world. Having said that, I would never recommend C as the la
25.
by mbrodersen 4y ago
For people who hate going to the gym but want to get stronger/healthier I recommend the book “Body by Science”. I have more than doubled my body strength following it. And only spending 15 min a week in the gym (!)
26.
by mbrodersen 4y ago
I highly recommend writing your own Lisp from scratch. It is a fun project! I have done it more than once and in different languages.
27.
by mbrodersen 4y ago
Yep that must be a new record :)
28.
by mbrodersen 4y ago
Agda is a really interesting language. A great way to learn the power of Dependent Types.
29.
by mbrodersen 4y ago
Every additional hour you work without getting paid is effectively reducing your hour rate. So the harder you work the less you get paid per hour. Sorry but that’s not very smart. If the company doesn’t want to pay you for the extra hours t
30.
by mbrodersen 4y ago
Take it as an opportunity to learn new skills and work on your own projects.

More ›