Aye, most of my 10 year career in web dev is pretty much those commands. However, some advanced git concepts are worth diving into. Stuff like git bisect that can narrow down the exact commit that broke your app is an absolute life saver. Knowing how to git cherry-pick is also a git skill professionals should be comfortable doing. Migrating work from one branch to another without merging the entire branch is pretty common.
The missile knows where it is at all times. It knows this because it knows where it isn’t. By subtracting where it is from where it isn’t, or where it isn’t from where it is (whichever is greater), it obtains a difference, or deviation. The guidance subsystem uses deviations to generate corrective commands to drive the missile from a position where it is to a position where it isn’t, and arriving at a position where it wasn’t, it now is. Consequently, the position where it is, is now the position that it wasn’t, and it follows that the position that it was, is now the position that it isn’t. In the event that the position that it is in is not the position that it wasn’t, the system has acquired a variation, the variation being the difference between where the missile is, and where it wasn’t. If variation is considered to be a significant factor, it too may be corrected by the GEA. However, the missile must also know where it was. The missile guidance computer scenario works as follows. Because a variation has modified some of the information the missile has obtained, it is not sure just where it is. However, it is sure where it isn’t, within reason, and it knows where it was. It now subtracts where it should be from where it wasn’t, or vice-versa, and by differentiating this from the algebraic sum of where it shouldn’t be, and where it was, it is able to obtain the deviation and its variation, which is called error.
Add a bit of the right structure and you’ve got the pseudocode for dead reckoning. (I guess that was probably the point, but I’ll hit the ol’ post button anyway…)
If you want the same traces as Java and python in the meme, you leave them, if you don’t you strip them. Or you ship them separately. You decide, like a big boy.
Have the user compile it without debug symbols to save space. If the user has a problem they can just recompile it with debug symbols and see what went wrong with gdb.
I’ve written a non-trivial amount of Elixir. It’s nice, but I wouldn’t say it’s like Ruby. It’s more heavily functional, and it wants you to work with data in an immutable way. If you’re coming from a language that doesn’t force immutability, then you’ll be miserable until you get your head around how to work that way.
I really like it, though. Especially now that it’s getting optional typing.
Elixir is an awesome language. It takes some getting used to as it’s meant to be more functional like Haskell, but it plays really nicely with big parallel workloads and is super clean to write
Don’t learn Elixir to replace Ruby. Learn it to enjoy OTP and BEAM.
I would love to join a cool company that’s willing to accept a dev that can transition fast. However, most of Elixir job listings I find are gambling or crypto. And I ain’t gonna touch those.
RoR is too much magic for me. Getting started with any new code base is such a pain that I never want to do again. As a manager, I’ll avoid any job post that mentions Ruby. I have maintained projects written in Delphi, Centura, Java, C#, PHP and none of them even come close to the pain of RoR. Java and C# are notorious for ceremonial interfaces but that’s nothing compared to trying to figure out RoR automagics.
Maybe in enterprises settings what you say makes sense, but for the small to medium startups I usually work for, RoR is great. It’s super easy to prototype and switch lanes. If I had to do what I do in Java I’d go insane. As for Delphi…
The RoR “magic” being obtuse is extremely exaggerated most of the time and more meme than reality. If you think PHP is better, by which I guess you mean Laravel, how on earth is that less “magical”? React? Next? I’ll take Ruby any day.
React can go fuck itself with a pineapple, fuck that piece of shit. Every project I’ve had to deal with that used React was an absurdly bloated mess because it imported fuckloads of React plugins and addons.
There is a lot of magic in Java. Try Spring Boot for example, and things magically connect together with annotations, or somehow methods get injected onto interface on the fly, or an http interface maps onto a function with parameters because the runtime is doing it. This is most evident when you set a break point in some class and there might be 4 or 5 mystery functions it passed through between it and where you thought it was calling from. Sl4j, Lombok, Hibernate are doing the same kind of thing.
That guy is not asking, is demanding. I use lots of open source software and am aware that the developer is often stretched thin. If I can’t help with the project (can’t say I have in the past two decades) I want them focused on what is important and what probably keeps them motivated, writing code and adding cool features. If they have time, fix bugs. If there is more bandwidth, write documentation.
Not wasting time making an executable for every OS out there because some ingrateful asshole is too lazy to figure out how to read instructions in plain English.
If you don’t know what you’ve done within a commit, it probably shouldn’t be a single commit, with or without AI Although if you’re talking about using AI to make funny commit-messages…
<span style="color:#323232;">// DO NOT REMOVE. We don’t know why but if you take off
</span><span style="color:#323232;">// this function the plane stops flying.
</span>
Just comment out the window until it is fixed. Either way it isn’t dangerous as long as you surround it with try/catch.
But I don’t know exactly about that catch part if something happens a few miles above.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.