Did them, the games, the websites, the failed startup thing.
I just do other things now.
Building finance stuff during the day, doing little computer outside work (a bit of 3D printing here and there).
It’s fine. My career’s fine. The work doesn’t suffer from it.
Do I have the spark? Idk, I feel I am too old for that spark shit. There is work to do, I do it. If it’s tedious, I’ll drag me feet a while, but eventually it’ll be done. It’s just work.
I think both viewpoints are valid. It's perfectly fine to see your work as a craft which you hone in your personal time, and also see it as a means to an end where you clock in, get the job done, and clock out. It's also understandable that the amount of personal time we have to dedicate to it, and even interest, can vary over time.
That said, I think your day job is more enjoyable when you see your work as a craft. It becomes less of a chore, you feel more engaged, and generally happier, which ultimately has a positive impact on your work and your colleagues. This has been my very fuzzy experience over the years, going through periods of both, but there are no definitive perspectives either way.
About the work being more enjoyable when seeing it as a craft: I think it only is more enjoyable, if you can somehow bring part of your craftsmanship into it, and are not overly limited by other people or the sprint or management or any of the other many factors that ruin the fun, like time available, terrible inherited codebase that would take weeks or months to fix, and so on.
Well, sure, there are aspects of the work that can suck the joy out of it, but that's part of it. :) Even in personal projects I can create a codebase that's difficult to work with, or depend on third party code and tools that I don't particularly enjoy. The tricky task is navigating in and around these hurdles, knowing how and when to address them, and ultimately, simply accepting them. If your expectation is constant enjoyment, you'll be disappointed not just at work, but at life in general.
That said, I struggle with this as well, so I'm speaking more aspirationally than from a place of wisdom. :)
> WPF shipped in late 2006. It was remarkable – XAML, hardware-accelerated rendering, real data binding. If Microsoft had made it the definitive answer and invested relentlessly, the story might have ended differently.
Er… The author perhaps never used it? WPF was the worst framework I ever used. It was unbearably verbose, brutally unforgiving, used 2-way bindings that created updating nightmares, ans not the least it was incredibly slow.
WinForms was not the best for sure, but at least you can get stuff done. It was for a long time the right answer to the question the author asked. .Net + WinForms worked well.
This is the common thread of all their frameworks since, and in my mind the reason they are stuck in an absolute quagmire. For a while it was possible to use HTML/JS in UWP (I think), but it didn't stick due to everyone already needing to move over their LOB apps with crazy amounts of XAML so that's what the focus was on.
"Hey, let's make something that's vaguely HTML but not really at all."
Big mistake.
Avalonia and Uno are repeating that mistake, even though with Uno, at least, there's a blessed way to do unidirectional data flow/reactive stuff.
I personally don't like superpowers very much. My boss does.
I think Claude makes more mistakes when using superpowers than when not.
but maybe it's my fault.
I recommend trying. it doesn't hurt. Just don't believe it's a silver bullet. It's still the same Claude.
The way I use Claude is quite similar to what super powers does under the hood anyways. Like I always ask things like this: "if I want to do X, what questions do you need to ask me to have all the information you need to make it happen"
>The way I use Claude is quite similar to what super powers does under the hood anyways.
I bake my own bread and solo code, both episodic. No matter how I vary fresh starts, I always end up in the same place. The optimization problem feels to be a giant bowl.
This reminds me of named flavors of management style for teams of programmers. A friend in this role instead prefers deep dives into Apollo flight control, and abstracting.
As a solo programmer I always converge on staying extraordinarily involved in planning and code review, and working in steps of finer granularity than superpowers suggests. One may produce less code this way, but it's the only way I know to discover one needs less code.
I was going to suggest the same game, guess the number. But instead of doing it in CLI, do it on her class calculator. If she's 11, she may already have something like a TI 82. These come with some form of BASIC (at least it had 30 years ago).
I remember that I did that about 30 years ago, and then because I had done it, I spent hours playing it.
Then if she likes that, you can make a 2 player tic-tac-toe, or a play-against-the-computer paper-rock-scissors. The fun is to start simple and then modify the game slowly. For example, in the guess a number, you could have funny answers for special numbers.
or a tame-the-unicorn game that's a bit like a tamagotchi, you can feed her, play with her, let her sleep, that kind of stuff, with very simple counters. In the end you can to ride on her back and be her best friend forever.
Anything that's turn-based, where you have very simple inputs that go in variables, check the variable against the game state, and then change the state in a basic fashion, and output something as text, and repeat.
Anything with a graphical game loop is going to be too much imo.
It is an issue because bitcoin is highly unpredictable.
These tools are good at predicting timeseries that are in fact quite predictable. Like insurances will use this to estimate the number of people who will die from cancer in the next year, the year after that, and so on up to 50 years in the future. The model will extrapolate the progresses made in cancer treatment from the current trend, etc. It is a prediction, cause it's still possible that a breakthrough comes in and suddenly people don't die from a certain form of cancer, but generally it should be roughly correct.
Bitcoin prices are a lot more chaotic, influenced by a ton of unrelated events that shape its path a certain way. There is absolutely no certainty that studying the shape of its past evolution will help in any way understand its future evolution.
Of course here I mean by studying its price alone. If you add more information, like who's behind each trend and why, you have a much better sense of what could happen next.
> Who's falling behind? What does falling behind even mean if the OP doesn't care about numbers and really doesn't want to play the social media game?
I think that's rather the point. The author feels that they are "falling behind" by the measure of the high energy social media creators, because they're not following the Ten Things You Must Know Before You Post (Number 7 Will Shock You!).
Did them, the games, the websites, the failed startup thing.
I just do other things now.
Building finance stuff during the day, doing little computer outside work (a bit of 3D printing here and there).
It’s fine. My career’s fine. The work doesn’t suffer from it.
Do I have the spark? Idk, I feel I am too old for that spark shit. There is work to do, I do it. If it’s tedious, I’ll drag me feet a while, but eventually it’ll be done. It’s just work.
reply