People in a few hundred years are going to laugh about the laws created in late stage liberalism. The frenzy and idiocy makes things like beard taxes seem reasonable
Not in 100 hundred years, by then they will be busy hunting and fighting. But in 500 years, when they will have universities and history departments again, yes, our age will be an eternal source of amusement.
If anyone wants an autocratic system we should give in to their wish, and give them, and only them exactly what they want. If they don't want rights and want to be ruled by a dictator I am sure they would have no problem with it. Leave the rest of us alone please.
Even if you're somewhere where the wind could give you 90% of your energy, you'll still need a reliable, baseline power source if you don't want everything to randomly shut down the other 10% of the time.
Wind + solar aren't as cheap as the LCOE makes it seem because you always have to pay for another source of power as baseline. If you added similar subsidies to natural gas it would be by far the cheapest energy source
Multiple hour coding assessments will work for people who are motivated for a new job. But every company wants "passive" candidates that are already working somewhere. If they're already (moderately) happy somewhere, they're not going to spend 3+ hours on your pre-process.
Companies that can identify talent without wasting the talent's time will be at a huge advantage
* None - just ignore the scripting and let the default AI take care of everything. There are some items that can't be used this way, e.g. Teleport and EMP, because the default AI wouldn't know how you'd want to use them.
* Blockly - use the block-based scripting to control your bots. This is what I suggest as the step for newcomers who still want to customize their bots' behavior.
* BotLandScript - this is a subset of JavaScript that I only recommend for people who already know how to code.
Blockly and BotLandScript should have feature parity (not that they do right now, but the differences are somewhat minor given the target audiences for each), so you don't necessarily have to code (or even know how to code) to play Bot Land. Then again, scripting will certainly give you an advantage.
For the record, the "figure it out" block is what kept me in the game instead of trying it once and moving on. A lot of these strategy coding games like to throw you in the fray and start you off with a blank slate.
I know how to code, but I don't know how to win a game of BotLand. Having the ability to just start a match right away is killer.
I played a dozen or so matches so far. Really excited to see how development progresses. Also surprised at how well the mobile app runs considering it's a web wrapper (but it doesn't feel like most web wrappers do!)
Blockly (or similar methods like Blueprints in Unreal & Simulink) is how most people will program in the future.
You’re going to get negativity from “developers” about using Blockly, but unless they’re your target audience don’t let it get to you.
Lots of EE’s use graphical tools to layout the circuit boards anyway... so text is really just an unnecessary abstraction over schematics & you’re bringing programming back to its roots :-)
Want to make a timeframe for that prediction? I'd like to record it... While I agree to ignore the criticisms from people who won't even play the game (which includes me, so I haven't commented on it, even though I've played a number of variants on this during high school) I think your prediction here is a stretch. First a quote to consider:
"Linux supports the notion of a command line or a shell for the same reason that only children read books with only pictures in them. Language, be it English or something else, is the only tool flexible enough to accomplish a sufficiently broad range of tasks."
-- Bill Garrett
Now a point about EEs/CEs... it's way nicer to write:
than to actually lay out and route a flip flop. Of course you're going to simulate such modules, and use graphical tools (the least of which is just to picture signal waveforms), this isn't to say graphical tools are going away or are pointless, but I would readily take the other side on a bet about your prediction since I don't think programming will even in 100 years be something people think of as manipulating graphical elements rather than typing/chording expressions satisfying some grammar/syntax we'd call a language.
We want to be a full fledged talent agency for software engineers, and the first thing we're making better for engineers is the interview process. We help you design your own interview process to best show off your skills.
One of the things that make tech interviews so nondeterministic is that it's like taking a test where the teacher never told you what to study. With us you'll know exactly what and how many steps there are in every company's process, and what to prepare for - from the beginning.
A big part of this is negotiating with companies to create personalized technical interviews. Maybe you're an expert in Kafka, so you can give a small presentation on how they could be using it and do a Q&A with the team. Or you're good at getting up to speed quickly and want to show that off in some pair programming. We want creative processes that don't leave you feeling like you just went through a meat grinder.
Companies also want to test your knowledge in some way, so we work with them to get you a guide of what to prepare for. But no being peppered with random CS questions - you'll have a company specific guide on what is important to know for the role, and what you can expect and prepare for in the interview.
This has gotten a little long-winded, but would be interested in talking about what else sets us apart from Triplebyte / Hired, or anything else that comes up