vinnymac

Additionally, as long as documentation is made throughout, this can still be valuable.

* Someone else can continue research, where they left off.

* The research they did, can be discussed amongst the team, possibly by a more senior teammate.

* It may reveal that further research isn’t necessary, and this effort should be shelved until a later date.

I had to create one for work last Thursday. They still require either a phone number or credit card when creating a developer account too.

I usually use https://oshpark.com/ or https://jlcpcb.com/ with EasyEDA or Kicad depending on what you're comfortable with. A good 3D printer wouldn't hurt either.

> I’ll also apologize if this post is a bit chaotic.

Loved this, didn’t find it chaotic at all.

Not sure if I missed it, but how are you planning on moving data from the old to the new storage? Do you have any concerns with corruption at that stage (validation)?

In addition to this communication guidance, I prefer when issues are disabled entirely. I would like it to be the default.

I am also looking forward to seeing LLMs applied to this space.

Plenty of problems could be solved with some simple research and understanding of the code in a project. If that could act as a barrier between those with issues and those who contribute, I imagine it would help a lot.

The UI problems are a symptom that Jira is complex, and they push that complexity onto the user rather than offering a simple product that forces everyone to operate how they recommend you should.

The freedom Jira offers managers is not for the benefit of any workplace I’ve ever been. I much prefer every single tool I’ve used that isn’t Jira for this reason.

I’ve experienced this as well.

For some projects I just configure publishConfig.directory directly at the dist folder.

While this may not look as clean, it is a lot easier for me to manage everything that’s published under a single directory.

I haven’t really struggled too much here.

Maybe an aversion to bundlers exists, but I think tsup and vite are great and simple. We have turbopack on the horizon too.

For small projects I don’t even need a configuration file for tsup to target both formats. For larger more complex projects vite configs tend to be under 50 LoC.

My best guess is that the code was used in non-node environments.

It wasn’t and isn’t uncommon to pull down a dependency from npm and expect it to work in multiple runtimes.

Olive is pre-release so it may be early days regarding educational material. The article includes exercises you can try, and I found the documentation to be decent.

https://microsoft.github.io/Olive/

I’m not sure if you’re being serious, but in any case; This will happen, as it always does, inevitably.

Meh, with Googles resources they could do so much good. This is a drop in the bucket, compared to what they could be doing.

My company is scrambling to account for the changes here, and ultimately it will be users who suffer until we have the proper data available.

This should’ve been a standard that all major browsers have implemented and agreed to, before being rolled out generally.

If you search the github page for the project, many have reported using a raspberry pi.

For example, here is an issue where a raspberry pi 4 is used. https://github.com/immich-app/immich/issues/611

Does this imply you can’t have `using` in expressions?

I have been writing GraphQL APIs on and off for the last 5 years, and in practice haven't had many scenarios where this was an issue.

In GraphQL the query for the example you gave could look like this

  ```gql
  query {
    user {
      things {
        owner {
          id
        }
      }
    }
  }
  ```

When resolving an array of type `Thing` for the `things` field, you would query for the user that the `owner` field represents. Rather than assuming all relations should be loaded for an owner by default, the client would specify the fields for the `owner` that it needs. Such as I have above for the owner id. Even if no fields are specified, it would be weird to assume all relations should be loaded by default.

Now if your developers are intentionally creating infinitely deep queries, then you'd solve this the same way you'd solve an infinite loop in your code today. An issue you would catch during development or CI/CD. This can be easy to catch using a linter or during review.

  ```gql
  query {
    user {
      things {
        owner {
          things {
            owner {
              things { } # etc
            }
          }
        }
      }
    }
  }
  ```

To simply protect from bad parties / developers, you might use something like https://github.com/slicknode/graphql-query-complexity

In addition you could introduce CI tools to enforce your devs stop writing such complex queries. Also see the @skip and @include directives that can further be used to control what data is queried. In practice, however, this isn't something that comes up too much. In cases where I have seen this happen, it's usually because a developer is trying to reuse fragments without considering what data they are querying, and whether they should be reusing those fragments.

https://graphql.org/learn/queries/#fragments

I haven't written Elixir professionally the last couple of years, but I was an early user of LiveView when it was first demoed at a conference.

As someone who currently writes applications using React Server Components, I am interested to see how concepts like LiveView evolve over time. We are now shipping significantly more HTML than before, and a lot less Javascript, as more has been moved to the server.

Makes me wish LiveView was portable to every other platform I work on, rather than having to convince companies to write more Elixir (although that isn't a bad thing).

I was surprised to see this mentioned.

I was working for a company over a decade ago that saw the military purchase a piece of software from us specifically for its messaging and XMPP based capabilities. We were requested to rewrite chunks of our application just to meet their needs. Makes me wonder if it is still in use somewhere.

Yea, the future of public discussions online is interesting to consider. LLM bots are already a thing, comments posted here could be from a bot. We don't have a way to really confirm it, and I am not sure it actually matters (yet).

Seems in addition to unpaid rent, they also haven't been paying to have the office cleaned.

https://www.denverpost.com/2023/05/22/twitter-boulder-colora...

I wonder if this office was still occupied.

First demo I tried was `Visualize weather data with two React chart libraries`, and all I see is an error at the bottom.

> Something went wrong: TypeError: Cannot read properties of null (reading 'useRef')

Appears to be an issue with the charting library used here at a glance?

Mobile browser support is a little problematic.

A couple of things I noticed immediately, that you may want to consider.

  - landing page is not responsive, hard to read on Safari on iOS
  - login screen in-app couldn’t be closed, had to navigate away to exit, perhaps a hidden icon somewhere?
  - comment threads seemed to have the same issues on iOS as the landing page

Definitely like the direction you took for the UI, looks like with a little bit of work it’ll become a great platform though!

Seems fruitless as an approach to reducing confusion to me. What about versions 0.1.6, 0.6.1, 6.0.1, and 6.1.0?

I’d be more likely to think something was wrong with those releases, and assume someone was forced to delist versions 0.16.0 thru 1.5.0.

As someone who’s used all three for years, I am curious why you feel Gitlab is superior?

The developer experience of GitHub and CircleCI feels better in every way from my perspective.

This school year, is the first that my wife hasn't taught, since she became a teacher. I watched over the last two years, as the pandemic beat her down, until she had to move on. You can only get physically and mentally abused, while being underpaid, for so long, before it becomes too much of a sacrifice.

I agree. The newer charging stations are so quick at a rest stop, that I don't even notice them anymore. Once it's down to 10 minutes, it won't even be a discussion topic imo.

Gamespy Tunnel as well, although I was always more a fan of XBConnect.

Both Google and Meta have reached out to me directly for an interview in the last week. When did this hiring freeze begin?

People live on transit, even where it is not free. I am curious how many more would live on transit, if it became free.

I am curious, how does this compare to say RAM usage on a smartphone or a tablet browser?

Is the newsfeed leaking mem, or is it just 50GBs over time?

I have seen the resume padder on many occasions, and have had to clean up after they left. It's amazing to see a team become visibly happier with their day job when you move to sensible foundations based on sound reasoning.

The teams that were the most efficient, and happiest with their day to day were the ones which picked frameworks with good documentation, a plethora of online resources, and ignored the latest shiny toy on the market.