Henrik Rasmussen (@nomtrosk) profile picture
Copenhagen, Denmark
Joined August 2015
Photo by Henrik Rasmussen (@nomtrosk)Photo by Henrik Rasmussen (@nomtrosk)Photo by Henrik Rasmussen (@nomtrosk)Photo by Henrik Rasmussen (@nomtrosk)Photo by Henrik Rasmussen (@nomtrosk)Photo by Henrik Rasmussen (@nomtrosk)Photo by Henrik Rasmussen (@nomtrosk)
Henrik Rasmussen retweeted
You used to be able to just create a Native GUI App in 10 seconds. No Electron, no Game Engines, no Web frameworks. Just a lean fast .EXE produced in seconds. Works on any Windows machine WITHOUT Internet connection. Software Development is actually going backwards.
744
1,719
357
22,376
2,150,937
Henrik Rasmussen retweeted
President Zelenskyy thanked the USA 94 times since Feb 24, 2022. United24 Media tracked only daily addresses, so the real count is much higher.
256
2,827
320
10,404
400,653
More important metric than runtimes
This Post is from a suspended account. Learn more
49
My take away from this language performance test: “It took me around 100 lines of code in Go to do the same as with 20 lines with Elixir and 35 with Python.” — @marcelolebre link.medium.com/1SCZmyRNnMb
1
40
38
741
41
4,883
332,435
Henrik Rasmussen retweeted
Software estimates are one of the oldest lies we tell ourselves. We all know they don't work, but pretend they mean something and later feel enraged when shit hits the fan. I focused a big part of my undergrad on software estimation. After graduating, I wrote plenty about the topic. Then, I started working for a company where I spent years researching how to make better estimates. We sold multiple millions of dollars of software using the tools I built. I read everything there's to read. I could recite Steve McConnel's "Software Estimation" book from top to bottom. Here is the most important lesson I learned: People can't estimate software. It doesn't matter who they are or how much experience they have. Estimating software reliably is science fiction. And the best part: They will ask you to estimate something. They will tell you they understand it's not exact. They will promise they won't hold you accountable. And then they will. They always do. There are two solutions for this. Let's start with my recommendations for those who don't have a choice: 1. Remove "quick," "simple," "straightforward," "easy," and every similar word from your dictionary. Never use them. Don't let others use them when referring to your work. 2. Never volunteer an estimate. Everything you say will be used against you. 3. When forced, estimate work you know you can complete today. Always estimate with a range: "It will take me 2 - 4 hours." 4. Estimate anything you won't do today in days and weeks. Say, "I should finish that feature sometime this week." Do not estimate future work in hours. But we all know your manager will force you to give an estimate. Here is what you should do: 1. Estimate how long you think it will take you to complete the task. 2. Multiply the number by 3. This will be the lower range of your estimate. 3. Double the lower range of the estimate. This will be the upper range. Example: If you think something will take you 1 day of work, say "between 3 and 6 days." Here is the funny part: It won't take you between 3 - 6 days. This is as much bullshit as any other method you can think of. The true solution for this problem: Work for a company that doesn't care about estimates.
501
1,610
234
10,012
1,948,502
This presentation blew my mind. Why are all online systems not running Erlang/Elixir?!?! @sasajuric youtube.com/watch?v=JvBT4XBd…
2
12
38
Precise and honest selling points of Rust youtube.com/watch?v=ieXrNJXI…
1
Cool embedded computer with modular peripherals: pockit.ai
This must be the largest dullest enterprise meeting in human history youtube.com/watch?v=J1s1evS3…