You have an idea and want to prototype it but you don't want to waste time building a backend for it just yet, try Dummy-Backend, it's simple and creates resources as you go with a proper REST structure.
If you product has inherent danger you should be responsible for it, I don't think it's unreasonable. If you're asking the same rights as human beings, then you should assume the same exact responsibilities
I always felt that if you want fairness and want to rip the full benefits of your creation (here AI) you should also be assuming full responsibilities for it. This is were most organizations fell short as they are always trying shift all responsibility to their users (self driving anyone?).
There is a long answer, but to keep it short we automated optimized planning. We can run the planner as many times as necessary (every time something changes) and find the best route to reach your goal based on your priorities and hours available. It's mostly a statical game, we constantly search for the best next move, not unlike video game AI, and recommend it to you. The AI behind the planner is were we spent the most time.
It's easy to forget that prior to its acquisition, Twitter was a financial catastrophe. It still could be, but Twitter seems to be working hard at becoming a profitable business. Does praising its unsustainable past and lost designs makes us some kind of spoiled brats?
Cmd + C is great… regarding the rest, I suspect your hardware could also be the sources of your problems. I also think anybody can work on any OS (as it is the case right now). Most of my compute is done on my Linux desktop, I sometimes work remotely on my MacBook via SSH and SSH+VPN when away from home. In my experience all Mac laptops get uncomfortably (understatement ) hot quickly and sometimes won’t turn on the ventilation on (when available)
I’ve tried the quest 2. I truly wanted it to work and was hoping I could find fixes when I hit roadblocks. I even invested in the most highly rated head strap and foam.
For me it’s a no go. The software is kinda ok, the headset are also kinda ok but heavy. Overall the experience was mediocre at best. I lost velocity for the two weeks I tried using it, it was clunky and often not working and needed just too many hacks.
As a sideline, this website has been designed using TailwindCSS... to the point that their page logo is the TailwindCSS logo rotated by 90 and so is their website background. I can't speak for the TailwindCSS team but that feels like pushing the use of free software a bit too far
I have never been in a company that was able to deal with backlog. Albeit I have not worked at all companies, there's got to be some that successfully deal with backlog... but how many?
Is Scrum a solution that really works, or merely a great concept?
I agree with and swear by the agile manifesto (it's really amazing) but IMHO, all of its byproduct methodologies fall short in the real world, with no exception.
I'm a manager, and post-its, tv screen in the room, extremely large whiteboards (all 3 walls) and spreadsheets have been my secret weapons for a long time... that and going on a long walks with my engineers 1-on-1 to discuss ideas and problems.
Tools and methodologies are guardrails, use them at the beginning as you learn the craft, get ride of them as you grow and always put meaningful conversation above all
Yes, sprints on paper are what you describe, but in reality, they rarely ensure deliveries or predictability, they even tend to hinder productivity as they narrow the body of work of a whole team. Think about it, after a week, what is usually the distribution of work of your team? For me, it was always very unbalanced, where people where working overtime and others (best case scenario) would be looking for some work to do.
I understand the author's heated post, because I've been there so many times, and I think THIS IS THE POINT of this article, the point that you are missing. Good manager shouldn't rely as much on a set tools that are broken or unfit for their team.
I my opinion, not enough people question Sprints and their viability and benefits. And he's right, backlogs are by far just a list of the things you wont do.
If your tool cannot fix your issues, the manager should. Use post-its, emails, spreadsheet, large whiteboards, hang a TV screen in the room, pdf, discussions... There is endless possibilities, be creative.
The pagination con given in the article is wrong, switching to stream isn’t fixing the dropping issue, removing sorting is likely why no records are being dropped (you wouldn’t drop records using a numerical sorted ID or creation date)
Pagination is incredibly useful to human. If I tell you I found something on page 15 you can relate to it, something I cannot do with infinite scroll.
I think there is a form of exhaustion regarding how crypto and Web 3 is supposed to resolve many things that seem to be working just well enough.
I understand that innovations do happen but the complexities (like smart contracts), the limitations of an append only database (that only store transactions and signatures), the damage done to our environment (CO2), the impact on electronic availability (video card shortages), the criminal uses of crypto and the life savings lost to a gambling like international market does make you wonder if this is all worth it.
I’m open to be proven wrong but I personally think that web3 and crypto, while very interesting, don’t have the attributes required to be a worthy innovation path for humankind
The best hands-on practice was when I had to build my own, nobody to tell me to cut corners and time to do things right. It's important to do it right to know how to do it wrong (most company will prevent you from doing things right because of time/budget constraints).
Ask yourself:
- What constitute a _good_ infrastructure?
- Something flexible/adaptable ?
- Something predictable ?
- Something resilient ?
- Something easy to monitor ?
- Something else ?
- How do you prioritize these, who gets to decide which one matters most...
Architecture is asking a lot of questions, inviting others who will benefit/use your work into the decision making process.
One thing that I learned that is still helpful to me today is try to push as many decisions as possible to later, keep the door open for futur choices. Every system architecture is part invention, part discovery. As you put together your foundation, new requirements/restrictions will appear and you'll be happy to have the freedom to make some of your decisions then.
I’m puzzled why he didn’t take the video down while he acknowledged that Maree is upsets about it, instead asking that she contacts him and requests the video to be taken down.
The strange perspective and sense of entitlement of a successful TikTok influencer…
I would add that, even for regular HTML you can write CSS using @apply and still leverage the nice structure tailwind provides while creating your component CSS classes.