161–170 of 183 posts
Earlier quoted context omitted.
[flagged]
You've made a whole lot of assumptions in that reply, all from 10 sentences. Maybe ask some questions next time instead of making assumptions that fit your preconceived notions. Your intuition is a bit off.
Earlier quoted context omitted.
I'm not sure that is actually true about tailors. My understanding is that most clothing was homemade. I assume people didnt generally make their own shoes but they made their own textiles and basic garments and most people didnt have many garments. Maybe there is a specific time period you are referring to where this was common but as I understand it, pre-industrially there were very few artisans selling products fo…
Presumably he is referring to the industrialization period when suits were the everyday fashion. Once we moved on to baggy jeans and sweatpants, where the fit doesn't matter much, then the tailor was no longer relevant.
Man, I work 8-4 Mon-Fri. As soon as 4 rolls around, I'm done with the money making portion of the day and the rest is just entirely fun stuff. I couldn't care less if what I'm doing isn't ever going to make money, it's just fun / interesting / satisfying curiosity. I run - but I know I'm never going to make money running. I climb - but I know I'm never going to make money climbing. I code for fun on my side projects…
I would like to be able to do that - I have such a long list of things I want to learn and do - but I can't just turn off my work brain at 4pm. I get sucked in by interesting problems. Low level optimization? They pay me for 9-5, but you can bet I'll be thinking about it over the weekend, maybe code up a potential solution. I used to think less about people who check out at 5pm - how can you just leave and not give a…
Man, I work 8-4 Mon-Fri. As soon as 4 rolls around, I'm done with the money making portion of the day and the rest is just entirely fun stuff. I couldn't care less if what I'm doing isn't ever going to make money, it's just fun / interesting / satisfying curiosity. I run - but I know I'm never going to make money running. I climb - but I know I'm never going to make money climbing. I code for fun on my side projects…
I would like to be able to do that - I have such a long list of things I want to learn and do - but I can't just turn off my work brain at 4pm. I get sucked in by interesting problems. Low level optimization? They pay me for 9-5, but you can bet I'll be thinking about it over the weekend, maybe code up a potential solution. I used to think less about people who check out at 5pm - how can you just leave and not give a…
Earlier quoted context omitted.
I'm not sure that is actually true about tailors. My understanding is that most clothing was homemade. I assume people didnt generally make their own shoes but they made their own textiles and basic garments and most people didnt have many garments. Maybe there is a specific time period you are referring to where this was common but as I understand it, pre-industrially there were very few artisans selling products fo…
Presumably he is referring to the industrialization period when suits were the everyday fashion. Once we moved on to baggy jeans and sweatpants, where the fit doesn't matter much, then the tailor was no longer relevant.
You could say it was brief, relative to humanity history, indeed, as a transition period between cottage/home textile manufacturing as well as sewing, and high (and accelerating) automation managed by fewer people and lots of low-paid workers (as it is today).
And such is the trajectory for software development, a brief golden age, between the moment where computers barely existed, and the moment where automation/acceleration takes over.
It won't eliminate software development, but it won't require as many people as it does today. Some "local" artisan shops, highly skilled, and more expensive, may still exist.
But the capital currently feeling high tech salaries will inevitably seek new/other growth opportunities, as it has always done with other growth drivers.
Man, I work 8-4 Mon-Fri. As soon as 4 rolls around, I'm done with the money making portion of the day and the rest is just entirely fun stuff. I couldn't care less if what I'm doing isn't ever going to make money, it's just fun / interesting / satisfying curiosity. I run - but I know I'm never going to make money running. I climb - but I know I'm never going to make money climbing. I code for fun on my side projects…
I would like to be able to do that - I have such a long list of things I want to learn and do - but I can't just turn off my work brain at 4pm. I get sucked in by interesting problems. Low level optimization? They pay me for 9-5, but you can bet I'll be thinking about it over the weekend, maybe code up a potential solution. I used to think less about people who check out at 5pm - how can you just leave and not give a…
As someone who checks out at 5pm, I think you're looking at it from the wrong POV.
The main thing that drives me is the projects I work on in my spare time. I care that _that_ code is a mess. So, I might do a bit of work on that in the morning, but then start my actual paying job at e.g. 8am.
So how can I just leave my hobby project and not give a shit that the code is a mess? Because I get paid to do so, I have to work on whatever my boss wants me to work on because that's my job -- but as soon as 5pm hits I get to think about the stuff I really care about again.
I worked for software/hardware companies for 21 years. Some were stable income for me, but nothing amazing. A few were startups where I worked hard but they didn't go anywhere (fortunately I earned a stable, market-rate income before they failed). One turned out to be reasonably life-changing, and I'm very lucky for that. On and off over that period of time I worked on open source projects, some that didn't go anywhere, some that have been successful.
Right now I'm building something to try to sell. I'm not going to take any VC money or pursue high growth. I'm not chasing the latest whiz-bang AI whatever. I'm building a fairly boring product (that is still fun for me to build), using the tech stack that I want, to the standards of quality that I want. Right now I'm working hard on it, but the goal is that, once it's "done" and has customers (fingers crossed I manage to attract paying customers), I'll be spending no more than 10 hours a week on it (and hopefully less on average). If it "only" gets to $500k/yr in revenue or so, after some number of years running it, I'll consider that a fantastic success. If I can run the entire thing on one or two VMs, and it never grows past that infra-wise, that's a fantastic success.
You can listen to both the angel and the devil and still control your own destiny, outside of the scraps your employer will throw at you. Who knows, though, maybe this idea of mine won't work. But I'm happy I'm giving it a try.
Earlier quoted context omitted.
[flagged]
> I can teach someone who knows how things work how to glue libraries together when/if we do need it, but I can't teach someone who glues libraries together how to make their own things; it's simply not worth the time or effort because it's effectively like starting from scratch and I may as well start with a complete junior in that case. I just want to point out that this goes beyond an argument explaining how hobby…
I absolutely think gluing libraries together is a substandard default way of working that leads to poor results, by the way. "[...] everything in software is someone's abstraction" is a cop-out that ignores the massive gap that exists between finding the lowest level you can execute (in many cases an OS call that cannot be split up into a smaller part, or calls into the lowest API you can find like OpenGL, Vulkan, etc., where we have to play by a driver's rules) and executing a function in a library that calls a library that calls a library that calls the OS or the like.
Taking on the cost of countless layers of function calls, potentially manager code, etc., just because "everything in software is someone's abstraction" is, to use your phrasing, a "nonsense" excuse for poor work and not taking ownership of the code that will execute.
I have a former coworker that elected to use a tokenizer/parser library that clocked in at about 6k lines of Rust code, where I personally decided to simply write one in about 600 lines (in Odin, which probably is considered more verbose). The 600 line one was faster, used less memory and naturally was easier to understand (easy enough to understand for someone who literally had never written a tokenizer/parser before to use and extend). It's defensible to use a library for a tokenizer/parser, of course, because "everything in software is someone's abstraction", but do you see the problem here where we get worse software and no one ever learns how to make better things if everyone just decides to `cargo install` readymade solutions?
I'm not saying that my colleague could at that moment have written the Odin solution in this case, but he would certainly be more likely to if he implemented things from scratch as a way of practicing, or decided to otherwise take ownership of the code that runs in work projects.
Earlier quoted context omitted.
I would like to be able to do that - I have such a long list of things I want to learn and do - but I can't just turn off my work brain at 4pm. I get sucked in by interesting problems. Low level optimization? They pay me for 9-5, but you can bet I'll be thinking about it over the weekend, maybe code up a potential solution. I used to think less about people who check out at 5pm - how can you just leave and not give a…
How long have you been a software engineer if I may ask?
Earlier quoted context omitted.
It's not a cushion job. At least not when you are working on a huge codebase together with lots of other developers.
What other jobs have you had? I have been a photo lab assistant, a sign maker apprentice, a graphic designer, an insurance agent, a financial advisor, a construction worker and manual laborer, an inner-city math teacher, a software developer turned manager turn developer, now at the staff level. Software is the most cush job I have had. More money for less work. Better perks. Less stress overall. Constantly learning,…
The problem is: there exists a very specific group of people who do software development as a job who are really passionate and idealistic about software (that's why they actually got interested in software development and decided to do this professionally). For these people, the whole "politics" about software devlopment, bullshit project management processes, not being allowed to make use of their full potential and skills, and office politics is (thus) hell on earth.
I thus very plausibly do believe that exactly for people who are incredibly passionate about software development, other jobs (that are outside their passion) can actually (paradoxically!) be more convenient.