| ▲ | josh2600 a day ago |
| This is sick, in the 90's Tony Hawk sense of the word. I love that people can just bang stuff into existence now. There were times in my life where I would wait for an engineering team to change the color of a button for a day to a week. We are not in the slow times anymore. |
|
| ▲ | shajsiisiss a day ago | parent | next [-] |
| You think technology was the bottleneck? Your button was not important and should not consume
resources of any kind and definitely not engineering resources. It taking a week was a feature, not a bug. It meant engineering properly evaluated the priority and urgency of tasks. Your magic slotmachine will enable a level of shit-producing and warped perception of engineering effort of breathtaking scale. It will have consequences. |
| |
| ▲ | left-struck 17 hours ago | parent | next [-] | | For years almost all the engineering effort at all the tech companies went into engineering things which grab as much human attention as possible. Almost any use of engineering time, or AI or whatever would be better than that. | |
| ▲ | frollogaston a day ago | parent | prev | next [-] | | Sometimes latency matters more than throughput. A simple change can and should go in quickly if the manager wants to see it. Except sometimes it can't because the team is strangled with red tape. | | |
| ▲ | Perz1val a day ago | parent [-] | | > if the manager wants to see it Exactly that's how prioritising works |
| |
| ▲ | tuwtuwtuwtuw a day ago | parent | prev | next [-] | | How is it warping the perception? | |
| ▲ | scotty79 a day ago | parent | prev [-] | | > You think technology was the bottleneck? Well, evidently. |
|
|
| ▲ | linsomniac 14 hours ago | parent | prev | next [-] |
| >I love that people can just bang stuff into existence now. I need to see if it can build me a fabulous todo app. 4-5 years ago I spent around a year refining a paper-and-pen daily planner, and I went 100% into it and liked it. The paper planner though had a non-ideal workflow, and so I wanted to look into some automation of it. I got a Kindle Scribe hoping they might grow its capabilities. It had a great "it's like paper" experience, but no automation or tools or apps seemed to come along. So then I tried a fairly high end Boox, I got it and then used it only a couple weeks and then stopped doing that daily planner process entirely. But if Fable could build a Boox or reMarkable app, that might be a big win. I've tried task warrior, and todoist, and in the end I just keep going back to a straight text file I edit. |
|
| ▲ | nonethewiser a day ago | parent | prev | next [-] |
| The funny thing is, making the input/output mechanism is way less impressive and especially way less useful than the underlying LLM tech that hackernews loves to deride. |
|
| ▲ | Yeask a day ago | parent | prev | next [-] |
| If a team takes a week to change the color of a button... is not because changing the code is hard. Were you the PM on those project btw? |
|
| ▲ | tffrr a day ago | parent | prev [-] |
| There were times in my life where I would wait for an engineering team to change the color of a button for a day to a week. lolwat sarcasm surely |
| |
| ▲ | glerk a day ago | parent | next [-] | | > stylelint beeps you can't just pass hex colors directly, that color is not in our design system, you need to write a design doc for custom color tokens and get approval from the frontend platform team, open a PR in their repo, make sure you have storybook tests covering all the color <cross product> button variants, ask in their slack channel for approve, ask their manager, wait. someone from their team leaves a comment: "we should make this an approved custom colors enum not a string, so if you want to add custom colors you also have to update this enum", fix the PR, staff engineer from sister team drive by request for changes: "we are currently implementing custom themes and changing colors will be done through the ColorSwatch service", ask for timelines, "maybe next week behind a feature flag", give up, close the PR, open a new PR with "stylelint-disable", force-merge it. | | |
| ▲ | handoflixue a day ago | parent | next [-] | | Your PR has been denied for not including a Ticket Number. Please make sure all bugs are assigned a Ticket and properly T-Shirt Sized at the next Scrum! Reminder: due to the holiday, the next Scrum Meeting will be in 3 weeks. | |
| ▲ | drawfloat a day ago | parent | prev [-] | | Probably should be telling the design team to actually use the colours that are approved then. | | |
| |
| ▲ | MarkusQ a day ago | parent | prev | next [-] | | I remember it taking long enough (they had to wait for another project to need a lot of that color) that we wound up using dope to mock it up. (Regular paint didn't hold and just chipped off.) | |
| ▲ | dylan604 a day ago | parent | prev [-] | | gotta catch 'em at the right time of a sprint cycle | | |
| ▲ | ern a day ago | parent [-] | | I still find people trying to run sprints when working with agents, but then saying things like "my sprint length went from 10 days, to 5 days to 3 days", but they balk at the notion that maybe sprints aren't fit for purpose anymore. |
|
|
