The Codist

His coding blog https://thecodist.com/ is also worth reading.

My programming blog (https://thecodist.com) sees Chrome 52%, Safari 27%, Firefox 9%, over six months covering a fair amount of the world. I use Plausible. I never found GA to be very reliable.

They're not just algorithmic. There's a lot of manual effort in each image: https://thecodist.com/my-art-and-color-after-tiling/, https://thecodist.com/why-i-use-swift-to-make-generative-art/ > In my process, generation is supplemented by many manual processes, including image manipulation, digital painting, and occasionally even AI

He wrote a blog explaining it: https://thecodist.com/my-art-and-color-after-tiling/

I think that this is relevant... 'When I was on TV (Computer Chronicles) in early 1987 showing our product Trapeze the other presenter was Mike Slade who was product manager of Excel. At the time young me thought him some random marketing weenie (young people can be pretty stupid). Yet he started all these companies later including ESPN, worked for Apple in various leadership roles, was a good friend of Steve Jobs and started his own VC firm' http://thecodist.com/article/my-biggest-regret-as-a-programmer

Airline reservations systems are kind of fascinating, because they were some of the first really complex computer systems, and a lot of those crusty old bits are still chugging along fifty odd years later, with newer and newer piles of code layered on top like a demented tower of jenga. http://thecodist.com/article/how_flight_reservations_work_part_1 http://thecodist.com/article/how_much_is_that_seat_by_the_window_how_f…

Relevant: http://thecodist.com/article/the_programming_steamroller_waits_for_no_… “The Programming Steamroller Waits For No One“ Also: https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ “Fire and Motion” The companies who stumble are the ones who spend too much time reading tea leaves to figure out the future direction of Facebook. People get worried about React and decide to rewrite their whole architecture for React because they think they have to. Facebook is shooting at you, and it’s just cover fire so that they can move forward and you can’t, because this is how the game is played, Bubby. Are you going to support Saga? Flow? React Native? Are you supporting it because your customers need it, or because someone is firing at you and you feel like you have to respond?

Nah, I thought it was a good point. It's easy to forget that we either change or become obsolete. It's one thing to know it abstractly, but it's hard to make any lifestyle changes, especially if it involves switching to a job in a completely new domain. http://thecodist.com/article/the_programming_steamroller_waits_for_no_… is a good essay on this. EDIT: previous discussion: https://news.ycombinator.com/item?id=7204515

Wayyyyy too many :) A few months back I wrote a Reddit comment listing "just" the high-quality React-related blogs that I read : https://www.reddit.com/r/reactjs/comments/5t8loz/what_are_your_top_rea… . I read a lot more besides that. To pick out just a few: - Scott Hanselman: https://www.hanselman.com/blog/ - Robert O'Callahan: http://robert.ocallahan.org/ - Henrik Warne: https://henrikwarne.com/ - Andrew Wulf ("The Codist"): http://thecodist.com/ - Lin Clark: https://code-cartoons.com/ . (Her actual blog hasn't been updated in a while, but she's also posted many in-depth articles to Mozilla organization blogs over the last few months.) And while I don't think

Correct. 4 years after this 2012 article, he wrote this [2016] => http://thecodist.com/article/my-biggest-regret-as-a-programmer He laments how he quit Apple when it was going down, then Steve Jobs came along few months later and the rest is history. Also how his Sister went the management route and has 10x Assets etc. I wish I hadn't found this 2016 article because that makes me read this OP 2012 article in a whole new light. And it's not very encouraging... :(

A contrary view: http://thecodist.com/article/my-biggest-regret-as-a-programmer

I'm not saying this to try and discredit this post. However, there's a very interesting trilogy here: Oct 2012: Yes I Still Want To Be Doing This At 56 http://thecodist.com/article/yes_i_still_want_to_be_doing_this_at_56 Jul 2015: How I've Avoided Burnout During More Than Three Decades As A Programmer [this article] April 2016: My Biggest Regret As A Programmer [is not going into management] http://thecodist.com/article/my-biggest-regret-as-a-programmer

His other post about his view of the downside of being a programmer is also relevant here.. http://thecodist.com/article/programming_is_a_dead_end_job

I use the Outline View in MS Word to organize my bookmarks. I use 4 levels: Heading - Subheading -- Link --- Text. (Note that each level is a separate line in MS Word Outline View.) An example: Education - Assessment -- http://www.nytimes.com/2014/09/07/magazine/why-flunking-exams-is-actua… --- test and test often to focus the learners' minds Business - Insights --http://thecodist.com/article/lessons_from_a_lifetime_of_being_a_progra… --- find dumb people with lots of money I find this to be a simple, easy system to organize what I find on the internet.

But I don't think infrastructure/libraries can be considered "co-founders" A better way to express the utility he gets can be summed up in this article: "We Are All Open Source Billionaires" http://thecodist.com/article/we-are-all-open-source-billionaires

I agree. I've been many times in situations where (smart) people said "this is ok, this situation is very simple to manage with threads", then discovered some deadlocks after a week. It is like juggling chainsaws [1]. I try very hard to avoid multithreading - most of the high-performance code I write is single threaded by default. I know MT programming enough to avoid many problems, but also know it well enough to see it's a very costly trap, if it can be avoided at all... [1] http://www.thecodist.com/article/writing-multithreaded-code-is-like-ju…

I've been doing it for two years and am barely past the "understand none of the words" phase. It helps to think of each term as an interesting puzzle. For example, SVD. It's fascinating if you dig into it. Most people don't want to, because it feels like work. For me, it's neat understanding ... whatever it is, ha. I think it's finding the basis eigenvectors in a higher dimensional space, which basically just means that e.g. the eigenvectors of a cube are the X, Y, Z axes you're used to. If you skew it along the X axis, the Y axis bends a bit, along with the cube. The eigenvectors form a shape that, when you find the volume of it, is the area of the resulting form. So the determinant of a cube's SVD is the volume of the cube. In higher dimensional spaces, it's the same thing, except it's called "eigenvectors" (named after Sir Eigen of Eigenmadethisup) because mathematicians have reasons for using complicated language, some of which is valid. But as you see from me muddling through this, the underlying concepts are all small simple pieces that fit together. Or I was nowhere close to the explanation of SVD. But it was close to something interesting, since it leads to the question of "What's the SVD of a sphere? How about a point cloud?" It was easy to figure out for a cube. Not so easy when it's an arbitrary shape. "And why is it useful?" Because it gives a lot of hints about what that object is. In the optimal case, in StyleGAN for example, the SVD can even be the basis…

The Koutnik links to this article, which inspired his essay. http://thecodist.com/article/my-biggest-regret-as-a-programmer. It was very painful to read, because I made exactly the same decision. I was VP/chief developer at a company that withered on the vine after a 10 year roller coaster ride at a software company that I had co-founded. I had two paths: I could have looked for a VP/Director job or I could have continued on as a Developer/Consultant. The money was pretty much the same, so I took the consultant route. The money was pretty much the same and programming was more fun. All went reasonably well until September 2008. I had just finished a very satisfying consulting gig, but I walked out into a very changed world. The day after was the banking crash. Even earlier a divorce had taken me to the cleaners. But far worse, small interesting companies had no use for older, still up-to-date, still competent developers. I found myself going from Finder to Implementer. Agile development, which had seemed like a boon, turned into a tool to lock everyone into two week death marches controlled by upper management. Technical decisions where made by people who didnt have a clue. Just as in the linked article, a woman working for me in the 80s took the management route and was a VP in a major SV software company a few years later. Now she is quite well off. Good for her; we are good friends. Moral? If you are a software developer, dont get old. (I'm still doing…

Unfortunately this person certainly wouldn't fit in at any organisation I ever worked for : http://thecodist.com/article/how-many-people-does-it-take-to-ship-soft… "The more people you have in any project the more communications you need, the more management you need, the slower information is disbursed and problems reported. You have to have more process to ensure that anything will be accomplished. Of course this all costs more money and time and often you have to do less just to get something shipped. It’s easy for everyone responsible for all these people to worry about unknown problems biting them in the ass so every decision becomes very conservative and cautious.This of course makes shipping difficult, expensive and often drags things out for a long time. Add to that memories of previous projects that had the same issues and things get even more cautious and slow." The main function of management at any medium or large company is to manage people, keep the peace and keep things chugging along. This person makes the huge mistake of wanting to be manager ... to do something other than manage people. Wanting to be a manager to use "the power" for good (ha!, having done both let me tell you this: managers have less power than individual contributors. Yes you have "power" to choose, what you say goes to an extent, but only insofar that you keep making "the right" choices. Think of a manager as a 14 year old going to a party and getting told by his parents that he…