You make a good point in that Docker promised to make dev environments reproducible so that everyone on the team would have the same environment. They even succeeded in that, but either intentionally or accidentally omitted reproducibility over time due to the introduction of non-locked dependencies.
arendjr
joined 1 year ago
Actually, I stand corrected. I just looked into insertion sort again, and you're right, it was insertion sort I initially came up with. The funny thing is, I was later taught "bubble sort" in an Informatics class in high school... but in reality that was insertion sort too!
So it seems I was taught under the wrong name and never realized, I wonder how many others are in the same boat 😅
~~Yes :)~~
Edit: Sorry, this wasn't true, see other comment!
Dunno what to say except that I started programming as an early teenager without formal education, so I “invented” bubble sort before I ever heard of other sorting mechanisms.
I agree it shouldn’t be used in real-life, but to me it’s pretty intuitive and at least I’ve disproven that “nobody” comes up with this by themselves :)
As someone who doesn’t like AI-based auto-complete but will happily use AI occasionally to ask questions every now and then, it looks like these guys might be on to something.
I’m not using Zed yet, but this is giving me some incentive to try it out.
As a junior with no clue how to write production code, is Clean Code going to provide with a decent framework I can quickly learn to start learning my craft, should I throw it out completely because parts are bad, or should I read both Clean Code and all its criticism before I write a single line?
I see what you’re getting at it, and I agree we shouldn’t increase the load for juniors upfront. But I think the point is mainly there are better resources for juniors to start with than Clean Code. So yeah, the best option is to throw it out completely and let juniors start elsewhere instead, otherwise they are starting with many bad parts they don’t yet realize are bad. That too would increase cognitive load because they would need to unlearn those lessons again.
Also in Europe, but I’ve worked at 3 different startups before becoming a contractor earlier this year.
- First one I worked for 5,5 years, joined at ~30 people and saw things grow to 180 people at which point the company was sold and I left about a year after that.
- Second one I worked for 7 years, was one of the first employees and responsible for building their frontend stack as well as various microservices from the ground up. Company grew to about 80 people, but I left after Covid layoffs. I wasn’t one of the layoffs, but culture went to shit quickly after that.
- Third I was also one of the first people and helped build a pretty exciting architecture from scratch. Stayed for 3,5 years, but unfortunately the company never found market fit during that time and the team never grew beyond ~20 people.
Overall I can say:
- If you value autonomy and you have a getting-things-done mentality this is the right gig for you.
- Culture differs very much per workplace, you may need to be lucky. (I don’t think that’s unique to startups though.)
- You need to be assertive and pro-active.
- Don’t do it for the money. Startups usually pay less, but in theory make up for it by offering equity. But most startups fail, so in most cases this will never be more than theory. Even if you do get an exit, chances are the payout is less than you would’ve earned working those years for a bigger corporation.
- The experience can be extremely rewarding because you can easily reach a position of influence.
- You will learn a lot.
- The experience can be frustrating because there is always pressure and a lot to do and you rarely have the means to do it all.
- You will need to improvise a lot.
- If you pull it off and your startup becomes successful the thrill is exhilarating.
I thought we were talking about gamers and Linux users? :p
I have a Framework laptop (Intel GPU) with Arch and KDE, and while I’ve never seen all windows crash when connecting an external monitor, I wouldn’t call it out of the ordinary for one or two to crash after I connect one, especially if I try to drag one to a new position right after.
This is the real reason we have linters.
I absolutely agree with you. If I can avoid NPM I will indeed do so. Sometimes that means using Deno, but sometimes it can be a valid reason to avoid using the language altogether. And sometimes we have to suck it up 🤷♂️
As someone who’s not used to Fahrenheit I can tell you there’s nothing intuitive about it. How cold is “very cold” exactly? How hot is “very hot” exactly? Without clear references all the numbers in between are meaningless, which is exactly how I perceive any number in Fahrenfeit. Intuitive means that without knowing I should have an intuitive perception, but really there’s nothing to go on. I guess from your description 50°F should mean it’s comfortable? Does that mean I can go out in shorts and a t-shirt? It all seems guesswork.