262 karma · joined March 24, 2018
this weierstrass function is definitely a mind bender I remember from high school.
Use sparingly of course, weigh in time for making the argument, but this is an artifact just as a convincing research, text or a plot. code can be part of the argument.
Imagine you're in the ancient times looking at your cell phone and seeing this distant galaxy in so much detail. Don't think about the technical details and the long time period facts and all that. Just do it as though you're looking through a special magical lens that allows you to see it, because you are!
then for the stereogram you do the same, observe the out of focus edges of the left and right pictures, then slowly uncross until left and right image occupy the same spot as though they were the same object. now its out of focus, but one (ok, actually three, because there were two, you “doubled” that by crossing, then merged two of them. but ignore the other two and focus on the merged pair)
sometimes you will merge images of the same picture, in this case you are just back at your normal vision, repeat :)
then you try to keep them overlapped and focus the vision, try to “believe” that you are really looking at a single object.
There is a notion of a “Pollyanna mode” in schematherapy. What it means is ignoring negative facts and challenges with an outwardly positive attitude and avoiding addressing the issues themselves.
This certainly can be harmful to oneself. Another harmful thing is hating and bashing oneself for mistakes and faults and I won’t make a comparative judgement, but a healthy way is supposed to be along the lines of speaking up openly about what bothers you and thinking what can be done about it if at all.
In the old system a lot of things were really slow. I know that now half year in we already have a couple of problems solved that required me and a small team’s half a year work to solve and right now Im working on a problem that almost was not solvable at all before, I’m planning it infractructurally solved by the end of the year.
Other teams say they threw away a lot of grabage that grew with the old implementation and kept only “the good parts”.
A lot of work done by the teams is now offloaded to the infrastrucutre.
We have remote IDE for everyone from day one instead of build-inside-docker-do-what -you-want because old build system could not be and never was thrown away overnight.
List goes on
What made it great: the company is 7 years old, I work basically since inception, half year late.
The codebase had some serious problems due to migrating build systems, rapid team growth and lack of proper communication while developing important infrastructure tools, lack of foresight at the start of a crucial requirement for the whole system that became clear 3 years in.
Aaand… Due to unique sequence of events half a year ago we had to start everything from scratch! We could not use a line of code from the old repo !
This brought miracles out! We started designing the right things right. People started talking to each other on the global scale, without the code limiting them!
The old code not only had problems on the engineering level, but it held people and team responsibilities along suboptimal interface boundaries! This is the biggest magic! After the rewrite started, all the people in the team landed exactly where they wanted and their areas of responsibility became clear and highly efficient. Some people started shining like I could not imagine. Because their organizational and communication skills were limited by a huge suboptimal codebase.
Also, it is very empowering to design a system when your whole team has real experience 5 years into the future. Also, everyone turned out to be caring about code simplicity and quality, I finally feel at home.
I could not wish for a better developer experience. The sexiest C++ coding time in my life :)
I would be grateful if you could elaborate on this. Is this a strategy for a fund to make money that I don’t understand?
This coupled with people acting on its predictions is a kind of self fulfilling prophecy.
which is to ask, are AI safety folks building models of this pattern? :)
I am in therapy for 2 years now (and not planning to stop for a while), the results I really enjoy and that are visible from outside and clear conseqences are only starting to crystallize. Imagine “learning C++” in 2 months. And that is purely mental. These emotional skills are not easy at all. This is a whole new “riding a bike”, but on all the million wheels of a real human that is you.
Understanding is not the result. The result is your comfort, your confidence, your loving yourself, you being your own perfect loving parent and close friend.
This is actually a missing education in my opinion.
I don’t use rust because I don’t have enough time in my life right now for discovering a new language just for the pleasure of it and even if I had, my real alternatives would be functional languages, not rust vs C++ which I use daily in a big project that has incentives stacked into C++ favor
Regarding “receiving a message”: my devices are allowed only limited use of notifications. Of all the messaging/social apps only messages from my wife in our messaging app of choice pop us as notifications. Slack certainly is not allowed there
I think we start to recognize this at larger scale.
Slack easily saves a ton of time solving complex problems that require interaction and expertise of a lot of people, often unpredictable number of them for each problem. They can answer with delay, in a good culture this is totally accepted and people still can independently move forward or switch tasks if necessary, same as with slower communication tools. You are not forced to answer with any particular lag, however slack makes it possible when needed to reduce it to zero.
Sometimes you are unsure if you need help or you can do smthing on your own. I certainly know that a lot of times eventually I had no chance whatsoever, because knowledge requires was too specialized, this is not always clear. Reducing barriers to communication in those cases is crucial and I don't see Slack being in the way here, only helpful.
The goal of organizing Slack is such that you pay right amount of attention to right parts of communication for you. You can do this if you really spend (hmm) attention trying to figure out what that is and how to tune your tools to achieve that.
Wrote this for myself, I’m a vim user :)
I’m in a desparate need of a message from Captain Obvious right now. I know nothing about perl
Good to see I’m not alone. How is it going so far?
I make it a point to spend time to make my work more comfortable. Thats what I like in infrastructure work.
This is a good video, thank you!