seventh-chord

I feel like my ideal workflow would be a middleground between doing the design up front and just jumping into coding. Before you start coding I feel like you don't have much of an idea of what problems you will run into, resulting in diagrams based on the wrong assumptions. But with code it's easy to loose track of the high level structure of what you are writing. Writing code, then diagramming the high level structure, and then going back to fix the code seems like a good way to go.

I've been doing that for my own clothes. White t-shirts turn pink, but pink is a good look too so I don't really care. Maybe that means I'm still a kid :)

Isnt supply price-inelastic in the short term, so "30% above" is the same quantity at all price levels?

Except the things you mention correspond to looking at sales data in your backend DB, not putting google analytics in your frontend, right?

Norway switched back to a tax-based model this year, where everybody above a certain income gets deducted between 150€ and 300€ more yearly. The cost to the average person went down, I assume that is mostly because there will be more total payers now. They also closed a 70-people office previously responsible for collecting the license fee.

"Turing-complete text editor can do anything" :)

To be fair, I dont actually know what percentage of editors have that feature, my impression is just that many people arent aware of the idea. Maybe Im wrong though.

I don't get why more editors don't support parsing compiler output to get the file name and line for errors. Its dead simple, no need to run a server, just allow running the compiler from within the editor and have some way of configuring the parsing so it can work with different compilers. Gets you 90% of the value for 10% of the work (because you don't need to do anything to the compiler).

Im unable to book flights with local airlines via firefox because the payment popup gets blocked with no warning. Sure, I can figure out whats going on and use a different browser, but it's terrible UX.

Ive experienced the same thing, but have attributed it to gaining more experience. I feel like the questions answered on stack overflow usually are ones that one can trivially solve by knowing where to find documentation, and the questions I end up wanting help with are too specific to bring up sensible search results. Maybe I'm just bad at using search engines though...

It seems so scary to ship software where you are not in full control over font rendering, because at that point you have suddenly have a million edge cases which you weren't forced to think about up front, but which can come back and bite you any time. Though I guess with everything running in web browsers it sort of has become the only way to go.

I'm curious in what way microsoft would not be interested in having users not install office. I thought that office was microsofts primary revenue source (maybe this is info from before cloud stuff though).

I guess "not nonsensical" would be more appropriate than "informative" :)

I tend to dump information like that in "// NB (my name, current date) tralala"-style comments. Do you have git integrated in your editor so you have git-blame-style commit messages next to your code? If that is the case, I guess putting the information in the commit messages makes sense.

Maybe it just comes down to how we choose to store auxiliary information.

Which part is it that confuses you? On github the commit messages and hashes on the left hand side indicate the last commit that touched those lines, and you can click on them to see the full commits, including changes made to other files. Alternatively you can click on the "View blame prior to this change"-icon (between the commit messages and the code), which will do as the name suggests: Show the commit which previously changed those lines.

I use git blame, but in the same way I use the rest of git: I find the commit which changed a line, and then look at what else that commit and the ones before/after it did.

I guess there is some value in being able to have a quick description of the commits shown when looking at the blame output though.