Jim Selikoff

Co-Founder at Check out user scans here:

[Jim Selikoff @JSelikoff]

Just walking through a capture of the Old Tyme Barber Shoppe... in my house! Request an invite to the SiteScape beta here: https://t.co/VTTJR6oUHO @SiteScapeAI @AndyPutch

[Jim Selikoff @JSelikoff]

@benstraussphoto https://t.co/kQ6oKDY9If

[Jim Selikoff @JSelikoff]

@iBrews @SiteScapeAI Probably best to try a couple of merges both ways and decide which works best for you!

[Jim Selikoff @JSelikoff]

@iBrews @SiteScapeAI Auto merge basically uses ICP (iterative closest points) which works best if scans have overlap and sufficient features, i.e., not a blank wall. We don’t enforce a user’s movement between scan segments so there could be cases where ICP can’t converge on a solution.

[Jim Selikoff @JSelikoff]

@iBrews @SiteScapeAI Scans in a multi-scan are generally pre-aligned, so a manual merge can usually be done without adjustment to scan position or rotation. The new “hands-free” mode assumes no tweaks are needed and skips the UI steps of the “Manual Merge”. Merged scans are returned very quickly!

[Alex Coulombe @iBrews]

One technique I stumbled on and really liked: Meta Ray Bans for reference video paired with @SiteScapeAI for depth data. Perfect for great big scans across a huge area.

[Jim Selikoff @JSelikoff]

@iBrews @SiteScapeAI Hey Alex, nice scans! Check out the “Hands-Free” Manual Merge option we just rolled out and let us know what you think!

[Donny Wals 👾 @DonnyWals]

I think the most harmful way you can use AI in your day to day work is to have it write code you truly don't understand.

If you can't vet the quality and security of the code that you're being given it's likely that you'll eventually run into problems because of it. As the project grows, you'll come to fully rely on the AI to know what it's doing (pro tip: it has no idea no matter how smart it looks) and it will backfire.

Instead, have it write code that you would be able to write yourself. Have it generate boilerplate that you'd find boring to write. Ask it to create small bits of code that you can review and tweak before moving on.

Cursor's composer is great because it can work on multiple files and it seems to know a lot about your project but it's not your replacement. It's a tool in your toolbox. It's a way for you to get stuff done faster and it allows you to focus on building something cool rather than remembering syntax all the time.

Using AI in your workflow adds a new task to your workflow though. Review and understand the AI's output. Sometimes it'll mean that you spend a bunch of time on a few lines of code. You might even have to rewrite or discard the code because it's not good. And that's okay.

Working with AI is exciting but we really shouldn't forget that we, the programmers, are fully responsible for the code we end up shipping.

[Donny Wals 👾 @DonnyWals]

If there’s one thing that I think everybody should understand before attempting to move to the Swift 6 language mode it’s actors, Sendability, and what it means to write thread-safe code. If you attempt to migrate without this understanding I can almost guarantee that you’ll have a hard time understanding the compiler errors you’ll get and which fixes you should apply.

[Warren Moore @warrenm]

I’ve updated my Metal spatial rendering sample to enable mixed immersion on visionOS 2 (beta), including a demonstration of how to emulate “progressive” passthrough transitions:

https://t.co/zXkZJWD7sV

[Donny Wals 👾 @DonnyWals]

Xcode 16.0 release notes are up though https://t.co/UW75g3hZWH

[Paul Hudson @twostraws]

What's new in Swift 6.0? I'm glad you asked!

- Full details with sample code: https://t.co/r6TM1MReBD
- Interactive Xcode playground: https://t.co/uPO4xJsT9M
- All Swift changes from 1.1 to 6.0: https://t.co/nOLLM1xisd

And now: it's time for #WWDC24 fun at Infinite Loop 🎉

[Jim Selikoff @JSelikoff]

@DonnyWals No more dancing with QuickTime for Teams sharing

[Jim Selikoff @JSelikoff]

@DonnyWals Check whether they finally added a LiDAR capability flag 😝

[Jim Selikoff @JSelikoff]

@voxagonlabs I see potential for a casual game where you’re a dieter getting chased by giant rice krispy treats / other high sugar, empty calorie snacks!

[Jim Selikoff @JSelikoff]

@docmilanfar Lacks common sense, perhaps, but not novelty!

[Frank Dellaert @fdellaert]

Impressive new 360->”CAD” method from @RealityLabs . Tiny brag: they use an “Atlanta World” prior, a term Grant Schindler and I coined after being dissatisfied with the rigid “Manhattan World” assumptions. Ah, good times :-)

[Frank Dellaert @fdellaert]

Apple seems to have some pretty good Visual Odometry under the AVP hood - not surprising as ARKit is quite good already (https://t.co/o4QUo6RTw8) - but this seems better than 2cm/second. Expected with higher field of view, still impressive!

[Donny Wals 👾 @DonnyWals]

Swift 5.10 is officially available so in this week’s post we take a look at everything you need to know about Swift 5.10.

In short, Swift 5.10 makes some very welcome improvements to the compiler’s ability to check whether your Swift Concurrency code is free of data races when you enable strict concurrency checking.

You can read the post here: https://t.co/VoqDJlyMXv

[Thomas Flynn @nebulousflynn]

Just in time for the weekend it's this week's Top 10 Cultural Heritage & History #3D models on @Sketchfab.

☕ Take a minute (or ten) to explore artefacts, spaces, and scenes from around the globe 🔗 https://t.co/Y5PH4urNts

...
#GLAM3D #3DforCUlture #museums #openGLAM #MuseTech

[Frank Dellaert @fdellaert]

#AppleVisionPro epiphany after walking back to our kitchen and finding Photos floating there, in *exactly* the same location: the App Store moment will be when third-party spatial content is discoverable and available in situ, *everywhere*.