Why not use python at that point? Sounds like the bus factor would be pretty big on this one

Based on things I’ve seen I can actually believe this is real. Just goes to show that you can’t trust everyone to have a functional intuition for separating horrible ideas from good ones.

I use it as a search engine but not as my only source. It’s really good at regurgitating the most relevant Stack Overflow answer I might find, which may or may not actually be applicable to my situation. As a rule I never copy paste code directly, I always rewrite it “in my own words”, even in cases where it’s basically the same. If the code it provides is more than 5 lines or so I can almost always think of a better way. I feel like I’d still be better off with a really solid reference manual though, and a recipe book. But they go out of date too fast these days.

I made some automation in python for common git tasks and use the cli otherwise. I tried a couple like sourcetree and the built in automation for VS but they’re either slow or lack features i’d like.

Yeah, that too! When you have some non technical manager breathing down your neck, you might have a hard time not fumbling around even if you normally could resolve the issue in no time.

I can see how this could be unfair, but working as a dev sometimes does require you to be on top of things in a high stress atmosphere. For example, what if you’re proposing an excellent technical solution in a meeting but some jaded older engineer is hard to convince? If you can’t outline your thinking in that scenario, your solution could be discarded just because someone was louder than you. As someone who used to have performance anxiety, I believe it’s generally something you can and should practice for. On the other hand, if there really isn’t a need for this type of skill, it totally makes sense to avoid creating interview environments where you are filtering candidates based on it.

I haven’t done much low level stuff, but I think the ‘main’ function is something the compiler uses to establish an entry point for the compiled binary. The name ‘main’ would not exist in the compiled binary at all, but the function itself would still exist. Executable formats aren’t all the same, so they’ll have different ways of determining where this entry point function is expected to be. You can ‘run’ a binary library file by invoking a function contained therein, which is how DLL files work.

Yeah, he was bamboozled as soon as he agreed to allow multiple separate files. The challenge was bs from the start, but he could have at least nailed it down with more explicit language and by forbidding any exceptions. I think it’s kind of ironic that the instructions for a challenge related to different representations of information failed themselves to actually convey the intended information.

Typescript on the other hand…

Yeah but like, what new features do apps have which weren’t available in those times? Embedded videos maybe? Doesn’t justify the bloat.

It sucks that you have to do that, but I know people who manage projects just want progress to come in on a steady drip feed. Hopefully some day you’ll get a decent manager who can understand your work style and roll with it though, or maybe get to the point of setting your own destiny!

I used to think C# was like Java but with fresh ideas. I still do, but Kotlin gives it a run for its money. The type system is pretty great. For example, you can use the Elvis operator to return early if something is null, allowing you to use a non-null type afterwards. In C#, nullable annotations feel more “grafted on”, and there are some weird quirks and footguns that Kotlin avoids by being a little smarter about it.

I dunno, I made an ipod clone app in Android for myself recently and it has both acceleration and a db progress indicator. These were not tough features to implement…

Good riddance, I say. Web dev is infested with layers upon layers of tools that attempt to abstract what is already fairly simple and straightforward to work with. We’re beyond the days of needing to build buttons out of small image fragments, and JS is (slowly) becoming more livable in its raw form. I welcome anything that keeps the toolchain as simple as possible.

I think what started me down the anti-React path was realizing that there were other frameworks out there that don’t even use a virtual dom. Plus you get tired of being told that the most obvious and intuitive way to do various things in React actually goes against some best practice that they’ve established.

As someone who works with typescript daily, you’re not wrong. It’s an extremely overcomplicated glorified linter that tries and mostly succeeds in catching basic type errors. But it also provides false confidence when you concoct something that shows no errors but doesn’t behave how you expect.

At least until it gets direct dom manipulation and multithreading…

Same here! I remember when Digg only supported single-level replies. Good times…

I had one of those that was grandma-owned but the transmission shit the bed within 5k miles. What a pos.

I understood what he was talking about instantly… but only because I did the same thing with the brake when I was a kid.