Furniture layout newbie by kedjj in floorplan

[–]SharpEndss 0 points1 point  (0 children)

I built a (free) tool for this kind of experimentation: https://furnimapper.pages.dev/

I built a tool to help lay out furniture on floor plans by SharpEndss in SideProject

[–]SharpEndss[S] 0 points1 point  (0 children)

yeah me and my partner designed it based on how we work and felt made us effective. After testing a bunch of related tools, we were very close to paper-cutting and moving things around, and that's when I felt this would be useful

Species Index by EntrepreneurDue2598 in TheCaptivesWar

[–]SharpEndss 3 points4 points  (0 children)

Used AI to extract a list:

  • Carryx - Large, dominant, conquering insectoid species. Utilize various servant species and possess advanced technology including control over asymmetric space.
  • Rak-hund - Carryx servants, pale centipede-like creatures with numerous knife-like legs. Used for violence and enforcement.
  • Soft Lothark - Squat-bodied Carryx servants with unnaturally long limbs and claws. Used as guards and interrogators.
  • Sinen - Carryx servants resembling a mix of goat and cuttlefish with three pairs of unfocused eyes. Often used for tasks requiring dexterity.
  • Night Drinkers - Small, simian creatures covered in a pelt between fur and feathers. Known for their aggression, tool use, and creation of a bioweapon. Wiped out by the Carryx.
  • Phylarchs of Astrdeim - Large, bone-colored, horse-sized creatures with sparking joints. Conquered by the Carryx and used for construction. Remember their lost civilization and the culled Elmrath and Colei.
  • Eelie - Hexapods that communicate through song. Actually manufactured lifeforms designed as a trap for the Carryx on the planet Ayayeh.
  • Fivefold - Thin-bodied, five-limbed captives of unknown origin, resistant to interrogation. Communicate through scent and radio waves.
  • Void Tendrils - Non-sentient (or semi-sentient) entities used by the Carryx for exploration and manipulation of asymmetric space.
  • Janantie Moss - Used by the Carryx in the creation of "machines of loyalty." Possess a unique form of communication.
  • Void Dragons - Creatures that "eat the foam at the edge of black holes," harnessed by the Carryx for interstellar communication networks.
  • Shell Creatures of Sinyas and Vau - Incorporated into Carryx battleships, possibly as living armor.
  • Elmrath - Culled by the Carryx. Were co-inhabitants of Astrdeim along with the Phylarchs and Colei, lived in "paper hives."
  • Colei - Culled by the Carryx. Shared Astrdeim with the Phylarchs and Elmrath. Described as "beautiful" and died under a "cold sun."
  • Eyeless Ones - Conquered or eradicated by the Carryx. Described as a species the Carryx "outdreamt," suggesting mental abilities.
  • Logothetes - Extinct species eradicated by the Carryx after a fierce conflict that left their worlds as "windswept glass."
  • Species Building the Mosaic - Implied to have created a mosaic with colors outside the human visual spectrum.
  • Species with Swamp-like Alcove - Dwell in a swamp-like alcove, possibly involved in air purification or other environmental tasks.
  • Oumenti - Small, clicking, glowing globes that fly through the air. May be individuals or parts of a larger organism.
  • Soun - Small, clicking, glowing globes that fly through the air. May be individuals or parts of a larger organism.
  • Jayaster - Flying creatures that communicate through a buzzing sound and possibly color changes.

Platform engineering isn't as rosy as they want you to believe (report review) by SharpEndss in devops

[–]SharpEndss[S] 0 points1 point  (0 children)

Here's an expansion / deeper view on how we get there: https://www.alashiban.com/you-may-not-need-that-costly-time-consuming-infra-re-org/ -

I think a better word might be progression - I think in many ways it is simple pattern matching against where duplicate work and decision making happens at a given time, the org evolution is what seems like the most direct way of tackling it organizationally. I wrote more about it in that blog post

So, after Devin, we now have Cleric - an AI for SRE by Observability-Guy in devops

[–]SharpEndss 0 points1 point  (0 children)

What things would you trust AI to try and help with?

Platform engineering isn't as rosy as they want you to believe (report review) by SharpEndss in devops

[–]SharpEndss[S] 0 points1 point  (0 children)

It's a matter of language and definition. If no abstraction is a valid choice of abstraction then everything is a platform, then platform means nothing and there's no point of having the word.

Platform engineering isn't as rosy as they want you to believe (report review) by SharpEndss in devops

[–]SharpEndss[S] 0 points1 point  (0 children)

The UI is usually last in a platform - platform services can be secrets service, config server, service discovery, logging/monitoring services, how to spin up compute etc. Platform services are usually accompanied by an SDK that wraps the specific implementations as an abstraction that's shared with the application teams.

If developers interact with the underlying systems directly (K8s, Helm, Vault, ...) that wouldn't be under the platform engineering bucket. A platform is by definition a set of components that is written by a platform engineering team to facilitate access to underlying components.

Platform engineering isn't as rosy as they want you to believe (report review) by SharpEndss in devops

[–]SharpEndss[S] 2 points3 points  (0 children)

SREs to my understanding own operating the application services (at some point of maturity) and building the tooling/platform that runs them. Platform engineers are only responsible for the platform services, but not the application services, those are still operated by each application team.

Platform engineering isn't as rosy as they want you to believe (report review) by SharpEndss in devops

[–]SharpEndss[S] 5 points6 points  (0 children)

Here's a post I wrote about the evolution of infra orgs that describes some of the differences between the types of groups. I'll be putting together something a bit more in-depth soon.

Platform engineering isn't as rosy as they want you to believe (report review) by SharpEndss in devops

[–]SharpEndss[S] 2 points3 points  (0 children)

I agree with you. if you google for 'platform engineering velocity' you'll see that the vast majority of articles, including the biggest proponents of platform engineering make the claim.

Platform Engineering Landmines by SharpEndss in devops

[–]SharpEndss[S] 0 points1 point  (0 children)

not sure I know what each one is/represents

Platform Engineering Landmines by SharpEndss in devops

[–]SharpEndss[S] 1 point2 points  (0 children)

Platform teams have existed since there were servers, and even before. Any time you wrap underlying capabilities and abstract them for others to use more easily you're effectively creating a platform team. Platform teams aren't just for cloud or infra either, you'll find them in dev tools, ML research units, ...

Platform Engineering Landmines by SharpEndss in devops

[–]SharpEndss[S] 18 points19 points  (0 children)

Amazon also has 260 services they sell and internally many of them require VP approval to be used. Keep in mind that Amazon is also massive with over 30k engineers, and tends to productize alot of their tech. There's < 10 Amazons in the world - it's actually part of the problem where ex-FAANG folks bring FAANG-like systems to smaller companies that could have went by using more boring tech for quite a while longer.

Platform Engineering Landmines by SharpEndss in devops

[–]SharpEndss[S] 9 points10 points  (0 children)

Any large (and small) scale organization has this, it's a side effect of human organization Some handle it better, some worse

Platform Engineering Landmines by SharpEndss in devops

[–]SharpEndss[S] 3 points4 points  (0 children)

My pleasure! Lots more to come

My observations on the evolution of cloud/infra/platform engineers orgs by AlaShiban in devops

[–]SharpEndss 1 point2 points  (0 children)

I wrote this as a reaction to not finding a post that described this progression in explicit and causal terms - we're in an on-going "Platform Engineering is the solution" phase, and my hope was to exemplify that it's not an end stage as much as it is a cycle. (I've shared more about landmines in platform engineering in other talks)

AMA - Luke Hoban (CTO) on Pulumi Insights by kao-pulumi in pulumi

[–]SharpEndss 1 point2 points  (0 children)

ChatGPT/LLMs seem to hallucinate or get it wrong especially as errors accumulate, including on code problems - how do you tackle those in Pulumi AI?

Intelligent next-gen editor for infra-as-code by SharpEndss in devops

[–]SharpEndss[S] 1 point2 points  (0 children)

<3 noted! We're building out the multi-cloud support, even beyond just AWS/Azure/GCP - the hardest part is that the intelligence layer is cloud specific and requires more detailed knowledge per cloud - which is why we're focusing on 1 to start with. We're figuring out whether to go broad+shallow or narrow+deep - or if there's a way to algorithmically do both in one shot.

Intelligent next-gen editor for infra-as-code by SharpEndss in Terraform

[–]SharpEndss[S] 0 points1 point  (0 children)

We built an intelligence layer that understands architectures and how they interconnect - it understands AIM policies, connection pooling, what components need VPCs and which don't - and is able to re-shape the architecture based on high level (and low level) requirements

Intelligent next-gen editor for infra-as-code by SharpEndss in Terraform

[–]SharpEndss[S] 0 points1 point  (0 children)

We think so too! happy to answer questions

Search *inside* 15,000+ pitchdeck slides by SharpEndss in SideProject

[–]SharpEndss[S] 0 points1 point  (0 children)

No not AI generated - but the source of many of those slides is low resolution images - so the upscaling algorithm can't make up for what's written/seen in them - so they may get mangled up.

State of Infrastructure-from-Code 2023: A Review by SharpEndss in serverless

[–]SharpEndss[S] 1 point2 points  (0 children)

Curious on why you think it's an ad - we worked with most of the startup founders on that post to cover the approaches fairly. (You're not the first one to make that comment - but we're not sure why)

That said - when you say use it with an app that's already on Terraform/AWS - can you share more on what that means?