HN user

Phreaker00

174 karma
Posts6
Comments34
View on HN
Stepping Back 1 year ago

I read somewhere that the subconscious brain continues "working on problems" even when you are not actively working on it consciously. Hence the expression to "sleep on it".

It's something I've actively used for almost two decades now when dealing with challenges i'm stuck on. I remember one of my professors explaining it as having a 'prepared mind'.

What I do is, before I go to bed, try to summarize the problem to myself as concise as possible (like rubber ducking) and then go to sleep. Very often the next morning I wake up with a new insight or new approach that solves the problem in 10 minutes that took me hours the day before.

Three-dimensional printing offers promise for patient-specific implants and therapies but is often limited by the need for invasive surgical procedures. To address this, we developed an imaging-guided deep tissue in vivo sound printing (DISP) platform. By incorporating cross-linking agent–loaded low-temperature–sensitive liposomes into bioinks, DISP enables precise, rapid, on-demand cross-linking of diverse functional biomaterials using focused ultrasound. Gas vesicle–based ultrasound imaging provides real-time monitoring and allows for customized pattern creation in live animals. We validated DISP by successfully printing near diseased areas in the mouse bladder and deep within rabbit leg muscles in vivo, demonstrating its potential for localized drug delivery and tissue replacement. DISP’s ability to print conductive, drug-loaded, cell-laden, and bioadhesive biomaterials demonstrates its versatility for diverse biomedical applications.

What you're trying to solve is a form of social validation and trust that brick and mortar stores implicitly have: 1. They have to have spent a reasonable amount of money to actually be there; 2. A busy store with lots of people at the registers means there's enough trust to spend money here.

To solve this in a virtual environment you'd need a comparable amount of implicit trust. For #1 it's doable: have a trustworthy domain name. Amazon.com is a lot more trustworthy than look-at-my-shop.tk. For #2 I don't think there's a trustworthy equivalent, since it's either off-site by a third party or unverifiable by users.

https://archive.ph/VEzfd

More should be revealed on 18 March, when Nayak is due to give a talk on Microsoft’s topological qubit data at the American Physical Society meeting in Anaheim, California.

In the meantime, “there’s no convincing, even mildly convincing, evidence for Majoranas”, Beenakker says.

The field of quantum computing is very interesting for the difficulties and claimed immense gains when successful. The route that Microsoft has chosen for its research is a lofty one; doing it fundamentally different than others in the field. However, this 'break through' sounded exactly like the break through reported in 2018[1] which has been redacted.

I'm looking forward to the presentation 18 March

[1] https://archive.ph/ntSxN#selection-1177.161-1177.166

As a freelance back-end developer with various co-founding experience this question speaks to me. I think it's all a matter of perspective.

Looking at it from a development perspective the two can mean the same thing: we pivot and so we need to add new features.

However, in my experience the key is to look at pivoting from a non-development perspective. As mentioned in parent comments you pivot to find a product market fit. That entails finding your audience and the problem you're solving for them. Those questions do not require a product, but a human understanding. Questions like 'is it actually a problem they need solving, or a slight convenience?' and 'how are they solving their problem without my product?'.

By pivoting quickly in that space you don't get bogged down by technical issues or challenges that don't even matter, and the real solution might be a week's worth of time.

Reading the following part confused me, since that's how I learned and I don't know Mr. McIntyre:

But my Scrum friends reminded me that stand-ups were never supposed to be status reports. They said that an evil elf named Yesterday-today-no-blockers McIntyre spread that lie around the industry long ago, and people have been confused ever since.

So I did some digging in the resources from the ScrumAlliance. There I found:

The three-questions format was included in older versions of the Scrum Guide but no longer appears in the updated guide.

So what to do instead? I also found this snippet which I think is useful:

The daily scrum is not a status meeting or status report. The purpose isn’t for a scrum master, manager, or stakeholder to see who is on schedule and who is behind; instead, it’s an opportunity for self-managing team members to synchronize with one another.

According to their press release: ""We've done this to create a bulwark against surveillance capitalism, the risk of buyout, and open-source projects becoming abandonware," the Open Home Foundation states in a press release. "To an extent, this protection extends even against our future selves—so that smart home users can continue to benefit for years, if not decades. No matter what comes."

As we've seen with 'OpenAI' there's never a guarantee, but I applaud this step.

For someone who has been in this field for 20 years I remember starting out doing every aspect of webdevelopment myself. Then the bigger and more complex the projects became, the less that made sense.

The requirements of the distinct fields have gotten to a point where it's very impractical and hardly worthwhile for one person to master them all. You can't expect someone to translate a design into modern components that support all types of devices, resolutions and contexts to also come up with optimized SQL queries and knowing how to choose between Docker and Ansible for their distributed serverless functions that handle a variety of external endpoints.

Ofcourse not every project that uses this approach needs this approach, and there's still a market for the Do-It-All developer. My point is that the webdevelopment world of today isn't that of a decade ago.

The writing of actual code in my experience isn't usually the most creative part of the process. It's the path leading up to the point where you actually start typing code; the translation between business goals and technical solution that requires creativity and ingenuity.

Especially in a team I can see a lot of added value from someone with a lot of experience during this proces. Documenting the outcome of that creative process is easily done with text-to-speech software.

Stream deck was a surprisingly good buy for me as well, although in 2020. Previously I had a keyboard with a lot of macro keys, but that died and I didn't want to go without the handy shortcuts I've set up. Now I'm using the stream deck for much more than what my keyboard offered.

In terms of best buy in 2022 was the Peak Design Capture Camera Clip. For a photographer it's amazing to not have the weight of the camera around your neck but securely attached to my backpack strap. The ease of attaching and removing the camera makes me actually use it more on hikes.

The amount of effort this guy puts into his projects is often mindblowing. Amazing content to get an idea of all the unforseen complexities with engineering seemingly simple concepts.

This seems like a very broad and vague question to me, making it hard to answer or imagine a starting point for your discovery on the subject.

Like many scientific fields these days the breath and depth is immense. Are you looking for a specific niche of astronomy or an overall understanding of the universe? And is that from a human perspective or perhaps a physics perspective?

I would narrow down your interests and start finding relevant sources there. Or, if you don't know, start at a very broad source like space.com or nasa.gov and explore the topics that grab your attention.

NASA needs to get taught on how to do live streams in 2022. For such a long-awaited presentation from one of the biggest space agencies in the world the quality of the live stream is terrible. Low video quality (720p highest), constant lag, microphone issues (wrong microphone open leading to NASA-ASMR) and failing connections to external locations.

I wish they put more effort into this. It deserves it!

Completely agree that this is the easiest way to do it. Especially a big whiteboard that can hold those sketches to come back to is really valuable. If only it was just as easy to digitise (not looking at you, laggy overpriced smart board).

WSL2 with docker containers should bring you quite close to the environment you're used to. Added benefit of working from containers locally is the server parity in OTAP

Looking at the thread in the product page this is not a cracked product. The listing is for a business license (probably OEM volume license) including several Adobe products.

Somewhat of a grey area in terms of legality, but not cracked (which would be strictly illegal).

I've long ago realized that going to sleep with a prepared mind (occupied by the problem) would often result in a working solution when waking up in the morning.

Once read an article that research showed that studying before sleep would increase retention 30% compared to studying in the morning. So at night your brain is actively working and you can take advantage of that.