907 karma · joined April 10, 2018
* My routine includes brushing my teeth 3x per day for 3 minutes with an ultrasonic toothbrush, I use an interdental brush at night, I use a tongue scraper in the morning and at night and I do an occasional chx mouthwash and semi-regular salt water rinses.
To be fair: finding the right level of abstraction in a sea of uncertainty can be a tricky problem - but sometimes this also just happens for very different reasons than out of necessity (ivory tower architecture commitees, external companies selling the most expensive solution, ego fueled idiocy or just plain old ignorance).
> Where high quality is nice to have, but is not the be-all-and-end-all.
while being mostly true in all other cases I don't think it does it justice what mediocrity actually means for everyone involved. I have seen very varying levels of quality requirements/enforcement, testing, delivery speed and eventual bugs at different costs at different companies. And I in general found that higher quality software and less bugs were associated with much happier and more productive developers. And I would make the argument that less happy developers => more turnover => more second order costs. So while it might not make or break the company it certainly has a negative impact on profits downstream. And for customers too. Vendor lock in is a great thing for a company to profit from but if you really make a shitty product it opens up a lot of venues for competitors to eventually canibalize your market or from users to jump ship the next time they can. Take MS Teams for example. Lots of lock in but trust me the second better competitors are on the table I vigorously fight to switch. It's a slow burn but a burn nonetheless.
Quite a lot to unpack here. I would argue the advice given is really good and valid for most people and so that's a good thing. I am sorry you feel under-represented and hope you find something valuable for yourself elsewhere.
Additionally I think lots of people find that they have to force themselves to start and finish a workout and only some eventually come to learn to like it. But for many it starts as a chore like preparing food or doing laundry or taking a shower. It costs time and effort and often hurts. And people can go for a while without any of those but it usually has consequences which are usually worse in the long run than the initial invest.
You seem to have a fairly static view of who "you" are. I used to be in the camp of "my body is just a vehicle for my brain" camp and did not understand why I would exercise at all since I was always skinny (but also super weak) and my mind was what I was working with. And then my grandpa told me: "A healthy mind likes to reside in a healthy body" and that took a few years to really sink in. And now I realize that pushing myself through regular workouts and making myself deliberately suffer exhaustion, fatigue and pain makes me more happy, stable and relaxed in general and I even think of myself as a fit athletic person now and made that part of my identity.
And lastly I am kind of curious about a thing: You said that you only want to do it when it's attached to a game. So if you share the notion that exercise is good and you already know that this is how it's easier for you to do it, then why not focus on exercises which are also games. There are so many of them. And for everyone else who does not need or want a game, meditating or doing yoga seems to be another great venue to start.
I can understand the performance argument but most of that is being worked on and the next team has already shipped lots of improvements in the past. But maybe the things I worked on haven’t reached a scale yet where these things become a bottleneck.
Back then I modelled the quantum circuit as a set of unitaries (by parametrizing them through their generator), that operate on one or two qubits, set a limit to the amount of steps and the amount of controlled gates and then threw different optimization algorithms at it. I got the best performance using simple dense neural networks. What's cool is that I could generate a training set really quickly since I could just randomly build tensor products of unitary matricies to create billions of unitaries of up to 7 qubits in minimal time and then just see how close I can get given a fixed length for the quantum circuit and a fixed number of control gates.
I really liked this approach and it was fun to work on. However it was ultimately limited as the size of the matrices scales exponentially with the number of qubits.
I am also really curious to see the projects which will eventually be selected. It's an interesting time we live in and I would argue that before we know it we will use highly AI augmented or enabled services in the future which will provide value we don't even know of yet. We had maps before we had google maps. And we had coaches before we had cars. And yeah, a lot of the AI stuff we see these days is mostly cool toys and lots of buzz to ride the wave but I am convinced we will see some really impactful stuff come out of it.
I also wonder how much of an impact the new Nvidia HGX systems will have on the medium term infra cost on running these services and whether we will see some benefits from that.
I also wonder if people who are in a position to sell our build houses will try (and maybe even succeed?) to sit this out or whether we will see a downward trend in prices again.
[1] https://weatherspark.com/y/68301/Average-Weather-in-Hamburg-... [2] https://fastrt.nilu.no/VitD_quartMEDandMED_v2.html
Maybe there is someone here who knows more!
O2 Unlimited:
- 32,99€/month for 4G/5G capped at 3mbit with unlimited data
- 42,99€/month for 4G/5G capped at 15mbit with unlimited data
- 62,99€/month for 4G/5G up to 500mbit with with unlimited data
Vodafone:
- 79,99€/month with 4G/5G up to 500mbit with unlimted data
Telekom:
- 84,99€/month with 4G/5G up to 500mbit with unlimited data
1und1:
- 49,99€/month with 4G/5G capped at 10mbit with unlimited data
- 69,99€/month with 4G/5G up to 500mbit with unlimited data
But if I am completely honest lots of government agencies and the people working there are entirely complacent with the state of bureaucracy because they don't feel like they can or need to change this sorry state of affairs. I had to wait more than two months to get an appointment to be able to formally leave the christian church to avoid paying church tax. When I went there the woman took my ID, started typing all my credentials into some interface of some government software for 10 minutes and then I could go. I don't even remember saying or hearing anything but "Hello", "ID Please" and "Bye".
Why can I not do that online with my ID? Why did she have to type in all my information and not get that from some other government body? Why is she even typing it at all of it's all on the ID and that could be scanned as they are entirely standardized. What did I wait for two months for?
When I talk to people who work for the government they tell me it's just the process and they simply don't question it. Sometimes some complain but there is little or nothing to be gained. And I think herein lies a bigger part of the problem. The structure does not reward or incentivise improvement.
And so I would argue the problem is not one of being publicly or privately owned but about the structures that provide incentive to offer good service. And if there is none - regardless of the ownership model - then most likely it will fall flat. When you have privately owned monopolies you see a similar effect - they don't need to improve affairs, they just need to stay in power.
So first of all, _you_ can use whatever ORM or database solution you like in general so _you_ specifically choose which technology you want to invest in. If you want to hand craft your kubernetes cluster for your database nodes and put them on GCP or Azure, then go for it. You want redis? Go for it. If you want to use supabase, firebase, planetscale or whatever, use that. If you want to choose a KV store that's built into your runtime then that's great. Believe it or not but people use lowdb in production and their database is literally a json file. I would argue whichever you choose, switching from one hosting provider, database solution, managed or unmanaged platform to another will always incur cost and how high that is will depend on your depth of integration and familiarity with it. I am most likely going to use this feature and I am happy it exists. Also let's not ignore that there is a large breadth of different needs that developers have. Would I build a massive modular corporate CRM system with BI features with it? Probably not. Am I going to build my next D&D game tool, habit tracker or Tinder for sneaker trading for it? Maybe!
I sincerely wonder what specifically you loose from this feature simply existing.
But here I sit, reflecting on my day-to-day: After the daily standup my PO calls me to ask if there is a chance that our external A/B testing tool can be coerced into tracking some arcane user flow in a slightly different way then the rest. After fiddling around with it for 30 minutes I conclude it can't but I have another idea on how they might get some of the data they want which I promptly put into words forwarding to the relevant people. I then get on to select a ticket from the backlog. Upon reading I notice the ticket is missing some info and the linked figma design is incomplete so I call someone from the design team to get some info and while we are at it we notice that the proposed solution is overly complicated and we settle on changing it - something that did not occur to anyone during refinement. Before I get to start coding the next teams meeting starts, this time to give us a brief of the strategy for the next quarter, and back to back the next refinement meeting starts. Half of the tickets have holes and missing edge cases in them and about 10% of them need to be outright discarded due to fundamental problems with our setup or architecture. We have lenghty discussions about minutiae of the user stories until finally the call comes to a close and I get some time to code. So back to my ticket. I open VSCode and I am greeted by our nextjs project: 850 components, 150 pages and 2200 unit tests and integrations with at least 12 different services in it - encoding the needs and wants of my corporate overlords and the history of it all. I get to identify where in our architecture the wanted feature fits best and think for a while of the exact composition of the components to fit our code style, best practices, testability requirements. I start scaffolding the first component when I see another call plop up. Someone from the testing team is confused why suddenly their locally initiated E2E tests against the dev stage fail. After 5 minutes of perusing logs it turns they didn't pull from main this morning and after doing that all was well. Back to coding. After scaffolding three more components I get to write a little more boilerplate and writing two or three utility functions to juggle around some data I proudly look at my code. Finishing touches and manual testing reveals that all is well. I write a storybook story for two of the components and think about which props should actually be controllable and mock out some of the involved api, write three little unit tests and one integration test to finally push my change to a newly minted feature branch. While the azure build and test pipeline slowly crawls towards completion I open our board, move the ticket to the code-review lane, put a small reminder into our dev teams channel and log my time in the time tracker. One hour of coding effort for ticket #31221. Good! While implementing my feature I noticed that a library we were using is out of date. A cursory search through the changelogs reveals that some of the breaking changes introduced in newer versions would break our app so I go on to write a technical ticket about that and put it in the backlog. Quick note to the PO that I got something for the next refinement and off I go to the next ...call. A bug in prod. Turns out one of our docker pods kicked the bucket. A quick restart and everything is fine again but we get into a lengthy discussion on whether we could finally migrate to some serverless architecture. I look at the clock. One more hour to go. Not really enough time to start a new ticket but looking at the board I find three tickets ready for code-review so that's what I do. One of them is from a less experienced dev so I try to be as thorough as I can and find a few things here and there which I promptly add as suggestions to the pull request. 10 minutes left. I sign off teams, close VSCode and close all tabs except for the time tracking one. I put in the last few entries and I am done for the day.
I am not scared of AI taking my job just yet. Not as long as I have to defend technical choices in front of business people, implement the most outlandish user flows with obscure edge cases, have back and forth discussions with the design team on the difficulty or feasability of their longings, help QA people with their setups, debug devops problems, show off progress, write changelogs, estimate PDs for different stories and epics on different levels of granularity, onboard new developers, off board other developers, dance around in retrospectives, conjure up ideas and solutions for architectural re-orientations and so on. Actually writing some code is only <25% of my job anyway. And I am no staff level engineer or tech lead. Just a frontend engineer with some side knowledge. All the frontend devs on my team are like that. But maybe I am just working on weird projects. Who knows. Maybe one day I'll just orchestrate AI or have to re-orient but for now I am fine.
To get back on the topic of perturbation theory I remember how the mathematical physicists in our lectures always complained that the systems the professors would use it for were not well suited to use it in the first place but often times the results were kinda nice so they used it anyway. Not that I remember any details but I was so fascinated when I found perturbation theory used again in QFT and it really dawned on my how powerful of a tool it is.
I would even argue most progressives are seeing flaws and don’t accept them and push for change but you don’t need to be “radical”(as in further from the status quo) in your views to do that and it doesn’t make you less of a progressive - you are just trying to push to a different spot on the manifold.