jamisonbryant
Joined 9 years ago
Joined 9 years ago
As developers, we're spoiled for widespread (e.g.) vim keybindings support in just about any IDE via extensions. When unable to use it in something like Web IDE, it is very frustrating and makes it less useful as a product.
[0]: https://about.gitlab.com/releases/2025/04/17/gitlab-17-11-re...
One other unusual (but slightly entertaining) thing the model did was it used a different image for the notification "icon" every go-round. I have absolutely zero idea where it was getting the little icons (hallucinating?? maybe making a HTTP request??) but it was really interesting to see.
A neat tool, I will send it to my frontend guy at work and see what he thinks.
I'd say this highly depends on the fastidiousness of the ticket taker and the rules of the venue. I purchased Major League Baseball tix recently through my employer which uses a 3rd-party seller site that has restrictions like this (a moving graphic behind the barcode with the admonishment not to take a screenshot because it won't work).
I was unable to attend the event that night so I sent my wife a screenshot of the ticket. Two tickets, in fact. They were taken with zero issue.
The funny thing is, before the brouhaha I wasn't even using a third party app to access the site or any 3rd-party platform (that I'm aware of) that used the API. I was using the native vanilla app and I found it just fine.
But, as a developer I could not in good conscience continue voting with my wallet by viewing ads for a company that clearly didn't care to play nice with the developers that were part of making the platform great.
That being said, I caved and set up an account with a temp email and the password 'password' (might wanna check on those password security rules) just to play with it so I could give some constructive feedback. Unfortunately, generating a story isn't working (the spinner is spinning infinitely) and I see a few errors and warnings in the Developer Console. I'm not sure what the Short Stories page is supposed to show, either, but it also appears to be malfunctioning.
I don't mean to eviscerate your project - it is always exciting and scary to share something with the world. This needs a little more work before it's ready for show-and-tell, though, IMO. I'm not even sure what I would use this for. Best of luck.
1. Inability to switch branches in the editor [0]
2. Full project search "to be enabled at a later date"
So I can't switch branches off of the default branch and I can't search the entire project. To me, this undermines your claim that the new web IDE "will provide users access to more features" and in fact I don't find it useful for hardly anything in its current state.
I get that it's a beta, but it seems a very incomplete one, at best.
[0]: https://gitlab.com/gitlab-org/gitlab-web-ide/-/issues/72
This is a great point that I will be sharing with my team. Sometimes (most of the time) I use the git cli, and sometimes I use the built-in Git pane in VS Code.
I have not used GitHub Desktop in quite a while. In your opinion does it make the commit graph easy-to-read? Because I have not found a tool _yet_ that makes that diagram easily parseable by the human eye. It just looks like a mountain of spaghetti commits linked together with a myriad of colored lines.
(I realize that part of the cause of my confusion is crappy discipline around commit history, but what can you do on a team of a certain size where you're not the lead? Just have to suck it up.)
Step 1: send yourself a message and mark it as Saved. It will now show up in your Saved items. The message should contain a section for what you did yesterday and what you're going to do today. Other than that it can be any content or formatting you like.
Step 2: set up a channel for posting your daily logs, e.g. #yesterdayandtoday
Step 3: update your daily log (saved message) as you go through your day. Add things you did TODAY in the Yesterday section, add things you know you have to do TOMORROW in the Tomorrow section.
Step 4: At the start of each day, copy-paste your saved message into the daily logs channel. Do this every day, this will form the longevity of your logs.
Finally, to review all your logs, just search for your name in the channel. Or tags, or whatever. I like to divide my log entries between tasks, accomplishments, blockers, and goals.