I don't think I have properly considered it. Maybe I've just had a bit of baby brain for the last year or so and I haven't completely kept up with things.
Are there any good resources that you can share for those remote positions?
As a counterpoint I have come across lots of software that is only developed for one platform and unfortunately I haven't been able to use it.
Sometimes the difference between a 3mb or 300mb install file is worth it if it means that the software is available to more users. In that sense it can be in the user's interest.
Some Indie games are just great on it too. I played through Hollow Knight, Blasphemous and Dead Cells far more than I would have done if I got them on PC or PS4. They were fairly cheap too.
This could be read the other way too.
In my experience there is a spectrum from reckless to needlessly perfectionist, neither of which approaches are very helpful.
Being focused on delivery is not necessarily a bad thing. But then I've mostly worked in small startups, so perhaps it's different elsewhere.
Isn't it much the same thing as Trump saying something racist that he can kind of get away with?
Johnson can say it, incite some anger in people who won't vote for him anyway, get his name on the news again and appeal to his base. Many of his supporters are the kinds of people that want to "Make Britain Great Again".
There isn't a vast constituency in Britain who love the poem, but there is a vast constituency who are mildly racist and look back to the "good old days".
Yes, Churchill said plenty of stuff that was racist/misogamist even back in those days. Bojo models himself after him. Btw I'm a big Churchill fan in spite of all that. The flawed hero.
I looked over the code for it, because earlier this year I was trying to make a turn based game that merged the gameplay of Imperialism II with the production tree depth of Factorio while having unique little sim like creature with traits that could be bred and inherited and so anytime I can learn something about how to structure code for TBS I'm pretty interested.
Anyhow: it looks pretty incomplete for example here is the GAME.playTurn() function:
GAME.playTurn = function () {
// 0. AUTOSAVE
// TODO
// 1. START OF TURN
// TODO
// 2. TRADE
// TODO
// 3. CITY MANAGEMENT
// TODO
// 4. MOVEMENT
// TODO
// 5. RESEARCH
// TODO
};
So I am not sure that `npx serve` will work and do anything meaningful, or if maybe the logic is in different file / branch.
That sounds like an awesome game - do you have any interesting links for how to structure TBS games? It's something I've always played around with but never feel I managed to get a decent design
I have a copy of SICP sitting on my shelf right now. I've really wanted to get started on it, but I must say that it seems like the kind of book that would take hundreds of hours to get through (with all the exercises, etc). Is that true?
Roughly how long have people taken to get through it?
I worked through the book in my spare time some years ago, and yes it probably took me hundreds of hours. I don't know the exact amount of time, but it was definitely in that range. I did not have any CS or math background, but a lot of practical programming experience. I was absolutely worth it.
I did not watch any of the lectures, just worked through the book, so I can't say if watching the lectures will make it easier or just take more time.
Thanks, good to know how much time I need to apportion.
I'm trying to find a way that I can fit it around work/family schedules and not let my concentration go too stale. I'm thinking of trying for an hour a day, but that feels so prescriptive...
The only advice I can give is, do not set goals like a chapter a week or n exercises a day. Sometimes a section or exercise is just hard and you have to take the time necessary.
This might be considered heresy but the first two chapters can go very quickly, and taken alone can be very impacting, so I'd recommend just them as an initial goal. Once you accomplish it (sooner than you might think!) you ought to use the momentum to continue on, just know it's a steep book for the last few chapters...
A quote I keep in mind: "The reader who has read the book but cannot do the exercises has learned nothing." -- J.J. Sakurai
I'm not quite as strict as Sakurai suggests -- sometimes it's helpful for me to plow ahead anyway and try to come back to the exercises later... Sometimes it's never, but if I do some exercises, integrate some of the non-exercises with other bits of knowledge, I still feel like I've learned something rather than nothing. "Gotten familiar with" might be the best phrase, and there's a nice technique Mike Acton made an infographic of for getting familiar with a stack of books on short notice: https://itsyourturnblog.com/you-cant-cheat-at-learning-quick...
My background is as a self-thought programmer. Never had any formal education related to software, but have worked professionally as a developer for many years. This gives some solid pragmatic experience, but the "fundamentals" tend to lack. I considered a compiler a form of black magic which I had no hope of ever understanding.
SICP gave me a throughout tour of basically all layers of the stack. Understanding the fundamentals of compilers just makes it easier to understand the design decisions behind individual languages, which makes them easier to learn and easier to leverage. SICP is also a journey throughout various paradigms - imperative, functional, stream based, lazy, OO, constraints solving etc. Having a solid grasp of various computing paradigms just give you much more freedom in your approach to solve problems. It also helped dispell any religion I had about particular platforms and languages - I realized religion is just comfort + fear. Experimenting with things like continuations and backtracking was almost mind-altering for me, since I thought the stack was an immutable law of nature and just not a particular design.
Are there any good resources that you can share for those remote positions?