Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shoo
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
34 ms
·
361.
▲
by
shoo
4y ago
Another recommendation for Peter Watts. Watts' Backlist is also available to read from his website, including 4 novels (his Starfish + Maelstrom + Behemoth trilogy) and Blindsight, as well as many short stories: https://rif
362.
▲
by
shoo
4y ago
the boulder did not suffice. what other steps can we take to prevent recurrence?
363.
▲
by
shoo
4y ago
This is a fair anecdote about response an active production incident. While there is a live incident, the focus should be on resolving it, and restoring service to customers. But, this anecdote does not comment about a postmortem or other o
364.
▲
by
shoo
4y ago
I don't have HR or management experience, but I can speculate: - an employee avoids sharing key technical information with colleagues, either verbally or writing anything down, and becomes a bottleneck for all changes relating to some
365.
▲
by
shoo
4y ago
Conclusion of the linked paper: > The results of this paper suggest the presence of a substantial bias against making changes when it comes to important life decisions, as evidenced by that fact that those who do make a change report bei
366.
▲
by
shoo
4y ago
Leaving a job is a good opportunity to re-calibrate your pay to market rates. Most companies don't give existing staff raises that are indexed to market rates. It can also be a good opportunity to set healthier boundaries - e.g. if you
367.
▲
by
shoo
4y ago
this is a crucial point. if the noodle nest does not solve an important customer problem, it can be eaten or thrown out. being eaten or thrown out is not the pathway to immortality. it must provide an important business function or feature,
368.
▲
by
shoo
4y ago
i think this has been the outcome every time i have seen BDD applied. when the only people maintaining the BDD suite are the developers, the situation can be improved by throwing away the human readable BDD layer and allowing the developers
369.
▲
by
shoo
4y ago
This kind of thing seems to happen in very large organisations that have accreted many production IT systems, especially once an org realises it has half-a-dozen different services in production that are performing an apparently equivalent
370.
▲
by
shoo
4y ago
> Everyone on this site is on average much more polite, resourceful and ambitious compared to the other tech sites. Hear hear. This site abounds with better-looking people with better ideas and more talent. And they're actually real
371.
▲
by
shoo
4y ago
> it took me 5 years to catch up with the salaries my friends who didn’t take the pause were making Worth exploring the opportunity cost in a bit more detail. One possible trajectory is to get a junior permie SWE job on some commercial p
372.
▲
by
shoo
4y ago
Sometimes experience can even be harmful. Suppose an individual or a team encountered one situation, and worked very hard to explore, figure out a viable "attack" to solve it, perhaps after a number of failures. Now they have expe
373.
▲
by
shoo
4y ago
When thinking about applying "lean" approaches to delivery of software projects, one easy but flawed analogy is to think of a manufacturing plant churning out some kind of widget. Say, we're manufacturing zippers. In the case
374.
▲
by
shoo
4y ago
That tracks input, not output. Maybe it's a good leading indicator, but how many nickels did this generate? What's the nickels/spit ratio compared to the last few quarters?
375.
▲
by
shoo
4y ago
here's a rough summary: 1. Mary recounts her experience of working with computerised MRP planning systems. These detailed plans were fragile and would need to be thrown out once reality began to diverge from the plan, then re-planned.
376.
▲
by
shoo
4y ago
It'll depend on the details of what business function the ML component is integrated into, how critical that function is, and how the org has chosen to structure production support responsibility across roles and teams. If the ML compo
377.
▲
by
shoo
4y ago
https://www.smbc-comics.com/index.php?&id=2411
378.
▲
by
shoo
4y ago
> it is us operations people who have to wake up to fix it in the middle of the night I have a tremendous amount of respect for operations & anyone else working at the "pointy end" of service delivery. Please make sure you
379.
▲
by
shoo
4y ago
Context definitely matters about the impact of failing to hit schedule has on the employer/client's business. But, all that said, the responsibility of meeting the deadline - or the risk and consequences of failing to meet the dea
380.
▲
by
shoo
4y ago
Thank you for sharing, yours is the healthiest perspective I can see. This aligns with how things should (and can!) work. My context: more than 10 years experience in commercial software/IT projects in Australia.
381.
▲
by
shoo
4y ago
technical perspective, ignoring business perspective: resolving the bugs by writing tests is excellent advice, especially once a component is sufficiently complex. get regression tests in place first, so you can sense how may new unknown de
382.
▲
by
shoo
4y ago
Another aspect is the cost and risk to the company if it ships defects to production (assuming it actually has customers, has largely de-risked product-market fit, etc). Suppose a company is in the hardware business and locks its cash into
383.
▲
by
shoo
4y ago
Great question. I don't know the details of how database schema changes were deployed, I only worked on the easy stuff - stateless web services. Exactly as you say, there is a time window where both the old and new system write to the
384.
▲
by
shoo
4y ago
Sometimes attestation can be involved if there are things like manual test or QA phases, and perhaps the QA manager needs to attest that the feature / release has passed some test plan. Sometimes it is possible to replace these "h
385.
▲
by
shoo
4y ago
I worked on a little web service in a much larger system, that was deployed to the company's on-prem datacentres. To deploy the entire system, maybe it'd take a few hours: there'd be 1-2 dozen services, a few databases, proba
386.
▲
by
shoo
4y ago
iphone, android? Linux? stretching "consumer" platform a little here. Costco?
387.
▲
by
shoo
4y ago
> you can't draw meaningful conclusions when some users get every new feature and some get none at all. those poor cursed users. reminiscent of a joke that used to grace Paul Mineiro's blog (machinedlearnings.com) a few years a
388.
▲
by
shoo
4y ago
Do you still do GIS through code or have you escaped entirely?
389.
▲
by
shoo
4y ago
Rob Walling has written and spoken a lot about marketing for developers. Rob published a book in 2010 titled "start small stay small" https://startsmall.com/ . A lot of the specific tricks and tools may be a dec
390.
▲
by
shoo
4y ago
The bogleheads.org "Non-US Investing" forum may be a good place to ask this question. https://www.bogleheads.org/forum/viewforum.php?f=22
More ›