Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)B
Posts
1
Comments
872
Joined
2 yr. ago

  • Kohls doesn't have it always on sale. They carefully rotate stock each week to half their stuff is up front and on sale, while the other half is in the back at normal prices. The staff will direct you awat from the normal priced stuff - they don't want anyone to pay the normal price, they just need to have it as normal price once in a while so they can claim to have a sale. (they fear if you buy the normal price you will be mad enough to not come back and repeat sales are worth more than one full price transaction)

  • Trains, and trucks. Trains can run from overhead wire but so far that has remained too expensive to be worth installing. Trucks are also significant and it isn't clear what we should do about them (there are many options, but what it the right one isn't clear)

  • No real surprise to anyone watching the alternatives take over. Last year my utility told me that the previous year (ie 2023) they generated more power from wind than all customers combined used. California has been building a lot of solar. Texas leads the nation in wind, with Iowa and Kansas both having large installations. There is still a lot of room to go in transport, but for most people EVs would cover everything they do with minimal impact (on road trips they will still need long recharging times, but not unreasonably long) The writing has long been on the wall for most fossil fuels. Anyone who pays attention to the economic factors involved has long known this.

    Most fossil fuels is not all. For sea and air transport we still don't have a useful option. Long distance freight over land is possible, but requires large investments and it isn't clear what is the best investment is. there are other industrial processes that still need fossil fuels. However the vast majority of energy the US uses today would be cheaper long term using renewable sources than the current ones and that is driving investment in switching.

  • I finally gave up. iiwant to keep in touch with what distant friends are doing. Finding and sharing memes is not doing something and that seems to be all I ever saw. Some people need to get a life. (unless you are confined to a hospital bed there are better things to eo with your life.) Too bad - I miss the rare contact with those distant friends.

  • Even in iowa you see them all over. There are so many drivers any car make other than the most exclusive will be seen soon if you fixate on it (read look).

    Stastics show tesla is a tiny brand by market share. However they are wer the only ev brand until reciently so people focus on them.

  • Cool build, but a little reading in how mills and lathes are made would result in a much better machine. The Gingery machine shop series is cheap and good to read even if you don't want to pour aluminum - his machines also make some bad compromises, but the books also inform you of things that would make you do machines like this different if you knew them.

  • It is really hard even when you know this to not pass over ugly people who are otherwise good at their job.

  • Easy to say if your code doesn't matter. If you work for regulated industries (FAA, FDA) you can't ship it out the door.

    I have been working on automating our tests for years. Manual testing still finds a lot of things despite passing all the automated tests. I'm now convinced anyone who says "automate that" doesn't care about quality, humans are too good at finding things.

  • I've worked for both over the years. Small companies have their own downsides. There is no clear winner. People complain all the time, so if you have never worked at a large company you have no clue what it is really like. Sure there are things not to like, but there are also things to like.

  • Works for a small company. If everyone in a large company is allowed the same leeway nothing could ever ship - while no one person (except a few incompetent that get fired eventually) makes too many mistakes, the combination of all of them mean the system is always horribly broken.

    Of course 50% of my job is just getting simple changes though which is annoying - but more than once that process has meant I didn't break everything.

  • A part of it is when you get old you realize the "kids" are doing the exact same thing you did 20 years ago, but they gave it a different name and changed some tiny details so they can pretend it is different. The real question is how do you get kids to see this - most don't (including me when I was a kid - and I was aware of the issue and tried to guard against it)

    The more important part at my age is to remember that kids today are just like me. Sure the exact style and what is in/out has changed, but kids are the same as we were. I didn't even have the option of a smart phone, but I had my own addictions, and the older generation complained about them.... Sometimes the old people have a point, but often kids these days are just like kids in the past.

  • There is a reason a lot of web apps run on the JVM - while it does have high overhead, once your app is running it is fast and you get some nice advantages. Plus Java has a large system of helpers and libraries. Even though you can do everything in Rust, you will end up writing a lot more code just because in Java you can just download a library to do something while Rust forces you to write it.

  • Hating the code is normal. After a while you start to realize all the hard to change decisions you made long ago. What you don't know is if those decisions you wish you had made would be better. There have been a lot of fads over the decades, some of them are complete junk, but the majority have some good points. However all of them have some negatives as well, and there is no obvious answer to which negative is right to accept for your projects.

    The ideal answer is spend 20 years learning lots of different options, then find a time machine and go back in time to and restart the project based on what you have learned. Of course at the end of that 20 years you will hear about some new thing you didn't try, but you have to draw the line somewhere. (finding a time machine is left as an exercise for the reader)

    Rust is an interesting language with some nice memory safety guarantees. As a C++ developer it speaks to some of the problems I have - but most of my problems with C++ are with 15 year old code from before I was able to use C++11. ( had to put a lot of effort into getting this good with c++ though, Rust is likely a lot easier to learn to my level). The Ada/Spark advocates have long been saying things that really speak to me as well - formally proven code sounds great, though there are others who tell me it isn't as good as the advocates claim. Go has some advocates saying interesting things as well, though they don't speak to the issues I personally have as much it might be better for you.

    If you are writing all new code then I would put Rust high on the list. However most programs are adding to something that exists and the friction of writing Rust to existing code is often high enough that I'd stick with what the other code is written in.

  • I wasn't trying to suggest that you are biased, only that I have no clue and so it is possible you are somehow unfairly doing something.

  • Human vision is very, very, very good. If you think a camera installed to a car is even close to human eyesight, then you are extremely mistaken.

    Why are you trying to limit cars to just vision? That is all I have as a human. However robots have radar, lidar, radio, and other options, there is no reasons they can't use them and get information eyes cannot. Every option has limits.

  • And bullshit on you not being able to see the lights. They're specifically designed so that's not an issue for colour blind people

    Some lights are, but not all of them are. I often say I go when the light turns blue. However not all lights have that blue tint and so I often cannot tell the difference between a white light and a green light by color. (but white is not used in a stoplight and I can see red/yellow just fine) Where I live all stoplights have green on the bottom so that is always a cheat I use, but that only works if I can see the relative position - in an otherwise dark situation I only see a light in front of me and not the rest of the structure and so I cannot tell. I have driven where stoplights are not green on bottom and I can never remember if green is left/right.

    Even when the try though, not all colorblind is the same. There may not be a mitigation that will work from two different people with different aspects of colorblind.

  • I can see red clearly and so not sure means I can go.

    I've only noticed issues in a few situations. When I'm driving at night and suddenly the weirdly aimed streetlight turns yellow - until it changed I didn't even know there was a stoplight there. The second was I was making a left turn at sunset (sun behind me) and the green arrow came on but the red light remained on so I couldn't see it was time/safe to go until my wife alerted me.

  • Cows are big and will accidentally kick you breaking ribs, or otherwise injure you. They are mostly safe, but there is a reason farming is one of the most dangerous jobs.

  • Anyone who has driven (or walked) into a sunrise/sunset knows that human vision is not very good. I've also driven in blizzards, heavy rain, and fog - all times when human vision is terrible. I've also not seen green lights (I'm colorblind).