You would just move the conversion logic to its own re-usable block and place that in your algorithm
Then if you say double click the conversion block you can see the logic inside it
3,544 karma · joined December 30, 2016
You would just move the conversion logic to its own re-usable block and place that in your algorithm
Then if you say double click the conversion block you can see the logic inside it
The way I see it is optimizing for average happiness
If you're getting a lot of money but you really hate 1/3 of your day it can bring the average down
Especially when you get to a point where the marginal increase in happiness from increased salary is small
Usually combined with some sort of visual scripting for the higher level logic
One of the coolest things is working on tools used by artists and seeing the result of what they make with it
Pay is lower but the work is much more interesting/satisfying
This one is so true
I don't understand why younger programmers are so obsessed with which language is "best"
To me the algorithm/logic in the abstract is the interesting part
I would much rather work on an interesting project/problem in a "bad" language than work on a boring project in a "good" language
Very low marginal unit costs, easy distribution, faster iteration, easier to scale, etc...
Its much harder than I thought
I started off explaining binary and how groups of wires can be used to represent numbers
Lost them somewhere around explaining gates/adders
I think its so difficult because there are so many layers of abstraction and you really need some basic electronics knowledge
Some good discussion here
https://news.ycombinator.com/item?id=30937201
One thing to keep in mind is that it’s not actually “no code”
I’ve worked at a big studio and if something was pretty complicated, performance critical, or just not supported by the engine it would be written in C++ and exposed via a new “block” that can be dropped in.
So one reason it works is because most projects you still have programmers on hand to abstract the hard stuff
I pull out the app all the time to answer various questions
For example:
* What kind of oil does my car take again? When was the last oil change?
* How much did I weigh in 2015
* What's the square footage of my apartment?
* What was my start/end date of job X?
Lots of random details like that I may need to reference later
I use the tables a lot for anything that changes over time
Stuff like this is pretty unstructured so I like having arbitrary hierarchies to keep it organized
Did you read the article?
What’s the difference?
For example, can you solve this problem in your head just closing your eyes and thinking about it? (no using your hands either)
* There is a 2D grid in front of you with coordinate system (x,y)
* X increases to the right, Y increases going up
* Point A is at coordinates (1, 1)
* Point B is at coordinates (2, 0)
Q: If we were to move from point B to A, what direction or combination of directions would you be moving? (possible directions are up, down, left, right)
I can solve this in my head but I clearly visualize a grid and the positions of points while doing so and once I have it visualized I just see the answer.
If someone solves this without visualizing it, what are they thinking or how do they do it?
Personally after working 8 hours the last thing I want to do is more programming/staring at a screen. I much prefer to do other totally unrelated hobbies.
Been in similar situation as OP, chose the more interesting job for similar pay difference and didn't regret it but YMMV
I ended up moving to a much more interesting job in a niche area and haven’t felt the need to work on code outside work since my main job is already interesting enough
The previous one was really comfortable to type on since you didn't feel the 90 degree metal edge digging into your wrist like on the pro models.
Was one of the main reasons I got it.
That is unfortunate.
The wedge air design is the most comfortable macbook to type on IMO since it doesn't have the thick 90 degree metal edge digging into your wrist like the others.
One of the main reasons I got it
And scratched disks was such a problem, I remember trying weird toothpaste lifehacks to fix them
Ended up buying some games twice due to that
I remember having one as a kid with like 25 games on it and just flipping through playing each for like 10 minutes
Recall playing a lot of Ant Attack from one of those discs for some reason
With rendering code I find a lot of the time you have to draw it out on paper to understand what it is doing/how it works
Typically simple calculations involving trig/vectors
I find it easier to have a physical one rather than flipping back and forth between paper/computer
Spent a couple years as a C++ dev and did some side projects (stuff like a toy engine) before finding a graphics role
Really interesting since there is a lot of math involved and you’re pushing the hardware to its absolute limits
Also really satisfying to see people playing the game and see your own changes visually in it
The learning curve is very steep though
It looks way too wide and spaced out on a regular desktop monitor
They usually have a wiki for beginners but it doesn't matter, it still just ends up with an endless stream of beginner content/discussions
Even for example /r/programmerhumor is like 90% CS101 jokes, its like everyone on that subreddit just learned to code recently
Does anyone know what the end goal of this kind of research is or why there is so much interest?
Its definitely cool but is the idea just to make photogrammetry cheaper/easier?
Or are there other use cases I'm missing
It’s called the human brain
I recommend this MIT lecture series, it’s pretty high level and explains some of the current tools and methods, findings. I don’t have any biology background but found it easy to understand.
https://youtube.com/playlist?list=PLUl4u3cNGP60IKRN_pFptIBxe...